Re: FBSD 12.1 - LightDM don't grab keyboard input & Xfce4 window decorator problem
Hello guys, Good news, all the problems are solved! Searching and reading about the upgrade of xorg-server, I did what the installation message says, and the kern.evdev.rcpt_mask=6 was the flag I needed! Long history short, I learned 2 things: 1- RTFM and all messages that pop up 2- The devd was replaced by udev, so evdev with libinput is the default for automatic input detection on X now Thanks for the help! Mario Em qui., 12 de mar. de 2020 às 08:50, Mario Olofo escreveu: > > This depends on how you updated it. I could guess you used >> freebsd-update at some point, but only you can know for sure. >> > > Indeed I did a freebsd-update, but I thought it just update the system to > patch vulnerabilities, not change it to release... > > To check which version of FreeBSD you are using should be possible with >> freebsd-version(1), check it's man page, I'm not using stable versions, >> only releases and current, and I'm not sure what the output is on stable. >> >> Migrating from quarterly to latest is done by configuring pkg, you >> should read the full pkg.conf(5) man page. The EXAMPLES section has >> examples clearly explaining what you are asking for. >> >> > Thank you, I should have take a look on man pages before ask, after the > change, the pkg was updated successfully. > > This all depends on what you did on your system, any suggestion can only >> be generic. You need to know your system condition. >> >> You stated that you mixed binary packages installed via pkg from the >> official repositories with locally built ports. As I said this is not >> really supported, and if you only compiled locally part of Xorg and >> mixed it with quarterly packages you have an high risk of having >> inconsistent binaries on your system. >> >> Check your logs for useful errors. >> > > Yeah, I mixed pkg and ports but after that I removed all ports packages > and reinstalled the pkg version, so the system reverted to a safe/stable > state. > After the change to latest, the pkg upgrade found a lot of files to > update, including xorg-server, xfce and xorg-drivers. > But, after the update to latest, only my usb mouse is detected on xserver > now... > The log don't have any errors, the Xorg log don't have any output about > touchpad and laptop keyboard too. > > The glitch in window titles was fixed after the update, so this is now ok > =). > The only problem now is the keyboard/touchpad in X. > I need to rebuild the kernel too? Any other command I can run to check if > I need something more? > > Thank you > > Mario > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FBSD 12.1 - LightDM don't grab keyboard input & Xfce4 window decorator problem
> This depends on how you updated it. I could guess you used > freebsd-update at some point, but only you can know for sure. > Indeed I did a freebsd-update, but I thought it just update the system to patch vulnerabilities, not change it to release... To check which version of FreeBSD you are using should be possible with > freebsd-version(1), check it's man page, I'm not using stable versions, > only releases and current, and I'm not sure what the output is on stable. > > Migrating from quarterly to latest is done by configuring pkg, you > should read the full pkg.conf(5) man page. The EXAMPLES section has > examples clearly explaining what you are asking for. > > Thank you, I should have take a look on man pages before ask, after the change, the pkg was updated successfully. This all depends on what you did on your system, any suggestion can only > be generic. You need to know your system condition. > > You stated that you mixed binary packages installed via pkg from the > official repositories with locally built ports. As I said this is not > really supported, and if you only compiled locally part of Xorg and > mixed it with quarterly packages you have an high risk of having > inconsistent binaries on your system. > > Check your logs for useful errors. > Yeah, I mixed pkg and ports but after that I removed all ports packages and reinstalled the pkg version, so the system reverted to a safe/stable state. After the change to latest, the pkg upgrade found a lot of files to update, including xorg-server, xfce and xorg-drivers. But, after the update to latest, only my usb mouse is detected on xserver now... The log don't have any errors, the Xorg log don't have any output about touchpad and laptop keyboard too. The glitch in window titles was fixed after the update, so this is now ok =). The only problem now is the keyboard/touchpad in X. I need to rebuild the kernel too? Any other command I can run to check if I need something more? Thank you Mario ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FBSD 12.1 - LightDM don't grab keyboard input & Xfce4 window decorator problem
Hello, I configured the full system with pkg and only build the drm-kmod. I downloaded the img from the 12.0 stable version, don't know when or why it become release for me =X The pkg was downloaded the first time I used it, so I don't know what can be wrong with it. May you point me some link to understand better how to see if i'm in stable/release and how to migrate from quarter to latest? I'll see if I'm in latest and reinstall all with pkg Thank you, Mario Em qua., 11 de mar. de 2020 às 12:24, Guido Falsi escreveu: > On 11/03/20 02:20, Mario Olofo wrote: > > Hello, > > > > @Guido > > I tried to rebuild the xorg-server but it stoped to recognize all input > > devices even on Xfce4, I think I'm missing something. > > Tried to rebuild the xf86-input-evdev too but didn't work either. > > Had to revert to the pkg version to be able to send this email > > Before these rebuilds were you using packages? from quarterly or latest? > > AFAIK mixing packages and locally built packages isn't really supported. > I works most of the time, but there are no warranties. Also it is > especially prone to breaking when building parts that work with hardware > drivers. > > So to properly upgrade your Xorg server if you're coming from quarterly > packages the safe way is to configure your machine to use latest > packages and perform a pkg upgrade. In rare cases you could need pkg > upgrade -f. > > If you want to use ports and have been using packages, only safe way is > to reinstall everything from ports, but I'd really suggest you use > project provided packages or build your own package set using a tool > like poudriere. > > Apart from this, new Xorg changes many things and upgrading only the > server will not be enough anyway. > > Unluckily if you don't perform a proper upgrade it's difficult to tell > if the problem is caused by a bug in some port or induced by some > misalignment on your system software. > > > > > @Ulf Rudolf <mailto:u.rud...@web.de> > > Now knowing that the xorg-server is not recognizing any input devices > > after rebuild the latest version, I have a feeling that this problem is > > related, maybe the LightDM expects some specific device? > > LightDM uses Xorg for it's input, so, no it should work. Have you tried > using "startx" as root to check that Xorg itself works fine? > > -- > Guido Falsi > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FBSD 12.1 - LightDM don't grab keyboard input & Xfce4 window decorator problem
Hello, @Guido I tried to rebuild the xorg-server but it stoped to recognize all input devices even on Xfce4, I think I'm missing something. Tried to rebuild the xf86-input-evdev too but didn't work either. Had to revert to the pkg version to be able to send this email @Ulf Rudolf Now knowing that the xorg-server is not recognizing any input devices after rebuild the latest version, I have a feeling that this problem is related, maybe the LightDM expects some specific device? My system is a Dell G3 2019 with: 12.1-RELEASE-p2 Mesa DRI Intel(R) UHD Graphics 630 (Coffeelake 3x8 GT2) Pkgs: - Xorg 7.7_3 - xorg-server 1.18.4_13,1 (hal is off in the description) - xfce 4.14 Ports: - drm-kmod-g20190710 Thank you, Mario Em ter., 10 de mar. de 2020 às 12:02, Guido Falsi escreveu: > On 10/03/20 13:41, Mario Olofo wrote: > > Hello All, > > In the prccess of making the FreeBSD my main OS, I stumbled on an very > > uncommon problem: the LightDM don't accept any keys, and I can't even get > > out to the tty with ctrl+alt+F1... > > > > I build the drm-kmod from ports, installed Xorg, Xfce4 and LightDM and > > lightdm-gtk-greeter with pkg, and enabled it on rc.conf with > > lightdm_enable="YES". > > On boot, it don't work because the lightdm need to be on video group, so > I > > added it to video groups and then the LightDM screen showed up, but only > > the mouse work. If I press a lot of keys and then use the mouse to > restart > > the system, I can see some garbage input on the first terminal! > > I didn't create a custom X config, but tried to force a input conf to see > > if it was the problem but it appears that the config is not used at all > > when starting LightDM. I rebuild from source the LightDM, but the problem > > persists. When I use startx to go directly to Xfce4 works like a charm. > > > > I'm sorry I don't have much insight about this, but this one (and the > following problem too) looks like a graphics hardware related problem. > > You should share some information about your system, which graphics > adapter and chipset you are using and what driver setup. > > > Then comes the second but less important problem that I found, the topbar > > decorator of windows are not displaying correctly. The background img > > behind the title don't stretch to cover the full width. Anyone had this > > problem before? > > There is a known problem with xfce 4.14 and window decorations on > certain hardware chipsets: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240887 > > It has been recently reported that Xorg server 1.20.7 (available with > the latest package set) fixes the issue. > > This update will reach quarterly packages at the start of April. If > you're willing you could migrate your machine to latest packages and > confirm if this fixes the issue for you. > > -- > Guido Falsi > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
Hi Rebecca, I checked when I had the problem but the machine was up to date. I already solved this problem with the fix in the bugzilla and a lot of help from the great people here to try to narrow down the problem, but the little detail is that the installer wasn't using the ZFS volumes as 4k. So before the setup for partitions I entered the command line, loaded the ZFS driver and added the ashift=12 sysctl to it, so it installed the volumes as 4k, and after that I rebuilt the kernel with the patch (quirks = 0x03) =) Thank you, Mario Em ter., 10 de mar. de 2020 às 17:06, Rebecca Cran escreveu: > > >> On Feb 26, 2020, at 9:20 PM, Warner Losh wrote: > >> > >> On Wed, Feb 26, 2020, 8:54 PM Mario Olofo > wrote: > >> > >> Hello Mark, > >> Yes, I think that it's related to the WD Green SSD. > >> Today I found this bug on FreeBSD's bugzilla: > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225666 > >> Tried to reinstall and recompile the kernel with the patch but it didn't > >> work, I continue to see corrupted data. > >> I think that the only way to be really sure about the corrupted data is > to > >> reinstall again but already boot with the quirks configured, but the > >> kern.cam.ada.X.quirks don't seems to exists on FreeBSD 12, > >> so I have a probability of corruption between installation and > compilation > >> of the patched kernel... > >> Don't know what more to do... > > > > What happens if you disable TRIM? > > Also, have you checked to see if there’s a firmware update available? > > Rebecca > > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FBSD 12.1 - LightDM don't grab keyboard input & Xfce4 window decorator problem
Hello All, In the prccess of making the FreeBSD my main OS, I stumbled on an very uncommon problem: the LightDM don't accept any keys, and I can't even get out to the tty with ctrl+alt+F1... I build the drm-kmod from ports, installed Xorg, Xfce4 and LightDM and lightdm-gtk-greeter with pkg, and enabled it on rc.conf with lightdm_enable="YES". On boot, it don't work because the lightdm need to be on video group, so I added it to video groups and then the LightDM screen showed up, but only the mouse work. If I press a lot of keys and then use the mouse to restart the system, I can see some garbage input on the first terminal! I didn't create a custom X config, but tried to force a input conf to see if it was the problem but it appears that the config is not used at all when starting LightDM. I rebuild from source the LightDM, but the problem persists. When I use startx to go directly to Xfce4 works like a charm. Then comes the second but less important problem that I found, the topbar decorator of windows are not displaying correctly. The background img behind the title don't stretch to cover the full width. Anyone had this problem before? Thank you, Mario ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
Yes, I installed with TRIM on and used the system with it on, but now I expanded the partition, reinstalled and rebuild the kernel with the quirk of broken TRIM to be safe but it appears to not be needed as far as I can tell. Will continue to work on the wifi driver now that the filesystem is stable =) Thank you all! <3 Mario Em dom., 1 de mar. de 2020 às 03:24, Daniel Kalchev escreveu: > Is TRIM still on? > > I understand the quirks patch indicates the drive has some trouble with 4K > aligned writes. If memory serves it I also indicated broken TRIM so to be > safe you need both. > > Daniel > > > > On 29 Feb 2020, at 2:46, Mario Olofo wrote: > > > > Hello guys, a little update that let me more confused > > > > I reinstalled the FreeBSD with 4k pages using the sysctl > > vfs.zfs.min_auto_ashift = 12 and no errors after a lot of stress I put on > > it. > > One thing that I noticed is that with the pool as 4k, the disk fill up > very > > fast, recompiling the kernel used my 8GB space and didn't even completed. > > But now I don't know if the 4k is the correct answer or if this just > delays > > the problem as the pages are bigger. > > > > Mario > > > >> Em sex., 28 de fev. de 2020 às 13:18, Mario Olofo < > mario.ol...@gmail.com> > >> escreveu: > >> > >> Yes, tried 4k quirk but not on install because don't know how to, I did > a > >> clean install then patch and rebuild the kernel, but > >> the volume was already configured for 512bytes, I think I would need to > >> create manually the volume, but don't remember how to anymore xD > >> But I'll search some tutorials and try. From what I saw, the patch > >> suggested on bugzilla got merged into the stable branch, so the quirk > will > >> be > >> detected to use 4k in the installer in a near future. > >> > >> Mario > >> > >> Em sex., 28 de fev. de 2020 às 12:52, Theron > >> escreveu: > >> > >>> On 2020-02-28 09:14, Mario Olofo wrote: > >>>> Thanks! > >>>> > >>>> The only thing that I didn't checked was the questions of Theron, > about > >>>> misaligned data. > >>>> The layout of the disk is as follows: > >>>> > >>>> Disco /dev/sdb: 447,1 GiB, 480113590272 bytes, 937721856 setores > >>>> Unidades: setor de 1 * 512 = 512 bytes > >>>> Tamanho de setor (lógico/físico): 512 bytes / 512 bytes > >>>> Tamanho E/S (mínimo/ótimo): 512 bytes / 512 bytes > >>>> Tipo de rótulo do disco: gpt > >>>> Identificador do disco: D1725E60-D734-4461-90F8-E9EB2376A65A > >>>> > >>>> DispositivoInício Fim Setores Tamanho Tipo > >>>> /dev/sdb12048 1023999 1021952499M Windows ambiente de > >>>> recuperação > >>>> /dev/sdb2 1024000 1228799204800100M Sistema EFI > >>>> /dev/sdb3 1228800 1261567 32768 16M Microsoft reservado > >>>> /dev/sdb4 1261568 532482047 531220480 253,3G Microsoft dados > básico > >>>> /dev/sdb5 532482048 549257215 16775168 8G FreeBSD ZFS > >>>> /dev/sdb6 549257216 937719807 388462592 185,2G Linux sistema de > >>> arquivos > >>>> > >>>> The zfsroot was configured automatically by the installer, so I think > >>> that > >>>> it align the volume automaticaly right? > >>>> > >>>> Mario > >>> > >>> Yes, I don't see any potential alignment issue here. I would wonder if > >>> this drive is misrepresenting its physical sector size, deceiving ZFS > >>> and the SATA driver into making small writes that the drive does not > >>> actually support, but it looks like you may have already tried the > >>> relevant workaround: > >>> > >>> On 2020-02-27 23:44, Mario Olofo wrote: > >>>> Maybe the problem really is a combination of factors, for the person > >>> that > >>>> filed a bug on bugzilla the fix was setting the quirks 4k and > >>> broken_trim, > >>>> but for me the real block size is 512bytes and only setting the flag > >>>> broken_trim didn't help... > >>>> > >>>> Mario > >>> Did you try 4k quirk ? > >>> > >>> Theron > >>> > >> > > ___ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org > " > > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
Hello, sorry my lack of vocabulary and thanks for the clarification I think that it's a waste of space for me, and I'm afraid that this empty space is making the problem just less frequent. I remember that many years ago I implemented a FFS for an embedded system, and the SD Card was 4k "aligned", with the smallest block being 512 bytes. The only difference really is when I write/read from it, I have to align the command to request x blocks starting at some 4k aligned address, even if I just want 1 block. As the system had a lot of small files, I did the FFS on top of this as 1k sectors, I hoped that the ZFS could do something like that (ie. read/write every 4k but with 1k sectors). Mario Em sáb., 29 de fev. de 2020 às 01:54, Chris escreveu: > On Fri, 28 Feb 2020 21:44:45 -0300 Mario Olofo mario.ol...@gmail.com said > > > Hello guys, a little update that let me more confused > > > > I reinstalled the FreeBSD with 4k pages using the sysctl > > vfs.zfs.min_auto_ashift = 12 and no errors after a lot of stress I put on > > it. > > One thing that I noticed is that with the pool as 4k, the disk fill up > very > > fast, recompiling the kernel used my 8GB space and didn't even completed. > > But now I don't know if the 4k is the correct answer or if this just > delays > > the problem as the pages are bigger. > The TLDR of 4k vs 512 largely has to do with the size of the files going > onto your medium. Many files of a smaller size fit better on a 512 > boundary. > Whereas larger mp3s or archives fair better on a 4k boundary. BTW these are > called SECTOR sizes. Not pages. :) 4k blocks typically read faster, than > the > 512 blocks (sectors). Because more data can be consumed in one read/write. > So really, your going to have to decide how best to "tune" your disk to > best > suite it's intended use. Many small files. Or big files, and storage. > > HTH > > --Chris > FreeBSD 14.0-FUTURE #0.000 cray256 > > > > Mario > > > > Em sex., 28 de fev. de 2020 às 13:18, Mario Olofo > > > escreveu: > > > > > Yes, tried 4k quirk but not on install because don't know how to, I > did a > > > clean install then patch and rebuild the kernel, but > > > the volume was already configured for 512bytes, I think I would need to > > > create manually the volume, but don't remember how to anymore xD > > > But I'll search some tutorials and try. From what I saw, the patch > > > suggested on bugzilla got merged into the stable branch, so the quirk > will > > > be > > > detected to use 4k in the installer in a near future. > > > > > > Mario > > > > > > Em sex., 28 de fev. de 2020 às 12:52, Theron > > > escreveu: > > > > > >> On 2020-02-28 09:14, Mario Olofo wrote: > > >> > Thanks! > > >> > > > >> > The only thing that I didn't checked was the questions of Theron, > about > > >> > misaligned data. > > >> > The layout of the disk is as follows: > > >> > > > >> > Disco /dev/sdb: 447,1 GiB, 480113590272 bytes, 937721856 setores > > >> > Unidades: setor de 1 * 512 = 512 bytes > > >> > Tamanho de setor (lógico/físico): 512 bytes / 512 bytes > > >> > Tamanho E/S (mínimo/ótimo): 512 bytes / 512 bytes > > >> > Tipo de rótulo do disco: gpt > > >> > Identificador do disco: D1725E60-D734-4461-90F8-E9EB2376A65A > > >> > > > >> > DispositivoInício Fim Setores Tamanho Tipo > > >> > /dev/sdb12048 1023999 1021952499M Windows ambiente > de > > >> > recuperação > > >> > /dev/sdb2 1024000 1228799204800100M Sistema EFI > > >> > /dev/sdb3 1228800 1261567 32768 16M Microsoft > reservado > > >> > /dev/sdb4 1261568 532482047 531220480 253,3G Microsoft dados > básico > > >> > /dev/sdb5 532482048 549257215 16775168 8G FreeBSD ZFS > > >> > /dev/sdb6 549257216 937719807 388462592 185,2G Linux sistema de > > >> arquivos > > >> > > > >> > The zfsroot was configured automatically by the installer, so I > think > > >> that > > >> > it align the volume automaticaly right? > > >> > > > >> > Mario > > >> > > >> Yes, I don't see any potential alignment issue here. I would wonder > if > > >> this drive is misrepresenting its physical sector size, deceiving ZFS > > >> and the SATA driver into making small writes tha
Re: Running FreeBSD on M.2 SSD
Hello guys, a little update that let me more confused I reinstalled the FreeBSD with 4k pages using the sysctl vfs.zfs.min_auto_ashift = 12 and no errors after a lot of stress I put on it. One thing that I noticed is that with the pool as 4k, the disk fill up very fast, recompiling the kernel used my 8GB space and didn't even completed. But now I don't know if the 4k is the correct answer or if this just delays the problem as the pages are bigger. Mario Em sex., 28 de fev. de 2020 às 13:18, Mario Olofo escreveu: > Yes, tried 4k quirk but not on install because don't know how to, I did a > clean install then patch and rebuild the kernel, but > the volume was already configured for 512bytes, I think I would need to > create manually the volume, but don't remember how to anymore xD > But I'll search some tutorials and try. From what I saw, the patch > suggested on bugzilla got merged into the stable branch, so the quirk will > be > detected to use 4k in the installer in a near future. > > Mario > > Em sex., 28 de fev. de 2020 às 12:52, Theron > escreveu: > >> On 2020-02-28 09:14, Mario Olofo wrote: >> > Thanks! >> > >> > The only thing that I didn't checked was the questions of Theron, about >> > misaligned data. >> > The layout of the disk is as follows: >> > >> > Disco /dev/sdb: 447,1 GiB, 480113590272 bytes, 937721856 setores >> > Unidades: setor de 1 * 512 = 512 bytes >> > Tamanho de setor (lógico/físico): 512 bytes / 512 bytes >> > Tamanho E/S (mínimo/ótimo): 512 bytes / 512 bytes >> > Tipo de rótulo do disco: gpt >> > Identificador do disco: D1725E60-D734-4461-90F8-E9EB2376A65A >> > >> > DispositivoInício Fim Setores Tamanho Tipo >> > /dev/sdb12048 1023999 1021952499M Windows ambiente de >> > recuperação >> > /dev/sdb2 1024000 1228799204800100M Sistema EFI >> > /dev/sdb3 1228800 1261567 32768 16M Microsoft reservado >> > /dev/sdb4 1261568 532482047 531220480 253,3G Microsoft dados básico >> > /dev/sdb5 532482048 549257215 16775168 8G FreeBSD ZFS >> > /dev/sdb6 549257216 937719807 388462592 185,2G Linux sistema de >> arquivos >> > >> > The zfsroot was configured automatically by the installer, so I think >> that >> > it align the volume automaticaly right? >> > >> > Mario >> >> Yes, I don't see any potential alignment issue here. I would wonder if >> this drive is misrepresenting its physical sector size, deceiving ZFS >> and the SATA driver into making small writes that the drive does not >> actually support, but it looks like you may have already tried the >> relevant workaround: >> >> On 2020-02-27 23:44, Mario Olofo wrote: >> > Maybe the problem really is a combination of factors, for the person >> that >> > filed a bug on bugzilla the fix was setting the quirks 4k and >> broken_trim, >> > but for me the real block size is 512bytes and only setting the flag >> > broken_trim didn't help... >> > >> > Mario >> Did you try 4k quirk ? >> >> Theron >> > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
Yes, tried 4k quirk but not on install because don't know how to, I did a clean install then patch and rebuild the kernel, but the volume was already configured for 512bytes, I think I would need to create manually the volume, but don't remember how to anymore xD But I'll search some tutorials and try. From what I saw, the patch suggested on bugzilla got merged into the stable branch, so the quirk will be detected to use 4k in the installer in a near future. Mario Em sex., 28 de fev. de 2020 às 12:52, Theron escreveu: > On 2020-02-28 09:14, Mario Olofo wrote: > > Thanks! > > > > The only thing that I didn't checked was the questions of Theron, about > > misaligned data. > > The layout of the disk is as follows: > > > > Disco /dev/sdb: 447,1 GiB, 480113590272 bytes, 937721856 setores > > Unidades: setor de 1 * 512 = 512 bytes > > Tamanho de setor (lógico/físico): 512 bytes / 512 bytes > > Tamanho E/S (mínimo/ótimo): 512 bytes / 512 bytes > > Tipo de rótulo do disco: gpt > > Identificador do disco: D1725E60-D734-4461-90F8-E9EB2376A65A > > > > DispositivoInício Fim Setores Tamanho Tipo > > /dev/sdb12048 1023999 1021952499M Windows ambiente de > > recuperação > > /dev/sdb2 1024000 1228799204800100M Sistema EFI > > /dev/sdb3 1228800 1261567 32768 16M Microsoft reservado > > /dev/sdb4 1261568 532482047 531220480 253,3G Microsoft dados básico > > /dev/sdb5 532482048 549257215 16775168 8G FreeBSD ZFS > > /dev/sdb6 549257216 937719807 388462592 185,2G Linux sistema de > arquivos > > > > The zfsroot was configured automatically by the installer, so I think > that > > it align the volume automaticaly right? > > > > Mario > > Yes, I don't see any potential alignment issue here. I would wonder if > this drive is misrepresenting its physical sector size, deceiving ZFS > and the SATA driver into making small writes that the drive does not > actually support, but it looks like you may have already tried the > relevant workaround: > > On 2020-02-27 23:44, Mario Olofo wrote: > > Maybe the problem really is a combination of factors, for the person that > > filed a bug on bugzilla the fix was setting the quirks 4k and > broken_trim, > > but for me the real block size is 512bytes and only setting the flag > > broken_trim didn't help... > > > > Mario > Did you try 4k quirk ? > > Theron > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
Thanks! The only thing that I didn't checked was the questions of Theron, about misaligned data. The layout of the disk is as follows: Disco /dev/sdb: 447,1 GiB, 480113590272 bytes, 937721856 setores Unidades: setor de 1 * 512 = 512 bytes Tamanho de setor (lógico/físico): 512 bytes / 512 bytes Tamanho E/S (mínimo/ótimo): 512 bytes / 512 bytes Tipo de rótulo do disco: gpt Identificador do disco: D1725E60-D734-4461-90F8-E9EB2376A65A DispositivoInício Fim Setores Tamanho Tipo /dev/sdb12048 1023999 1021952499M Windows ambiente de recuperação /dev/sdb2 1024000 1228799204800100M Sistema EFI /dev/sdb3 1228800 1261567 32768 16M Microsoft reservado /dev/sdb4 1261568 532482047 531220480 253,3G Microsoft dados básico /dev/sdb5 532482048 549257215 16775168 8G FreeBSD ZFS /dev/sdb6 549257216 937719807 388462592 185,2G Linux sistema de arquivos The zfsroot was configured automatically by the installer, so I think that it align the volume automaticaly right? Mario Em sex., 28 de fev. de 2020 às 03:04, Pete Wright escreveu: > > > On 2020-02-27 20:44, Mario Olofo wrote: > > Thanks for the update. > > > > May you share what quirks was detected for your card and firmware to > > see if it matches mine? > > The only way I was able to run FreeBSD 12-STABLE on the SSD was using > > the suggested sysctl vfs.zfs.trim.enabled=0 > > Maybe the problem really is a combination of factors, for the person > > that filed a bug on bugzilla the fix was setting the quirks 4k and > > broken_trim, but for me the real block size is 512bytes and only > > setting the flag broken_trim didn't help... > > > This is a default install off of the latest 12.1-STABLE snapshot, no > special loader or sysctl knobs used. dmesg doesn't show anything > interesting: > > $ dmesg|grep ada > ses0: pass0,ada0 in 'Slot 00', SATA Slot: scbus0 target 0 > ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 > ada0: ACS-2 ATA SATA 3.x device > ada0: Serial Number 185243800880 > ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes) > ada0: Command Queueing enabled > ada0: 457872MB (937721856 512 byte sectors) > GEOM_ELI: Device ada0p4.eli created. > > here's the output of sysctl: > $ sysctl kern.cam.ada > kern.cam.ada.0.sort_io_queue: 0 > kern.cam.ada.0.max_seq_zones: 0 > kern.cam.ada.0.optimal_nonseq_zones: 0 > kern.cam.ada.0.optimal_seq_zones: 0 > kern.cam.ada.0.zone_support: None > kern.cam.ada.0.zone_mode: Not Zoned > kern.cam.ada.0.rotating: 0 > kern.cam.ada.0.unmapped_io: 1 > kern.cam.ada.0.write_cache: -1 > kern.cam.ada.0.read_ahead: -1 > kern.cam.ada.0.delete_method: DSM_TRIM > kern.cam.ada.write_cache: 1 > kern.cam.ada.read_ahead: 1 > kern.cam.ada.spindown_suspend: 1 > kern.cam.ada.spindown_shutdown: 1 > kern.cam.ada.send_ordered: 1 > kern.cam.ada.default_timeout: 30 > kern.cam.ada.retry_count: 4 > > cheers, > -pete > > -- > Pete Wright > p...@nomadlogic.org > @nomadlogicLA > > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
Thanks for the update. May you share what quirks was detected for your card and firmware to see if it matches mine? The only way I was able to run FreeBSD 12-STABLE on the SSD was using the suggested sysctl vfs.zfs.trim.enabled=0 Maybe the problem really is a combination of factors, for the person that filed a bug on bugzilla the fix was setting the quirks 4k and broken_trim, but for me the real block size is 512bytes and only setting the flag broken_trim didn't help... Mario Em sex., 28 de fev. de 2020 às 00:58, Pete Wright escreveu: > > > On 2/24/20 11:13 AM, Mario Olofo wrote: > > Hi Pete, > > The nvmecontrol devlist don't found any devices. > pciconf -lv nvme0 didn't found anything either. > > The camcontrol devlist output was as follows: > > root@~ # camcontrol devlist > at scbus0 target 0 lun 0 (ada0,pass0) > at scbus1 target 0 lun 0 (ada1,pass1) > at scbus2 target 0 lun 0 (pass2,da0) > > > just wanted to provide an update here. so i had a system that needed a > new root drive and figured that the price of this device was worth a shot. > i figured if it has issues it'd be a good opportunity to help find the root > cause and fix them. so anyway...i got the drive today and i am not seeing > any issues with it so far. here's the device on my end: > > $ sudo camcontrol devlist > at scbus0 target 0 lun 0 (ada0,pass0) >at scbus2 target 0 lun 0 (ses0,pass1) > $ > > i am running 12-STABLE, with an encrypted zfsroot device. i've pumped > about 10gigs through it so far restoring my homedir with no issues, and zfs > scrub has run without any corrupted blocks detected. > > so i don't think it's an issue with this specific m.2 device, perhaps > there is something odd happening in your local env though that is causing > this issue to crop up. > > -pete > > -- > Pete wrightp...@nomadlogic.org > @nomadlogicLA > > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
Hello Daniel, Indeed setting the sysctl variable on install and after that on loader.conf appears to solve the data corruption problem =O Did the same as before, install git, node, npm, etc and all good. I will build the kernel and install xorg and xfce to use more disk space and see if some problem shows up Thank you, Mario Em qui., 27 de fev. de 2020 às 10:41, Daniel Kalchev escreveu: > Like I wrote earlier: > > sysctl vfs.zfs.trim.enabled=0 > > is your friend. > > Best to do this before installing and put vfs.zfs.trim.enabled=0 in > /boot/loader.conf in the boot drive to permanently have it. > > Daniel > > > On 27 Feb 2020, at 14:19, Mario Olofo wrote: > > > > This was supposed to be disabled by the quirk 0x02 > (ADA_Q_NCQ_TRIM_BROKEN) > > right? > > There's some command to disable trim on installer boot and then > permanently > > after the install? > > > > Mario > > > > > > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
This was supposed to be disabled by the quirk 0x02 (ADA_Q_NCQ_TRIM_BROKEN) right? There's some command to disable trim on installer boot and then permanently after the install? Mario Em qui., 27 de fev. de 2020 às 01:20, Warner Losh escreveu: > > > On Wed, Feb 26, 2020, 8:54 PM Mario Olofo wrote: > >> Hello Mark, >> >> Yes, I think that it's related to the WD Green SSD. >> Today I found this bug on FreeBSD's bugzilla: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225666 >> >> Tried to reinstall and recompile the kernel with the patch but it didn't >> work, I continue to see corrupted data. >> I think that the only way to be really sure about the corrupted data is to >> reinstall again but already boot with the quirks configured, but the >> kern.cam.ada.X.quirks don't seems to exists on FreeBSD 12, >> so I have a probability of corruption between installation and compilation >> of the patched kernel... >> >> Don't know what more to do... >> > > What happens if you disable TRIM? > > Warner > >> >> Mario >> >> Em qua., 26 de fev. de 2020 às 20:48, Mark Linimon >> escreveu: >> >> > On Tue, Feb 25, 2020 at 08:18:51PM -0300, Mario Olofo wrote: >> > > the ZFS already shows corrupted data... >> > >> > Although this may have already been stated in the thread and I missed >> it, >> > I have not had similar problems with the NVME chips I have used (first >> an >> > HP, and now a Samsung). I am really starting to wonder if this is >> > hardware- >> > specific. >> > >> > mcl >> > >> ___ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" >> > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
Hello Mark, Yes, I think that it's related to the WD Green SSD. Today I found this bug on FreeBSD's bugzilla: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225666 Tried to reinstall and recompile the kernel with the patch but it didn't work, I continue to see corrupted data. I think that the only way to be really sure about the corrupted data is to reinstall again but already boot with the quirks configured, but the kern.cam.ada.X.quirks don't seems to exists on FreeBSD 12, so I have a probability of corruption between installation and compilation of the patched kernel... Don't know what more to do... Mario Em qua., 26 de fev. de 2020 às 20:48, Mark Linimon escreveu: > On Tue, Feb 25, 2020 at 08:18:51PM -0300, Mario Olofo wrote: > > the ZFS already shows corrupted data... > > Although this may have already been stated in the thread and I missed it, > I have not had similar problems with the NVME chips I have used (first an > HP, and now a Samsung). I am really starting to wonder if this is > hardware- > specific. > > mcl > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
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 =) Em ter., 25 de fev. de 2020 às 18:56, Mario Olofo 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 =) > > Mario > > Em ter., 25 de fev. de 2020 às 12:11, Karl Denninger > escreveu: > >> >> On 2/25/2020 9:53 AM, John Kennedy wrote: >> > On Tue, Feb 25, 2020 at 11:07:48AM +, 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 very >> quicky. ... >> >I've always wondered if ZFS (and other snapshotting file systems) >> would help >> > kill SSD disks by locking up blocks longer than other filesystems >> 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 to 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 /years >> /without any problems. The drives are Intel 730s, which Intel CLAIMS >> don't have power-loss protection but in fact appear to; not only do they >> have caps in them but in addition they pass a "pull the cord out of 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" data 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-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
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 =) Mario Em ter., 25 de fev. de 2020 às 12:11, Karl Denninger escreveu: > > On 2/25/2020 9:53 AM, John Kennedy wrote: > > On Tue, Feb 25, 2020 at 11:07:48AM +, 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 very > quicky. ... > >I've always wondered if ZFS (and other snapshotting file systems) > would help > > kill SSD disks by locking up blocks longer than other filesystems > 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 to 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 /years > /without any problems. The drives are Intel 730s, which Intel CLAIMS > don't have power-loss protection but in fact appear to; not only do they > have caps in them but in addition they pass a "pull the cord out of 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" data 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-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
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 =/ 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 às 21:26, Mario Olofo 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 happened > 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-ssd#WDS480G2G0B > > Mario > > Em ter., 25 de fev. de 2020 às 21:12, George Michaelson > 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 >> wrote: >> > >> > 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 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 knows how to load the >> > kernel from the HDD via loader on SSD or grub2, I can try =) >> > >> > Mario >> > >> > Em ter., 25 de fev. de 2020 às 20:18, Mario Olofo < >> mario.ol...@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 =) >> > > >> > > Em ter., 25 de fev. de 2020 às 18:56, Mario Olofo < >> mario.ol...@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 =) >> > >> >> > >> Mario >> > >> >> > >> Em ter., 25 de fev. de 2020 às 12:11, Karl Denninger < >> k...@denninger.net> >> > >> escreveu: >> > >> >> > >>> >> > >>> On 2/25/2020 9:53 AM, John Kennedy wrote: >> > >>> > On Tue,
Re: Running FreeBSD on M.2 SSD
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 happened 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-ssd#WDS480G2G0B Mario Em ter., 25 de fev. de 2020 às 21:12, George Michaelson 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 wrote: > > > > 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 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 knows how to load the > > kernel from the HDD via loader on SSD or grub2, I can try =) > > > > Mario > > > > Em ter., 25 de fev. de 2020 às 20:18, Mario Olofo > > > 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 =) > > > > > > Em ter., 25 de fev. de 2020 às 18:56, Mario Olofo < > mario.ol...@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 =) > > >> > > >> Mario > > >> > > >> Em ter., 25 de fev. de 2020 às 12:11, Karl Denninger < > k...@denninger.net> > > >> escreveu: > > >> > > >>> > > >>> On 2/25/2020 9:53 AM, John Kennedy wrote: > > >>> > On Tue, Feb 25, 2020 at 11:07:48AM +, 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 very > > >>> quicky. ... > > >>> >I've always wondered if ZFS (and other snapshotting file > systems) > > >>> would help > > >>> > kill SSD disks by locking up blocks longer than other filesystems > > >>> 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 to > > >>> extra wear > > >>> > on them. Eventually one of those will get to the point of erroring > > >>> out. > > >>> > > > >>> >Persona
Re: Running FreeBSD on M.2 SSD
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 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 knows how to load the kernel from the HDD via loader on SSD or grub2, I can try =) Mario Em ter., 25 de fev. de 2020 às 20:18, Mario Olofo 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 =) > > Em ter., 25 de fev. de 2020 às 18:56, Mario Olofo > 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 =) >> >> Mario >> >> Em ter., 25 de fev. de 2020 às 12:11, Karl Denninger >> escreveu: >> >>> >>> On 2/25/2020 9:53 AM, John Kennedy wrote: >>> > On Tue, Feb 25, 2020 at 11:07:48AM +, 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 very >>> quicky. ... >>> >I've always wondered if ZFS (and other snapshotting file systems) >>> would help >>> > kill SSD disks by locking up blocks longer than other filesystems >>> 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 to >>> 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 /years >>> /without any problems. The drives are Intel 730s, which Intel CLAIMS >>> don't have power-loss protection but in fact appear to; not only do they >>> have caps in them but in addition they pass a "pull the cord out of 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" data 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-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
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 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@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
Hi Mike, thanks for the insight. I tried both, but not at the same time. When I found that the ZFS was corrupting the filesystem, I reinstalled the FreeBSD using UFS but no luck. Ulf told me that he had the same problem and it turned out the problem was a defective RAM, but here I just ran the test 2 times, one from Dell BIOS Diagnostics Tool and other from mdsched.exe from Windos 10, but here the RAM is ok... Thank you again, Mario Em seg., 24 de fev. de 2020 às 22:15, Mike Karels escreveu: > Mario, have you ruled out the possibility that the UFS and ZFS filesystems > are overlapping? It would be worth a careful check of the partition table > and filesystem sizes. You can check the actual UFS size with dumpfs. > I ask in part because UFS has a tendency to write to the last cylinder > group. > > Also, are you sure you want to use both UFS and ZFS? I do it personally > for historical reasons, but on a larger machine with several disks. But > there are reasons not to use both, including different memory cache > strategies. > > Mike > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
Old_age Offline - 4632 242 Total_Host_GB_Read 0x0030 100 100 000Old_age Offline - 4956 244 Temp_Throttle_Status0x0032 000 100 ---Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_DescriptionStatus Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Aborted by host 90% 3166 - # 2 Short offline Completed without error 00% 2522 - # 3 Short offline Interrupted (host reset) 90% 2070 - # 4 Short offline Interrupted (host reset) 90% 2040 - # 5 Short offline Interrupted (host reset) 90% 2011 - # 6 Short offline Interrupted (host reset) 90% 2011 - # 7 Short offline Aborted by host 80% 2011 - # 8 Short offline Completed without error 00% 624 - # 9 Short offline Aborted by host 30% 433 - #10 Short offline Aborted by host 90% 401 - #11 Short offline Completed without error 00% 400 - #12 Short offline Completed without error 00% 321 - #13 Short offline Completed without error 00% 106 - #14 Short offline Self-test routine in progress 20% 106 - #15 Short offline Aborted by host 90%11 - Selective Self-tests/Logging not supported Em seg., 24 de fev. de 2020 às 16:50, Matt Garber escreveu: > On Mon, Feb 24, 2020 at 2:44 PM Mario Olofo wrote: > >> Hi Pete, in the logs there's nothing wrong, I only see the problem on >> zpool >> status after the first scrub, even if I just >> reinstall the FreeBSD and some basic packages (didn't even need a lot of >> files as I thought). > > > Mario, > > Out of curiosity, how are you able to tell for sure you aren’t also > experiencing corruption under Linux or Windows on the same hardware? Have > you been able to run a ZFS scrub using ZFS on Linux? > > Both default file systems, ext4 and NTFS, are completely unable of letting > you know if corruption has occurred — they’ll just corrupt silently — so > I’m wondering how you’ve ruled that out. > > > Thanks, > — > Matt > > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
Hi Pete, in the logs there's nothing wrong, I only see the problem on zpool status after the first scrub, even if I just reinstall the FreeBSD and some basic packages (didn't even need a lot of files as I thought). Hello Rebecca, indeed is this model I'm using, the SATA versions is cheaper so I installed this. My notebook is a Dell G3 i5 8th gen, the original disk is the hybrid HDD detected as ST1000LX015. Mario Em seg., 24 de fev. de 2020 às 16:36, Rebecca Cran escreveu: > On 2/24/20 12:13 PM, Mario Olofo wrote: > > > root@~ # camcontrol devlist > > at scbus0 target 0 lun 0 (ada0,pass0) > > at scbus1 target 0 lun 0 (ada1,pass1) > > at scbus2 target 0 lun 0 (pass2,da0) > > Ok, so it's a SATA M.2 SSD - one of these: > > https://shop.westerndigital.com/products/internal-drives/wd-green-sata-ssd#WDS480G2G0B > > > -- > Rebecca Cran > > > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
Hi Pete, The nvmecontrol devlist don't found any devices. pciconf -lv nvme0 didn't found anything either. The camcontrol devlist output was as follows: root@~ # camcontrol devlist at scbus0 target 0 lun 0 (ada0,pass0) at scbus1 target 0 lun 0 (ada1,pass1) at scbus2 target 0 lun 0 (pass2,da0) The dmesg | grep ada1 shows the following: Feb 24 18:54:31 kernel: ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 Feb 24 18:54:31 kernel: ada1: ACS-2 ATA SATA 3.x device Feb 24 18:54:31 kernel: ada1: Serial Number 183541800480 Feb 24 18:54:31 kernel: ada1: 600.00MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes) Feb 24 18:54:31 kernel: ada1: Command Queueing enabled Feb 24 18:54:31 kernel: ada1:457872MB (937721856 512 byte sectors) Mario Em seg., 24 de fev. de 2020 às 15:27, Pete Wright escreveu: > > > On 2020-02-24 09:58, Mario Olofo wrote: > > Hello John, thank you for your reply. > > > > Yesterday I reinstalled the 12.1 on a VirtualBox virtual machine, did the > > same steps and it didn't corrupted the ZFS, so I think that the problem > is > > in the FreeBSD's driver for m.2 SSD. > > Besides the corruption of the filesystem, I forgot to mention that I > > noticed a little noise on disk writes on FreeBSD, but not on Linux or > > Windows. > > I found some old threads about incorrectly params for sector size for > > Samsung's SSD, but nothing about WD. > > If someone responsible for the driver need help to solve this problem, I > > can reinstall the FreeBSD on my machine and compile a custom kernel to > > gather debug information. > > Unfortunately you haven't provided much in details regarding the > hardware you are running as far as FreeBSD see's it. I can confirm I > have had many systems using m.2 for quite a while and have had zero > issues. Could you provide some of these details? > > (assuming this is an NVMe device): > $ sudo nvmecontrol devlist > $ sudo pciconf -lv nvme0 > > if your device isn't NVMe and is a sata device then this info may be > helpful as well: > $ sudo camcontrol devlist > > and your dmesg will also probably be helpful here as well. I think > getting at least this basic info will help determine where the issue is > cropping up. > > cheers, > -pete > > -- > Pete Wright > p...@nomadlogic.org > @nomadlogicLA > > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
Hello John, thank you for your reply. Yesterday I reinstalled the 12.1 on a VirtualBox virtual machine, did the same steps and it didn't corrupted the ZFS, so I think that the problem is in the FreeBSD's driver for m.2 SSD. Besides the corruption of the filesystem, I forgot to mention that I noticed a little noise on disk writes on FreeBSD, but not on Linux or Windows. I found some old threads about incorrectly params for sector size for Samsung's SSD, but nothing about WD. If someone responsible for the driver need help to solve this problem, I can reinstall the FreeBSD on my machine and compile a custom kernel to gather debug information. Thank you, Mario Em seg., 24 de fev. de 2020 às 11:47, John Kennedy escreveu: > On Sun, Feb 23, 2020 at 11:18:08PM -0300, Mario Olofo wrote: > > Some time ago I tried to switch from Linux to FreeBSD 12.1, used a WiFi > > dongle and all good, until I found that both ZFS and UFS corrupted the > > filesystem very fast. > > I work with a lot of small files because of web programming > (node_modules), > > so after a clean install, after installing the dependencies for my > project, > > if I scrub the zpool, it always found that the system is corrupted and > > never recover. > > > > I have a WD Green M.2 SSD 480GB WDS480G2G0B. > > Both Linux and Windows work correctly and don't detect any problems with > > the disk. > > > > Did someone knows if it isn't supported by FreeBSD or there's some > specific > > configuration params that I need to set to it work correctly? > > > > I made a post on the forums back in the day I had the problem, the logs I > > had are all there: > > > https://forums.freebsd.org/threads/fixing-metadata-errors-after-zfs-clear-zfs-scrub.72139/ > > > Can't answer your WD Green question specifically, but I'm happy with my > setup, below. Good to look for quirks, but you probably also want to list > other hardware involved as well (which might have it's own quirks). If > you've > had good success (and no corruption) with two other operating systems on > the > same hardware, I'd probably be looking at software and/or drivers, and that > requires knowledge of the hardware. > > > I've got dual EVOs (below is just from one I'm typing on) on two > different > FreeBSD boxes. Nothing specific I had to do in FreeBSD, although on the > other > motherboard I had to tweak the motherboard settings to give it the > channels it > needed to shine. > > kernel: nvd0: NVMe namespace > kernel: nvd0: 476940MB (976773168 512 byte sectors) > kernel: nvd1: NVMe namespace > kernel: nvd1: 476940MB (976773168 512 byte sectors) > > If compiling kernel and packages from source count as having lots of > little > files, then I do as well. I think I'm ZFS everywhere (boot partition being > the question over time). > > Personally, the only ZFS corruption I've had over time has been caused by > bad hardware. When I moved the disks to another box, they were fine with > the same version of FreeBSD. I scrub my zpool about once a month just > because, > plus after I get the kernel to crash. > > The original box went all the way back to root-on-ZFS + FreeBSD 11. The > newer box just started around 12.0 (2019-05-31). > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Running FreeBSD on M.2 SSD
Hello guys, Some time ago I tried to switch from Linux to FreeBSD 12.1, used a WiFi dongle and all good, until I found that both ZFS and UFS corrupted the filesystem very fast. I work with a lot of small files because of web programming (node_modules), so after a clean install, after installing the dependencies for my project, if I scrub the zpool, it always found that the system is corrupted and never recover. I have a WD Green M.2 SSD 480GB WDS480G2G0B. Both Linux and Windows work correctly and don't detect any problems with the disk. Did someone knows if it isn't supported by FreeBSD or there's some specific configuration params that I need to set to it work correctly? I made a post on the forums back in the day I had the problem, the logs I had are all there: https://forums.freebsd.org/threads/fixing-metadata-errors-after-zfs-clear-zfs-scrub.72139/ Thank you, Mario ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS - Problem removing files after changing the compression type
Hello, In the logs I don't have any output about problems with the filesystem. Indeed I had a corrupted file after learning about the zpool status -v, but the ones that I can't delete didn't show up. Searching on the web I found that running the command #echo > /path/to/undetelable/file seems to fix the file to become deletable, but Im not sure why the file was stuck in the first place... Taking advantage of the opportunity, where is the best place I can seek advice to solve issues with 3D acceleration with Intel while I have this notebook with Optimus? Thank you for the pacience, Best regards, Mario Em qua, 5 de jun de 2019 às 10:34, Dean E. Weimer escreveu: > On 2019-06-05 8:14 am, Mario Olofo wrote: > > Hello guys, > > > > I'm configuring a new installation of FreeBSD-12.0-RELEASE and > > installed > > with ZFS for the root file system. > > I run the command zfs set compression=lz4 root, and after this, the > > system > > become a little weird. > > I tried to test some npm install to see if the compression was working > > and > > it is, but when I try to run some commands (ie. ng serve), it fails > > with > > I/O error. > > Deleted the node_modules directory and when I tried to delete the .npm > > dir, > > the system returns "Directory not empty". > > When run as sudo rm -rf, the result is "Unknown error: 122" > > > > I did something that I was not supposed to? > > In the btrfs one can change the compression on the fly without issues > > because of metadata, don't know if zfs behaves this way too. > > > > My system is a Dell G3, with a i5 8gen and an SSD on the m.2 slot > > running > > the FreeBSD (on UFS the notebook freezes and halt when I run npm > > install). > > Gentoo and Windows running on the same SSD and it's all good. > > > > Thank you, > > Best reggards, > > > > Mario > > You should be able to change ZFS compression on the fly. Old data > already written is not changed, but new writes will use the new > compression setting. I have done this before, It looks like something > else is happening I don't think the issue is related to the ZFS > compression setting. I am not familiar with npm, so I have no idea whats > going on there. Look at your dmesg output and check logs to see if the > system logged any disk access errors also check status of zpool with > zpool status. > > -- > Thanks, > Dean E. Weimer > http://www.dweimer.net/ > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ZFS - Problem removing files after changing the compression type
Hello guys, I'm configuring a new installation of FreeBSD-12.0-RELEASE and installed with ZFS for the root file system. I run the command zfs set compression=lz4 root, and after this, the system become a little weird. I tried to test some npm install to see if the compression was working and it is, but when I try to run some commands (ie. ng serve), it fails with I/O error. Deleted the node_modules directory and when I tried to delete the .npm dir, the system returns "Directory not empty". When run as sudo rm -rf, the result is "Unknown error: 122" I did something that I was not supposed to? In the btrfs one can change the compression on the fly without issues because of metadata, don't know if zfs behaves this way too. My system is a Dell G3, with a i5 8gen and an SSD on the m.2 slot running the FreeBSD (on UFS the notebook freezes and halt when I run npm install). Gentoo and Windows running on the same SSD and it's all good. Thank you, Best reggards, Mario ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
