Re: Question about 'gptzfsboot'
On 2019-04-29 15:24, Ian Lepore wrote: > > I can't say anything at all about drm or other video driver issues, I'm > just not knowledgeable about that stuff at all. > > The only thing I was getting at was that the changes I made in r346675 > might make this error stop happening: > >gptzfsboot: error 1 LBA 18446744072709551608 >gptzfsboot: error 1 LBA 1 >gptzfsboot: No ZFS pools located, can't boot > > Emphasis on the "might"... that appears to be an error during probing > for zfs, and I made some fixes related to probing for zfs. > Ian I saw this gptzfsboot issue 3 times in a row after re-activating r346885 but have not seen it again after at least 12 reboots this afternoon. It looks like there is an issue with the DRM update or changes to the kernel between r346544 and r346885 that is causing a separate problem for me. Thanks for looking into this. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
On 2019-04-29 14:58, Toomas Soome wrote: > > It means you have different issues - one is about gptzfsboot causing boot > problems and apparently it got fixed when you did update the bootcode (the > boot partition is global). But also you got bitten by DRM update, and since > you had old BE around, you were able to load old kernel. > > Now the question is, is that gptzfsboot issue really fixed or is it just the > “warm boot” fix you were seeing earlier too. > Toomas: After activating the snapshot made for r346885, I got the same sort of gptzfsboot errors that I had seen previously. After my third attempt, I was finally given the prompt for my Geli password and proceeded to the boot menu. I selected item #3 and went to the loader menu. I selected booting from kernel.old and got a successful startup. I have rebooted this laptop another dozen times this afternoon and had not had any more gptzfsboot issues since the three observed when re-activating r346885. It looks like the changes made by Ian Lepore did not solve my problem with gptzfsboot. I will probably start another thread about my issue with the DRM update. Thanks for the assistance. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
On Mon, 2019-04-29 at 14:47 -0400, Thomas Laus wrote: > On 2019-04-29 14:27, Thomas Laus wrote: > > It was more than a broken console. All of the other 2 computers > > that I > > upgraded to r346885 were essentially 'dead'. I could not even > > remotely > > login to them via ssh. All of them required a hard power button > > reset > > to get into single user mode to let me comment out the rc.conf line > > that > > loads the DRM driver. The computer could successfully boot without > > DRM > > activation but would go to a black console screen again with > > 'startx'. > > This also required a hard power button shutdown. I rolled back to > > r346544 and everything worked again like before. > > > > My disastrous update to r346885 included installing a new > > gptzfsboot and > > pmbr in the drive boot record. I did not try booting an older > > kernel > > using the new gptzfsboot. I was concerned about the lack of ssh > > login > > when the computers lost their console, so I just rolled back my > > system > > to the last snapshot made a week ago. > > > > Ian: > > I re-activated the r346885 BEADM snapshot and booted from my > 'kernel.old' from r346544 and everything came up OK including 'X'. > > I don't know what that means. It might be that I have a DRM issue > instead of a gptzfsboot problem? Everything except for the kernel is > now running CURRENT r346885. I am not using the updated > drm-current-kmod because I am using the r346544 kernel.old. > > Tom > > I can't say anything at all about drm or other video driver issues, I'm just not knowledgeable about that stuff at all. The only thing I was getting at was that the changes I made in r346675 might make this error stop happening: gptzfsboot: error 1 LBA 18446744072709551608 gptzfsboot: error 1 LBA 1 gptzfsboot: No ZFS pools located, can't boot Emphasis on the "might"... that appears to be an error during probing for zfs, and I made some fixes related to probing for zfs. -- Ian ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
> On 29 Apr 2019, at 21:47, Thomas Laus wrote: > > On 2019-04-29 14:27, Thomas Laus wrote: >> It was more than a broken console. All of the other 2 computers that I >> upgraded to r346885 were essentially 'dead'. I could not even remotely >> login to them via ssh. All of them required a hard power button reset >> to get into single user mode to let me comment out the rc.conf line that >> loads the DRM driver. The computer could successfully boot without DRM >> activation but would go to a black console screen again with 'startx'. >> This also required a hard power button shutdown. I rolled back to >> r346544 and everything worked again like before. >> >> My disastrous update to r346885 included installing a new gptzfsboot and >> pmbr in the drive boot record. I did not try booting an older kernel >> using the new gptzfsboot. I was concerned about the lack of ssh login >> when the computers lost their console, so I just rolled back my system >> to the last snapshot made a week ago. >> > Ian: > > I re-activated the r346885 BEADM snapshot and booted from my > 'kernel.old' from r346544 and everything came up OK including 'X'. > > I don't know what that means. It might be that I have a DRM issue > instead of a gptzfsboot problem? Everything except for the kernel is > now running CURRENT r346885. I am not using the updated > drm-current-kmod because I am using the r346544 kernel.old. > It means you have different issues - one is about gptzfsboot causing boot problems and apparently it got fixed when you did update the bootcode (the boot partition is global). But also you got bitten by DRM update, and since you had old BE around, you were able to load old kernel. Now the question is, is that gptzfsboot issue really fixed or is it just the “warm boot” fix you were seeing earlier too. rgds, toomas > Tom > > > -- > Public Keys: > PGP KeyID = 0x5F22FDC1 > GnuPG KeyID = 0x620836CF > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
On 2019-04-29 14:27, Thomas Laus wrote: > It was more than a broken console. All of the other 2 computers that I > upgraded to r346885 were essentially 'dead'. I could not even remotely > login to them via ssh. All of them required a hard power button reset > to get into single user mode to let me comment out the rc.conf line that > loads the DRM driver. The computer could successfully boot without DRM > activation but would go to a black console screen again with 'startx'. > This also required a hard power button shutdown. I rolled back to > r346544 and everything worked again like before. > > My disastrous update to r346885 included installing a new gptzfsboot and > pmbr in the drive boot record. I did not try booting an older kernel > using the new gptzfsboot. I was concerned about the lack of ssh login > when the computers lost their console, so I just rolled back my system > to the last snapshot made a week ago. > Ian: I re-activated the r346885 BEADM snapshot and booted from my 'kernel.old' from r346544 and everything came up OK including 'X'. I don't know what that means. It might be that I have a DRM issue instead of a gptzfsboot problem? Everything except for the kernel is now running CURRENT r346885. I am not using the updated drm-current-kmod because I am using the r346544 kernel.old. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
On 2019-04-29 11:14, Ian Lepore wrote: > > I'm fighting my own video driver troubles (seems like a lot of that > going around lately); on an upgrade of a machine from 11-stable to 12- > stable I lost my console. > > But, a broken kernel and/or userland shouldn't affect your ability to > use the new boot components. That is, you can use gptzfsboot and > loader that contain my fixes, and use them to load an older kernel that > has working video drivers. > Ian: It was more than a broken console. All of the other 2 computers that I upgraded to r346885 were essentially 'dead'. I could not even remotely login to them via ssh. All of them required a hard power button reset to get into single user mode to let me comment out the rc.conf line that loads the DRM driver. The computer could successfully boot without DRM activation but would go to a black console screen again with 'startx'. This also required a hard power button shutdown. I rolled back to r346544 and everything worked again like before. My disastrous update to r346885 included installing a new gptzfsboot and pmbr in the drive boot record. I did not try booting an older kernel using the new gptzfsboot. I was concerned about the lack of ssh login when the computers lost their console, so I just rolled back my system to the last snapshot made a week ago. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
On 2019-04-29 10:33, Thomas Laus wrote: > Updating to r346885 turned out to be a disaster! There were changes to > DRM between FreeBSD 13.0-CURRENT r346544 and r346885. The desktop that > I use for a build machine because it is much faster than any of my other > PC's installed kernel and world without any problems including starting > 'X'. I had to update the drm-current-kmod port on my build PC. Nothing > was in /usr/src/UPDATING or /usr/ports/UPDATING about the need to do so. > DRM on my build computer did not start until the update and then worked > as expected. > > I did the same on my Dell laptop and it crashed on the first boot right > after loading DRM-kmod. I removed the line in rc.conf that activates > the kernel module and my laptop booted into multiuser. When I started > 'X' it crashed just like before. The screen was black and I could not > login remotely via SSH. Nothing in any system log. The Xorg log shows > this and stops: > Ian: I updated my other desktop PC's (Intel Atom D510 and Dell AMD Sempron) and received the same black screen, not responsive, no log events just like my laptop with CURRENT r346885 and the DRM kmod update from ports. The only computer that had success was my Intel i5 Skylake. I did not try updating my other laptop since r346885 had issues on three computers. Recovery also required a BEADM rollback to the last successful snapshot. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
On Mon, 2019-04-29 at 10:33 -0400, Thomas Laus wrote: > > On 2019-04-28 22:27, Ian Lepore wrote: > > > > > > If you're using gptzfsboot, I guess you're using zfs? I just > > > fixed a > > > problem with probing disks for zfs volumes a few days ago > > > (r346675). > > > There is even some small chance it fixes this problem, because > > > one of > > > the things I noticed was that in one of the disk structures in > > > loader, > > > the "slice offset" value was sometimes a bit random-looking, like > > > it > > > was being initialized with whatever garbage was laying around in > > > memory. It actually makes some sense that the "garbage" might be > > > different between a firstboot after power-on and a reboot. > > > > > > So all in all, it wouldn't hurt to update both gptzfsboot and > > > loader > > > (gpart bootcode -b and -p) to see if there's a fix lurking in my > > > zfs > > > probe changes. > > > > > > > I'll build and update my laptop OS this morning and report back to > > this > > thread if I have any additional issues. > > > > Ian: > > Updating to r346885 turned out to be a disaster! There were changes > to > DRM between FreeBSD 13.0-CURRENT r346544 and r346885. The desktop > that > I use for a build machine because it is much faster than any of my > other > PC's installed kernel and world without any problems including > starting > 'X'. I had to update the drm-current-kmod port on my build > PC. Nothing > was in /usr/src/UPDATING or /usr/ports/UPDATING about the need to do > so. > DRM on my build computer did not start until the update and then > worked > as expected. > > I did the same on my Dell laptop and it crashed on the first boot > right > after loading DRM-kmod. I removed the line in rc.conf that activates > the kernel module and my laptop booted into multiuser. When I > started > 'X' it crashed just like before. The screen was black and I could > not > login remotely via SSH. Nothing in any system log. The Xorg log > shows > this and stops: > > 40.979]compiled for 1.18.4, module version = 2.4.0 > [40.979]Module class: X.Org Video Driver > [40.979]ABI class: X.Org Video Driver, version 20.0 > [40.979] (II) intel: Driver for Intel(R) Integrated Graphics > Chipsets: > i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, > 865G, > 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, > Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, > Q35, > Q33, > GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 > [40.981] (II) intel: Driver for Intel(R) HD Graphics > [40.981] (II) intel: Driver for Intel(R) Iris(TM) Graphics > [40.981] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics > [40.981] (II) modesetting: Driver for Modesetting Kernel Drivers: > kms > [40.981] (II) scfb: driver for wsdisplay framebuffer: scfb > [40.981] (II) VESA: driver for VESA chipsets: vesa > [40.981] (--) Using syscons driver with X support (version 2.0) > [40.981] (--) using VT number 9 > > I had to recover my system using beadm to rollback to the last > CURRENT > snapshot from a week ago. > > Tom > > I'm fighting my own video driver troubles (seems like a lot of that going around lately); on an upgrade of a machine from 11-stable to 12- stable I lost my console. But, a broken kernel and/or userland shouldn't affect your ability to use the new boot components. That is, you can use gptzfsboot and loader that contain my fixes, and use them to load an older kernel that has working video drivers. -- Ian ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
> On 2019-04-28 22:27, Ian Lepore wrote: >> >> If you're using gptzfsboot, I guess you're using zfs? I just fixed a >> problem with probing disks for zfs volumes a few days ago (r346675). >> There is even some small chance it fixes this problem, because one of >> the things I noticed was that in one of the disk structures in loader, >> the "slice offset" value was sometimes a bit random-looking, like it >> was being initialized with whatever garbage was laying around in >> memory. It actually makes some sense that the "garbage" might be >> different between a firstboot after power-on and a reboot. >> >> So all in all, it wouldn't hurt to update both gptzfsboot and loader >> (gpart bootcode -b and -p) to see if there's a fix lurking in my zfs >> probe changes. >> > I'll build and update my laptop OS this morning and report back to this > thread if I have any additional issues. > Ian: Updating to r346885 turned out to be a disaster! There were changes to DRM between FreeBSD 13.0-CURRENT r346544 and r346885. The desktop that I use for a build machine because it is much faster than any of my other PC's installed kernel and world without any problems including starting 'X'. I had to update the drm-current-kmod port on my build PC. Nothing was in /usr/src/UPDATING or /usr/ports/UPDATING about the need to do so. DRM on my build computer did not start until the update and then worked as expected. I did the same on my Dell laptop and it crashed on the first boot right after loading DRM-kmod. I removed the line in rc.conf that activates the kernel module and my laptop booted into multiuser. When I started 'X' it crashed just like before. The screen was black and I could not login remotely via SSH. Nothing in any system log. The Xorg log shows this and stops: 40.979]compiled for 1.18.4, module version = 2.4.0 [40.979]Module class: X.Org Video Driver [40.979]ABI class: X.Org Video Driver, version 20.0 [40.979] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [40.981] (II) intel: Driver for Intel(R) HD Graphics [40.981] (II) intel: Driver for Intel(R) Iris(TM) Graphics [40.981] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics [40.981] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [40.981] (II) scfb: driver for wsdisplay framebuffer: scfb [40.981] (II) VESA: driver for VESA chipsets: vesa [40.981] (--) Using syscons driver with X support (version 2.0) [40.981] (--) using VT number 9 I had to recover my system using beadm to rollback to the last CURRENT snapshot from a week ago. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
On 2019-04-28 22:27, Ian Lepore wrote: > > If you're using gptzfsboot, I guess you're using zfs? I just fixed a > problem with probing disks for zfs volumes a few days ago (r346675). > There is even some small chance it fixes this problem, because one of > the things I noticed was that in one of the disk structures in loader, > the "slice offset" value was sometimes a bit random-looking, like it > was being initialized with whatever garbage was laying around in > memory. It actually makes some sense that the "garbage" might be > different between a firstboot after power-on and a reboot. > > So all in all, it wouldn't hurt to update both gptzfsboot and loader > (gpart bootcode -b and -p) to see if there's a fix lurking in my zfs > probe changes. > I'll build and update my laptop OS this morning and report back to this thread if I have any additional issues. Thanks Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
On Sun, 2019-04-28 at 19:29 -0400, Thomas Laus wrote: > On 2019-04-28 08:07, Ronald Klop wrote: > > > > Is this the same as this? > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 > > > > The messages are similar. The boot process will normally proceed on > the > second or third attempt. On some days, I don't see this message > appear > and my laptops boot normally. I don't think that this problem is > hardware related. One laptop is a Compaq Pavilion with an AMD Turion > CPU and the other is a Dell Inspiron with an Intel Core2 Duo > CPU. One > hard drive is mechanical and the other is a SSD. I have swapped hard > drives between the two laptops and the issue still shows up on > occasion > with each PC. I have never seen this issue on any of my desktop > computers. Everything is running FreeBSD 13.0-CURRENT r346544 > GENERIC-NODEBUG at the moment. The thread in the bug report also > shows > a smaller LBA number, mine is LBA 18446744072709551608 and much > further > in geometry than most of the reported issues. I have seen this issue > since FreeBSD 12 was CURRENT. Since the boot process will work on a > second or third boot attempt, it is not a show stopper for me. > > Tom > If you're using gptzfsboot, I guess you're using zfs? I just fixed a problem with probing disks for zfs volumes a few days ago (r346675). There is even some small chance it fixes this problem, because one of the things I noticed was that in one of the disk structures in loader, the "slice offset" value was sometimes a bit random-looking, like it was being initialized with whatever garbage was laying around in memory. It actually makes some sense that the "garbage" might be different between a firstboot after power-on and a reboot. So all in all, it wouldn't hurt to update both gptzfsboot and loader (gpart bootcode -b and -p) to see if there's a fix lurking in my zfs probe changes. -- Ian ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
On Sun, Apr 28, 2019 at 5:30 PM Thomas Laus wrote: > On 2019-04-28 08:07, Ronald Klop wrote: > > > > Is this the same as this? > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 > > > The messages are similar. The boot process will normally proceed on the > second or third attempt. On some days, I don't see this message appear > and my laptops boot normally. I don't think that this problem is > hardware related. One laptop is a Compaq Pavilion with an AMD Turion > CPU and the other is a Dell Inspiron with an Intel Core2 Duo CPU. One > hard drive is mechanical and the other is a SSD. I have swapped hard > drives between the two laptops and the issue still shows up on occasion > with each PC. I have never seen this issue on any of my desktop > computers. Everything is running FreeBSD 13.0-CURRENT r346544 > GENERIC-NODEBUG at the moment. The thread in the bug report also shows > a smaller LBA number, mine is LBA 18446744072709551608 and much further > in geometry than most of the reported issues. I have seen this issue > since FreeBSD 12 was CURRENT. Since the boot process will work on a > second or third boot attempt, it is not a show stopper for me. Ever boot with thumb drives plugged in? Does the DVD player have a disk in it? Warner > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
On 2019-04-28 08:07, Ronald Klop wrote: > > Is this the same as this? > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 > The messages are similar. The boot process will normally proceed on the second or third attempt. On some days, I don't see this message appear and my laptops boot normally. I don't think that this problem is hardware related. One laptop is a Compaq Pavilion with an AMD Turion CPU and the other is a Dell Inspiron with an Intel Core2 Duo CPU. One hard drive is mechanical and the other is a SSD. I have swapped hard drives between the two laptops and the issue still shows up on occasion with each PC. I have never seen this issue on any of my desktop computers. Everything is running FreeBSD 13.0-CURRENT r346544 GENERIC-NODEBUG at the moment. The thread in the bug report also shows a smaller LBA number, mine is LBA 18446744072709551608 and much further in geometry than most of the reported issues. I have seen this issue since FreeBSD 12 was CURRENT. Since the boot process will work on a second or third boot attempt, it is not a show stopper for me. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
On Fri, 26 Apr 2019 13:31:02 +0200, Thomas Laus wrote: List: I have been having gptzfsboot issues with my two laptops since 12.0 was still CURRENT. I receive 'error 1' on the first boot most days. gptzfsboot: error 1 LBA 18446744072709551608 gptzfsboot: error 1 LBA 1 gptzfsboot: No ZFS pools located, can't boot Is this the same as this? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 Regards, Ronald. Most of the time the boot process is successful on my next attempt. This happens on two different laptops (different manufacturer). Different hard drives (one mechanical, the other SSD). Both laptops are running 13.0-CURRENT FreeBSD 13.0-CURRENT r346544 GENERIC-NODEBUG. All of my desktop computers are running the same version of FreeBSD and never exhibit this issue. Is there something unique to a laptop reading the boot record and looking for a GELI encrypted partition that a desktop does not? Tom ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
Toomas Soome [tso...@me.com] wrote: > > > I always update the bootcode with gpart each time when updating my system. > > > > Oh right, this from gptzfsboot⦠ok, I guess I should do something > I have been planning all along⦠Do you need some sort of quick workaround? > No quick workaround is required, take your time. This is minor issue for me because my laptops mostly boot on the next attempt. Thanks for the quick response. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
> On 26 Apr 2019, at 16:20, Thomas Laus wrote: > > Toomas Soome [tso...@me.com] wrote: >> >> The key is about LBA in first message. Make sure you have latest >> boot code installed with gpart. >> > I always update the bootcode with gpart each time when updating my system. > Oh right, this from gptzfsboot… ok, I guess I should do something I have been planning all along… Do you need some sort of quick workaround? rgds, toomas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
Toomas Soome [tso...@me.com] wrote: > > The key is about LBA in first message. Make sure you have latest > boot code installed with gpart. > I always update the bootcode with gpart each time when updating my system. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Question about 'gptzfsboot'
> On 26 Apr 2019, at 14:31, Thomas Laus wrote: > > List: > > I have been having gptzfsboot issues with my two laptops since 12.0 was > still CURRENT. I receive 'error 1' on the first boot most days. > > gptzfsboot: error 1 LBA 18446744072709551608 > gptzfsboot: error 1 LBA 1 > gptzfsboot: No ZFS pools located, can't boot > > Most of the time the boot process is successful on my next attempt. > This happens on two different laptops (different manufacturer). > Different hard drives (one mechanical, the other SSD). Both laptops are > running 13.0-CURRENT FreeBSD 13.0-CURRENT r346544 GENERIC-NODEBUG. All > of my desktop computers are running the same version of FreeBSD and > never exhibit this issue. Is there something unique to a laptop reading > the boot record and looking for a GELI encrypted partition that a > desktop does not? > The key is about LBA in first message. Make sure you have latest boot code installed with gpart. rgds, toomas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Question about 'gptzfsboot'
List: I have been having gptzfsboot issues with my two laptops since 12.0 was still CURRENT. I receive 'error 1' on the first boot most days. gptzfsboot: error 1 LBA 18446744072709551608 gptzfsboot: error 1 LBA 1 gptzfsboot: No ZFS pools located, can't boot Most of the time the boot process is successful on my next attempt. This happens on two different laptops (different manufacturer). Different hard drives (one mechanical, the other SSD). Both laptops are running 13.0-CURRENT FreeBSD 13.0-CURRENT r346544 GENERIC-NODEBUG. All of my desktop computers are running the same version of FreeBSD and never exhibit this issue. Is there something unique to a laptop reading the boot record and looking for a GELI encrypted partition that a desktop does not? Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
