Date: Wed, 26 Feb 2020 00:41:52 -0300 From: Mario Olofo <mario.olofo@gmail.com> To: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: Running FreeBSD on M.2 SSD Message-ID: <CAP4Gn9C0OaXA-yxRFmOZfbNpww3vQzFpN8=1vy77gSD_h3OdOw@mail.gmail.com> In-Reply-To: <CAP4Gn9CmftR6hiJvP0VeO-nz243PQVQ-Ym4zz55HCBgD2Y90Yg@mail.gmail.com> References: <CAP4Gn9DFAoQtq6NP4hZ-Jq=ddnhp7Bzc_X%2BSce2FPVWn6kjASg@mail.gmail.com> <202002250115.01P1F9KX090465@mail.karels.net> <CAP4Gn9CqCSk5Lof_-05j1S0EWmTdB_HRfOe5zVig5khf7wJ0ow@mail.gmail.com> <188F34DA-192C-4D44-96B5-18A7DAE8EC67@digsys.bg> <6028c786-8610-01d9-818e-6f69a2fe9645@ingresso.co.uk> <20200225145346.GA42880@phouka1.phouka.net> <6e329bb8-b96e-fa16-cc73-426685593943@denninger.net> <CAP4Gn9D1==FR8S4O3jJbLXwNEYqffL2L_uhK8yHD2xBzJGemqQ@mail.gmail.com> <CAP4Gn9CqNpyz1S8QfDjm0vwhSVmjYMtk5Rt0Q3fZ=P_7nVMSSA@mail.gmail.com> <CAP4Gn9A=%2BdDxjMiNm-JqdHCRA=x7SgpHiNdzFm=BaPHoH3ByBg@mail.gmail.com> <CAKr6gn1naC73FwG%2BMqW6=6UkDoD4y5MoAAZ9LUNtLDPAFZbdmQ@mail.gmail.com> <CAP4Gn9CmftR6hiJvP0VeO-nz243PQVQ-Ym4zz55HCBgD2Y90Yg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Guys, just a little update: I was able to boot from the HDD, just had to remove the FreeBSD partition from the SSD because the loader always load from the first pool that it founds (I say first because the two installations was on zfs/root, so it never boot the second pool). After one hour of usage the ZFS remains stable, no errors detected. I installed git, npm, node, xorg, xfce4, put some projects and loaded all the node_modules dependencies and after some time deleted some files, reboot twice, add and remove more files and the system have 0 errors... The problem with it on the SSD maybe really related to some lack of a very specific configuration of my part or is a driver parameter/misdetection problem =3D/ If you need more information from the system I can collect! Thank you all for the support, Mario Em ter., 25 de fev. de 2020 =C3=A0s 21:26, Mario Olofo <mario.olofo@gmail.c= om> escreveu: > Hybrid HDD are the norm for notebooks, that is, 1TB hard drive with 16GB > of SSD internal memory for fast writes and hot data (most used pages). > In my case, the notebook came with a ST1000LX015, but the problem happene= d > on the SSD, not on this HDD. > The SSD is a WD Green m.2, Rebecca already posted a link to the model: > https://shop.westerndigital.com/products/internal-drives/wd-green-sata-ss= d#WDS480G2G0B > > Mario > > Em ter., 25 de fev. de 2020 =C3=A0s 21:12, George Michaelson <ggm@algebra= s.org> > escreveu: > >> you said "hybrid HDD" >> >> is this possibly about write-back vs write-through cache integrity and >> some confusion in a driver over what is committed back in disk, and >> what is not? >> >> this feels like a very nasty corner case. Could you be explicit about >> versions and vendors? >> >> I am asking for selfish reasons: I have a lot of dependencies in a >> large SSD backed ZFS postgres server on Dell, and I am about to commit >> to a lenovo X1 Carbon 7/8th gen which would be SSD and almost >> certainly was intended to be ZFS-SSD in FreeBSD. >> >> -George >> >> On Wed, Feb 26, 2020 at 9:22 AM Mario Olofo <mario.olofo@gmail.com> >> wrote: >> > >> > Hello, >> > >> > I reinstalled FreeBSD 12.1 on my SSD (in the swap partition of my Linu= x >> to >> > test) and on my Hybrid HDD. >> > >> > Just configured rc.conf to start my wifi dongle, downoaded git, node a= nd >> > npm via pkg and... as you can see in my screenshot, >> > the ZFS already shows corrupted data... >> > >> > Can't been able to load the FreeBSD from the HDD though, don't know >> why, if >> > someone knows how to load the >> > kernel from the HDD via loader on SSD or grub2, I can try =3D) >> > >> > Mario >> > >> > Em ter., 25 de fev. de 2020 =C3=A0s 20:18, Mario Olofo < >> mario.olofo@gmail.com> >> > escreveu: >> > >> > > Hello, >> > > >> > > I reinstalled FreeBSD 12.1 on my SSD (in the swap partition of my >> Linux to >> > > test) and on my Hybrid HDD. >> > > >> > > Just configured and rc.conf to start my wifi dongle, downoaded git, >> node >> > > and npm via pkg and... as you can see in my screenshot, >> > > the ZFS already shows corrupted data... >> > > >> > > Can't been able to load the FreeBSD from the HDD though, don't know >> why, >> > > if someone direct me how to load the >> > > kernel from the HDD via loader or grub2, I'll try =3D) >> > > >> > > Em ter., 25 de fev. de 2020 =C3=A0s 18:56, Mario Olofo < >> mario.olofo@gmail.com> >> > > escreveu: >> > > >> > >> Hello, >> > >> >> > >> I reinstalled FreeBSD 12.1 on my SSD (in the swap partition of my >> Linux >> > >> to test) and on my Hybrid HDD. >> > >> >> > >> Just configured and rc.conf to start my wifi dongle, downoaded git, >> node >> > >> and npm via pkg and... as you can see in my screenshot, >> > >> the ZFS already shows corrupted data... >> > >> >> > >> Can't been able to load the FreeBSD from the HDD though, don't know >> why, >> > >> if someone direct me how to load the >> > >> kernel from the HDD via loader or grub2, I'll try =3D) >> > >> >> > >> Mario >> > >> >> > >> Em ter., 25 de fev. de 2020 =C3=A0s 12:11, Karl Denninger < >> karl@denninger.net> >> > >> escreveu: >> > >> >> > >>> >> > >>> On 2/25/2020 9:53 AM, John Kennedy wrote: >> > >>> > On Tue, Feb 25, 2020 at 11:07:48AM +0000, Pete French wrote: >> > >>> >> 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 ve= ry >> > >>> quicky. ... >> > >>> > I've always wondered if ZFS (and other snapshotting file >> systems) >> > >>> would help >> > >>> > kill SSD disks by locking up blocks longer than other filesystem= s >> > >>> might. For >> > >>> > example, I've got snapshot-backups going back, say, a year then >> those >> > >>> blocks >> > >>> > that haven't changed aren't going back into the pool to be >> rewritten >> > >>> (and >> > >>> > perhaps favored because of low write-cycle count). As the disk >> fills >> > >>> up, the >> > >>> > blocks that aren't locked up get reused more and more, leading t= o >> > >>> extra wear >> > >>> > on them. Eventually one of those will get to the point of >> erroring >> > >>> out. >> > >>> > >> > >>> > Personally, I just size generously but that isn't always an >> option >> > >>> for >> > >>> > everybody. >> > >>> >> > >>> I have a ZFS RaidZ2 on SSDs that has been running for several /yea= rs >> > >>> /without any problems. The drives are Intel 730s, which Intel >> CLAIMS >> > >>> don't have power-loss protection but in fact appear to; not only d= o >> they >> > >>> have caps in them but in addition they pass a "pull the cord out o= f >> the >> > >>> wall and then check to see if the data is corrupted on restart" >> test on >> > >>> a repeated basis, which I did several times before trusting them. >> > >>> >> > >>> BTW essentially all non-data-center SSDs fail that test and some >> fail it >> > >>> spectacularly (destroying the OS due to some of the in-flight data >> being >> > >>> comingled on an allocated block with something important; if the >> > >>> read/erase/write cycle interrupts you're cooked as the "other" dat= a >> that >> > >>> was not being modified gets destroyed too!) -- the Intels are one >> of the >> > >>> very, very few that have passed it. >> > >>> >> > >>> -- >> > >>> -- Karl Denninger >> > >>> /The Market-Ticker/ >> > >>> S/MIME Email accepted and preferred >> > >>> >> > >> >> > _______________________________________________ >> > freebsd-stable@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> > To unsubscribe, send any mail to " >> freebsd-stable-unsubscribe@freebsd.org" >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAP4Gn9C0OaXA-yxRFmOZfbNpww3vQzFpN8=1vy77gSD_h3OdOw>