Good morning all, @Pete French, you have trim activated on your SSDs right? I heard that if its not activated, the SSD disc can stop working very quickly. @Daniel Kalchev, I used UFS2 with SU+J as suggested on the forums for me, and in this case the filesystem didn't "corrupted", it justs kernel panic from time to time so I gave up. I think that the problem was related to the size of the journal, that become full when I put so many files at once on the system, or was deadlocks in the version of the OS that I was using. @Alexander Leidinger I have the original HDD 1TB Hybrid that came with the notebook will try to reinstall FreeBSD on it to see if it works correctly. Besides my notebook been a 2019 model Dell G3 with no customizations other than the m.2 SSD, I never trust that the system is 100%, so I'll try all possibilities. 1- The BIOS received an update last month but I'll look if there's something newer. 2- Reinstall the FreeBSD on the Hybrid HDD, but if the problem is the FreeBSD driver, it'll work correctly on that HD. 3- Will try with other RAM. This I really don't think that is the problem because is a brand new notebook, but... who knows =). Thank you, Mario Em ter., 25 de fev. de 2020 ?s 08:08, Pete French <petefrench at ingresso.co.uk> escreveu:> > > On 25/Feb/2020 10:52, Daniel Kalchev wrote: > > It might well be, that FreeBSD is more agressive with your > motherboard/chipset or does not implement known quirk of that ? which might > trigger some edge cases for the SSD. Ultimately, if you can move that SSD > to another motherboard and test it, it would confirm where the issue is. > > I have often wondered if ZFS is more aggressive with discs, because > until very recently any solid state drive I have used ZFS on broke very > quicky. For USB sticks that is not unexpected, but decent SSD's also > seem to last less than a year with ZFS on top. I don't let it bother me > anymore simply always install them in pairs and replace when I start > seeing errors. > > By the way, I am not talking about checksum errors here from ZFS, I am > talking about the drive starting to error into dmesg. Checksum errors I > could belive that I was gettign with UFS in the past and just didnt know > it. But this behaviour is that the drive stops working. Some USB sticks > lasted less than a week. Some earlier SSD's only a month or two. More > recent SSD's are lasting longer, and I dont use USB sticks much anymore. > > I am sure I have mentioned this before and people say that it works for > them, so maybe its my magic touch which causes it. :-) > > -pete. > _______________________________________________ > freebsd-stable at freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org" >
On 2/25/2020 8:28 AM, Mario Olofo wrote:> Good morning all, > > @Pete French, you have trim activated on your SSDs right? I heard that if > its not activated, the SSD disc can stop working very quickly. > @Daniel Kalchev, I used UFS2 with SU+J as suggested on the forums for me, > and in this case the filesystem didn't "corrupted", it justs kernel panic > from time to time so I gave up. > I think that the problem was related to the size of the journal, that > become full when I put so many files at once on the system, or was > deadlocks in the version of the OS that I was using. > @Alexander Leidinger I have the original HDD 1TB Hybrid that came with the > notebook will try to reinstall FreeBSD on it to see if it works correctly. > > Besides my notebook been a 2019 model Dell G3 with no customizations other > than the m.2 SSD, I never trust that the system is 100%, so I'll try all > possibilities. > 1- The BIOS received an update last month but I'll look if there's > something newer. > 2- Reinstall the FreeBSD on the Hybrid HDD, but if the problem is the > FreeBSD driver, it'll work correctly on that HD. > 3- Will try with other RAM. This I really don't think that is the problem > because is a brand new notebook, but... who knows =). > > Thank you, > > Mario >I have a Lenovo Carbon X1 that has a Samsung nVME SSD in it and it's fine with both FreeBSD12-STABLE and Windows (I have it set up for dual EFI boot using REFIND.)? It does not have a "custom" driver for Win10; it is using Microsoft's "built-in" stuff. Zero problems and I beat on it pretty-heavily. -- -- Karl Denninger /The Market-Ticker/ S/MIME Email accepted and preferred -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4897 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20200225/31f99c9e/attachment.bin>
FreeBSD does not technically have driver for different disks. People asked whether it is an NVMe device or SATA device, because those interfaces have different drivers. But for FreeBSD, an mechanical SATA, hybrid SATA or SSD SATA will use exactly the same SATA driver. It depends on the chipset. It is possible however, that the timing between the drive and the SATA controller might be different and that is causing the problem. Did you experiment with different settings of the SATA controller in BIOS? If the problem is related to the size of journal, that might mean for some reason the SSD is slow. About th eonly thing an SSD might be slow for is TRIM. Therefore, TRIM might be your problem if weirdly implemented in that drive ? so you might try to disable it and see if the problem goes away. As it?s not a server, I doubt you will notice much of performance drop. You can disable TRIM for ZFS with sysctl vfs.zfs.trim.enabled=0 You can put it in /boot/loader.conf. Do this before writing any data to the pool or even creating the pool. Speaking of that, the output of sysctl kstat.zfs.misc.zio_trim might tell us something. I would advise doing all such tests with ZFS, because it will spot any flaky hardware/setup easily. Daniel> On 25 Feb 2020, at 15:28, Mario Olofo <mario.olofo at gmail.com> wrote: > > Good morning all, > > @Pete French, you have trim activated on your SSDs right? I heard that if > its not activated, the SSD disc can stop working very quickly. > @Daniel Kalchev, I used UFS2 with SU+J as suggested on the forums for me, > and in this case the filesystem didn't "corrupted", it justs kernel panic > from time to time so I gave up. > I think that the problem was related to the size of the journal, that > become full when I put so many files at once on the system, or was > deadlocks in the version of the OS that I was using. > @Alexander Leidinger I have the original HDD 1TB Hybrid that came with the > notebook will try to reinstall FreeBSD on it to see if it works correctly. > > Besides my notebook been a 2019 model Dell G3 with no customizations other > than the m.2 SSD, I never trust that the system is 100%, so I'll try all > possibilities. > 1- The BIOS received an update last month but I'll look if there's > something newer. > 2- Reinstall the FreeBSD on the Hybrid HDD, but if the problem is the > FreeBSD driver, it'll work correctly on that HD. > 3- Will try with other RAM. This I really don't think that is the problem > because is a brand new notebook, but... who knows =). > > Thank you, > > Mario >
On 25/Feb/2020 13:28, Mario Olofo wrote:> Good morning all, > > @Pete French, you have trim activated on your SSDs right? I heard that > if its not activated, the SSD disc can stop working very quickly.On the curent dfives, yes, but I have run with trim disabled in the past, It kinds of depends on the drive - so were horirbly slow on trim, and trim could be a big bottleneck. Havent seen that on a recent drive though, and they all now have trim enabled on them.