Re: [SOLVED LESS]Grub does not recognize lvm physical volume by uuid after restart
On 04/04/14 01:02 AM, André Nunes Batista wrote: On Tue, 2014-04-01 at 20:39 +0100, Joe wrote: Grub2 2.02~beta2-8 packages now available in sid, booting OK for me. Less is more, Joe! I confirm that upgrading to grub2 2.02~beta2-8 also solves the my machine. I was checking back in the list about this issue as I had to downgrade grub2 also. So, if I upgrade to 2.02~beta2-8 (or newer) there shouldn't be any problems. Will report back. Also, this will allow me to forget about this and get my new SSD in the box to do a dirty upgrade/clean install on it (not decided yet). KS -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53556aee.9020...@fastmail.fm
Re: [SOLVED LESS]Grub does not recognize lvm physical volume by uuid after restart
On 21/04/14 03:01 PM, KS wrote: On 04/04/14 01:02 AM, André Nunes Batista wrote: On Tue, 2014-04-01 at 20:39 +0100, Joe wrote: Grub2 2.02~beta2-8 packages now available in sid, booting OK for me. Less is more, Joe! I confirm that upgrading to grub2 2.02~beta2-8 also solves the my machine. I was checking back in the list about this issue as I had to downgrade grub2 also. So, if I upgrade to 2.02~beta2-8 (or newer) there shouldn't be any problems. Upgraded to 2.02~beta2-9 and boot process is normal. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53557fb7.8000...@fastmail.fm
Re: [SOLVED LESS]Grub does not recognize lvm physical volume by uuid after restart
On Tue, 2014-04-01 at 20:39 +0100, Joe wrote: On Tue, 25 Mar 2014 18:05:39 -0300 André Nunes Batista andrenbati...@gmail.com wrote: On Tue, 2014-03-25 at 14:15 -0300, André Nunes Batista wrote: On Mon, 2014-03-24 at 12:36 +, Darac Marjal wrote: On Mon, Mar 24, 2014 at 12:17:17PM +, Joe wrote: On Mon, 24 Mar 2014 11:17:53 + Darac Marjal mailingl...@darac.org.uk wrote: Now, I'm not certain about this, but I suspect that either the initramfs hasn't recognised that I'm using LVM, or it just isn't starting the LVM on its own. I haven't actually investigated this, but it might be related to bug #616689. Except... both the OP's initramfs and mine do recognise the swap partition within LVM, but not any others. And my system is (apparently) OK after downgrading grub from the latest version. Ah. Sorry for the noise, then. Your answer proved not be noise at all. I tried to follow Joe's steps and downgraded grub2-common, grub-common, grub-pc and grub-pc-bin all to jessie (2.00-22), ran update-grub2 and then grub-install /dev/sda and lost my grub.cfg. I've restored it using supergrubdisk, which, when booting, gave me access to that previous initramfs shell. Then I ran vgchange -ay ^D, ^D and was able to boot the system. One thing caught my eye through the process: grub says it's generating configs for i386 only, but this machine uses amd64 kernel. As soon as I get the chance I'll read #616689 and try to investigate it further on this machine. Currently it only boots through this forced activation method you taught me. I'm marking this thread as solved as I finally got to restore the system boot process. To anyone who may care, after booting the OS as described above, I once again reconfigured grub packages, keeping it downgraded to 2.00-22, as suggested by Joe. After that I could update-grub2 and got no complaints when installing to /dev/sda. Grub2 2.02~beta2-8 packages now available in sid, booting OK for me. Less is more, Joe! I confirm that upgrading to grub2 2.02~beta2-8 also solves the my machine. -- André N. Batista GNUPG/PGP KEY: 6722CF80 signature.asc Description: This is a digitally signed message part
Re: [SOLVED MORE]Grub does not recognize lvm physical volume by uuid after restart
On Tue, 25 Mar 2014 18:05:39 -0300 André Nunes Batista andrenbati...@gmail.com wrote: On Tue, 2014-03-25 at 14:15 -0300, André Nunes Batista wrote: On Mon, 2014-03-24 at 12:36 +, Darac Marjal wrote: On Mon, Mar 24, 2014 at 12:17:17PM +, Joe wrote: On Mon, 24 Mar 2014 11:17:53 + Darac Marjal mailingl...@darac.org.uk wrote: Now, I'm not certain about this, but I suspect that either the initramfs hasn't recognised that I'm using LVM, or it just isn't starting the LVM on its own. I haven't actually investigated this, but it might be related to bug #616689. Except... both the OP's initramfs and mine do recognise the swap partition within LVM, but not any others. And my system is (apparently) OK after downgrading grub from the latest version. Ah. Sorry for the noise, then. Your answer proved not be noise at all. I tried to follow Joe's steps and downgraded grub2-common, grub-common, grub-pc and grub-pc-bin all to jessie (2.00-22), ran update-grub2 and then grub-install /dev/sda and lost my grub.cfg. I've restored it using supergrubdisk, which, when booting, gave me access to that previous initramfs shell. Then I ran vgchange -ay ^D, ^D and was able to boot the system. One thing caught my eye through the process: grub says it's generating configs for i386 only, but this machine uses amd64 kernel. As soon as I get the chance I'll read #616689 and try to investigate it further on this machine. Currently it only boots through this forced activation method you taught me. I'm marking this thread as solved as I finally got to restore the system boot process. To anyone who may care, after booting the OS as described above, I once again reconfigured grub packages, keeping it downgraded to 2.00-22, as suggested by Joe. After that I could update-grub2 and got no complaints when installing to /dev/sda. Grub2 2.02~beta2-8 packages now available in sid, booting OK for me. -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140401203953.7028b...@jretrading.com
Re: Grub does not recognize lvm physical volume by uuid after restart
I'm running jessie/sid, I've had the initramfs not recognize my root partition a couple times recently after routine upgrades. The best, or at least easiest, solution I've found to fix this problem so far is to go in with a rescue boot CD and reinstall the kernel. It would be nice if I didn't have reinstall my kernel after every other apt-get dist-upgrade. On Sat, Mar 22, 2014 at 4:27 PM, André Nunes Batista andrenbati...@gmail.com wrote: Hello dear debian users! Recently, one jessie notebook I administer went through a forceful shutdown (holding down the power button) and after that grub cannot see the lvm physical volume by uuid. After trying to load the volume for some seconds, it gives the following message and drops to a minimal initramfs shell: Gave up waiting for root device. Common problems: - Boot args - check rootdelay=(long enough?) - check root=(right device?) - Missing modules ALERT! /dev/disk/by-uuid/090f9d09g0f9g-xx-xx does not exist. Dropping to a shell Using this minimal shell I'm able to go to this path and it actually does not contain any reference to this physical volume. Also, on /dev/mapper/ there is no reference to the root and home logical volumes, but there is a reference to the swap logical volume. Using a live distribution I had no problem mounting this volume and accessing its contents, so no real damage, but I would be glad on some pointers on how to make grub recognize it again. I've tried booting by-id and old school /dev/sdaX directly but had no luck. It was once installed using the default guided lvm partition from debian installer. TIA -- André N. Batista GNUPG/PGP KEY: 6722CF80 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1395520074.21009.26.camel@tagesuhu-pc -- Dale Harris rod...@maybe.org rod...@gmail.com /.-) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAEBW9tY70iaPmsv=pok-cyd5wybipqxyjg17gvuonplxkvt...@mail.gmail.com
Re: [OT][SOLVED]Grub does not recognize lvm physical volume by uuid after restart
On 20140325_180539, André Nunes Batista wrote: On Tue, 2014-03-25 at 14:15 -0300, André Nunes Batista wrote: On Mon, 2014-03-24 at 12:36 +, Darac Marjal wrote: On Mon, Mar 24, 2014 at 12:17:17PM +, Joe wrote: On Mon, 24 Mar 2014 11:17:53 + Darac Marjal mailingl...@darac.org.uk wrote: Now, I'm not certain about this, but I suspect that either the initramfs hasn't recognised that I'm using LVM, or it just isn't starting the LVM on its own. I haven't actually investigated this, but it might be related to bug #616689. Except... both the OP's initramfs and mine do recognise the swap partition within LVM, but not any others. And my system is (apparently) OK after downgrading grub from the latest version. Ah. Sorry for the noise, then. Your answer proved not be noise at all. I tried to follow Joe's steps and downgraded grub2-common, grub-common, grub-pc and grub-pc-bin all to jessie (2.00-22), ran update-grub2 and then grub-install /dev/sda and lost my grub.cfg. I've restored it using supergrubdisk, which, when booting, gave me access to that previous initramfs shell. Then I ran vgchange -ay ^D, ^D and was able to boot the system. One thing caught my eye through the process: grub says it's generating configs for i386 only, but this machine uses amd64 kernel. As soon as I get the chance I'll read #616689 and try to investigate it further on this machine. Currently it only boots through this forced activation method you taught me. I'm marking this thread as solved as I finally got to restore the system boot process. To anyone who may care, after booting the OS as described above, I once again reconfigured grub packages, keeping it downgraded to 2.00-22, as suggested by Joe. After that I could update-grub2 and got no complaints when installing to /dev/sda. Since I could not figure out if it was bug #616689 or #741652 (initramfs or grub), I've replied both and I guess any further debugging better be handled on one of those than here. So problem solved. and John, I do not need assistance with SGD, thank you, it worked just as expected. -- André N. Batista GNUPG/PGP KEY: 6722CF80 I've been following (lurking?) this thread hoping to improve my knowledge of the boot process. I've never heard of SGD. What is it? Google thinks it is a genetic or protein sequence database which is surely not what you are talking about. Cheers, -- Paul E Condon pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140326162806.gc4...@big.lan.gnu
Re: [OT][SOLVED]Grub does not recognize lvm physical volume by uuid after restart
Paul E Condon writes: I've been following (lurking?) this thread hoping to improve my knowledge of the boot process. I've never heard of SGD. What is it? Super Grub Disk. -- Alberto -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87siq4gaqh@eps142.cdf.udc.es
Re: [OT][SOLVED]Grub does not recognize lvm physical volume by uuid after restart
On Wednesday 26 March 2014 10:28:06 Paul E Condon wrote: On 20140325_180539, André Nunes Batista wrote: On Tue, 2014-03-25 at 14:15 -0300, André Nunes Batista wrote: On Mon, 2014-03-24 at 12:36 +, Darac Marjal wrote: On Mon, Mar 24, 2014 at 12:17:17PM +, Joe wrote: On Mon, 24 Mar 2014 11:17:53 + Darac Marjal mailingl...@darac.org.uk wrote: Now, I'm not certain about this, but I suspect that either the initramfs hasn't recognised that I'm using LVM, or it just isn't starting the LVM on its own. I haven't actually investigated this, but it might be related to bug #616689. Except... both the OP's initramfs and mine do recognise the swap partition within LVM, but not any others. And my system is (apparently) OK after downgrading grub from the latest version. Ah. Sorry for the noise, then. Your answer proved not be noise at all. I tried to follow Joe's steps and downgraded grub2-common, grub-common, grub-pc and grub-pc-bin all to jessie (2.00-22), ran update-grub2 and then grub-install /dev/sda and lost my grub.cfg. I've restored it using supergrubdisk, which, when booting, gave me access to that previous initramfs shell. Then I ran vgchange -ay ^D, ^D and was able to boot the system. One thing caught my eye through the process: grub says it's generating configs for i386 only, but this machine uses amd64 kernel. As soon as I get the chance I'll read #616689 and try to investigate it further on this machine. Currently it only boots through this forced activation method you taught me. I'm marking this thread as solved as I finally got to restore the system boot process. To anyone who may care, after booting the OS as described above, I once again reconfigured grub packages, keeping it downgraded to 2.00-22, as suggested by Joe. After that I could update-grub2 and got no complaints when installing to /dev/sda. Since I could not figure out if it was bug #616689 or #741652 (initramfs or grub), I've replied both and I guess any further debugging better be handled on one of those than here. So problem solved. and John, I do not need assistance with SGD, thank you, it worked just as expected. I've been following (lurking?) this thread hoping to improve my knowledge of the boot process. I've never heard of SGD. What is it? Google thinks it is a genetic or protein sequence database which is surely not what you are talking about. Cheers, http://www.supergrubdisk.org/wiki/SGD_Howto_Boot -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2506575.NjbTNsKjEL@lxcl01
Re: Grub does not recognize lvm physical volume by uuid after restart
On Mon, 2014-03-24 at 12:36 +, Darac Marjal wrote: On Mon, Mar 24, 2014 at 12:17:17PM +, Joe wrote: On Mon, 24 Mar 2014 11:17:53 + Darac Marjal mailingl...@darac.org.uk wrote: Now, I'm not certain about this, but I suspect that either the initramfs hasn't recognised that I'm using LVM, or it just isn't starting the LVM on its own. I haven't actually investigated this, but it might be related to bug #616689. Except... both the OP's initramfs and mine do recognise the swap partition within LVM, but not any others. And my system is (apparently) OK after downgrading grub from the latest version. Ah. Sorry for the noise, then. Your answer proved not be noise at all. I tried to follow Joe's steps and downgraded grub2-common, grub-common, grub-pc and grub-pc-bin all to jessie (2.00-22), ran update-grub2 and then grub-install /dev/sda and lost my grub.cfg. I've restored it using supergrubdisk, which, when booting, gave me access to that previous initramfs shell. Then I ran vgchange -ay ^D, ^D and was able to boot the system. One thing caught my eye through the process: grub says it's generating configs for i386 only, but this machine uses amd64 kernel. As soon as I get the chance I'll read #616689 and try to investigate it further on this machine. Currently it only boots through this forced activation method you taught me. -- André N. Batista GNUPG/PGP KEY: 6722CF80 signature.asc Description: This is a digitally signed message part
initramfs-tools or dracut ? (was Re: Grub does not recognize lvm physical volume by uuid after restart)
Hello, On Tue, Mar 25, 2014 at 6:15 PM, André Nunes Batista andrenbati...@gmail.com wrote: On Mon, 2014-03-24 at 12:36 +, Darac Marjal wrote: On Mon, Mar 24, 2014 at 12:17:17PM +, Joe wrote: On Mon, 24 Mar 2014 11:17:53 + Darac Marjal mailingl...@darac.org.uk wrote: Now, I'm not certain about this, but I suspect that either the initramfs hasn't recognised that I'm using LVM, or it just isn't starting the LVM on its own. I haven't actually investigated this, but it might be related to bug #616689. Except... both the OP's initramfs and mine do recognise the swap partition within LVM, but not any others. And my system is (apparently) OK after downgrading grub from the latest version. Ah. Sorry for the noise, then. Your answer proved not be noise at all. I tried to follow Joe's steps and downgraded grub2-common, grub-common, grub-pc and grub-pc-bin all to jessie (2.00-22), ran update-grub2 and then grub-install /dev/sda and lost my grub.cfg. I've restored it using supergrubdisk, which, when booting, gave me access to that previous initramfs shell. Then I ran vgchange -ay ^D, ^D and was able to boot the system. One thing caught my eye through the process: grub says it's generating configs for i386 only, but this machine uses amd64 kernel. As soon as I get the chance I'll read #616689 and try to investigate it further on this machine. Currently it only boots through this forced activation method you taught me. This thread remember me what happens to me last week: I had a grml installation (which I expect to have a behaviour exactly like a debian system now that I installed all the packages that I needed from debian sid). That installation was without lvm, all contents to one partitioin. So the last week I wanted to change that installation and move to lvm style. So I backed data, created partitions, and tried to update grub / etc/fstab .. from chroot I knew about #741342 Debian Bug, so I workaround about it with GRUB_DISABLE_LINUX_UUID=true hack The result of that movement was a unbootable system (grub rebooted the system) After researching grub or kernel parameters, like panic, I find about where was the error: initramfs generated inside the chroot was failed and lsinitramfs list an empty initramfs empty (after research I hit another bug [1]) Compressing initramfs generated, lsinitramfs show only this file: kernel/x86/microcode/GenuineIntel.bin So finally I copied an initramfs from other sid machine, and it worked. Then I tried to regenerate initramfs from scratch in the machine, and like I didn't know about [1] bug, I think it was erroneus. I didn't report any bug because it was a grml system when it was installed. Then I tried to install dracut (which is an alternative to initramfs-tools) and it worked like a charms. lsinitr* worked again, and I could boot without any problem So, how do you extract your initramfs content ? There is a patch at [1], but it is not being accepted by the maintainer. (I guess dd and offset commands illustrated at the bug will work) I will try to return to initramfs-tools and see if the generated initramfs is working (like it seems) Regards, [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717805 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cal5ymzqovouebx5yqjvbgqvkkc-myv_lfjb+gya_sc-ae9b...@mail.gmail.com
Re: [SOLVED]Grub does not recognize lvm physical volume by uuid after restart
On Tue, 2014-03-25 at 14:15 -0300, André Nunes Batista wrote: On Mon, 2014-03-24 at 12:36 +, Darac Marjal wrote: On Mon, Mar 24, 2014 at 12:17:17PM +, Joe wrote: On Mon, 24 Mar 2014 11:17:53 + Darac Marjal mailingl...@darac.org.uk wrote: Now, I'm not certain about this, but I suspect that either the initramfs hasn't recognised that I'm using LVM, or it just isn't starting the LVM on its own. I haven't actually investigated this, but it might be related to bug #616689. Except... both the OP's initramfs and mine do recognise the swap partition within LVM, but not any others. And my system is (apparently) OK after downgrading grub from the latest version. Ah. Sorry for the noise, then. Your answer proved not be noise at all. I tried to follow Joe's steps and downgraded grub2-common, grub-common, grub-pc and grub-pc-bin all to jessie (2.00-22), ran update-grub2 and then grub-install /dev/sda and lost my grub.cfg. I've restored it using supergrubdisk, which, when booting, gave me access to that previous initramfs shell. Then I ran vgchange -ay ^D, ^D and was able to boot the system. One thing caught my eye through the process: grub says it's generating configs for i386 only, but this machine uses amd64 kernel. As soon as I get the chance I'll read #616689 and try to investigate it further on this machine. Currently it only boots through this forced activation method you taught me. I'm marking this thread as solved as I finally got to restore the system boot process. To anyone who may care, after booting the OS as described above, I once again reconfigured grub packages, keeping it downgraded to 2.00-22, as suggested by Joe. After that I could update-grub2 and got no complaints when installing to /dev/sda. Since I could not figure out if it was bug #616689 or #741652 (initramfs or grub), I've replied both and I guess any further debugging better be handled on one of those than here. So problem solved. and John, I do not need assistance with SGD, thank you, it worked just as expected. -- André N. Batista GNUPG/PGP KEY: 6722CF80 signature.asc Description: This is a digitally signed message part
Re: [SOLVED]Grub does not recognize lvm physical volume by uuid after restart
On 03/25/2014 05:05 PM, André Nunes Batista wrote: On Tue, 2014-03-25 at 14:15 -0300, André Nunes Batista wrote: On Mon, 2014-03-24 at 12:36 +, Darac Marjal wrote: On Mon, Mar 24, 2014 at 12:17:17PM +, Joe wrote: On Mon, 24 Mar 2014 11:17:53 + Darac Marjal mailingl...@darac.org.uk wrote: Now, I'm not certain about this, but I suspect that either the initramfs hasn't recognised that I'm using LVM, or it just isn't starting the LVM on its own. I haven't actually investigated this, but it might be related to bug #616689. Except... both the OP's initramfs and mine do recognise the swap partition within LVM, but not any others. And my system is (apparently) OK after downgrading grub from the latest version. Ah. Sorry for the noise, then. Your answer proved not be noise at all. I tried to follow Joe's steps and downgraded grub2-common, grub-common, grub-pc and grub-pc-bin all to jessie (2.00-22), ran update-grub2 and then grub-install /dev/sda and lost my grub.cfg. I've restored it using supergrubdisk, which, when booting, gave me access to that previous initramfs shell. Then I ran vgchange -ay ^D, ^D and was able to boot the system. One thing caught my eye through the process: grub says it's generating configs for i386 only, but this machine uses amd64 kernel. As soon as I get the chance I'll read #616689 and try to investigate it further on this machine. Currently it only boots through this forced activation method you taught me. I'm marking this thread as solved as I finally got to restore the system boot process. To anyone who may care, after booting the OS as described above, I once again reconfigured grub packages, keeping it downgraded to 2.00-22, as suggested by Joe. After that I could update-grub2 and got no complaints when installing to /dev/sda. Since I could not figure out if it was bug #616689 or #741652 (initramfs or grub), I've replied both and I guess any further debugging better be handled on one of those than here. So problem solved. and John, I do not need assistance with SGD, thank you, it worked just as expected. It's only been since the last week that my Ubuntu harddrive was automatically added with update-grub. Some package upgraded did the trick I suppose. And no, I didn't have to fix my system. Ric -- My father, Victor Moore (Vic) used to say: There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome. R.I.P. Dad. /https://linuxcounter.net/cert/44256.png / -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5331f36c.3070...@gmail.com
Re: Grub does not recognize lvm physical volume by uuid after restart
On Sat, Mar 22, 2014 at 05:27:54PM -0300, André Nunes Batista wrote: Hello dear debian users! Recently, one jessie notebook I administer went through a forceful shutdown (holding down the power button) and after that grub cannot see the lvm physical volume by uuid. After trying to load the volume for some seconds, it gives the following message and drops to a minimal initramfs shell: Gave up waiting for root device. Common problems: - Boot args - check rootdelay=(long enough?) - check root=(right device?) - Missing modules ALERT! /dev/disk/by-uuid/090f9d09g0f9g-xx-xx does not exist. Dropping to a shell Using this minimal shell I'm able to go to this path and it actually does not contain any reference to this physical volume. Also, on /dev/mapper/ there is no reference to the root and home logical volumes, but there is a reference to the swap logical volume. Using a live distribution I had no problem mounting this volume and accessing its contents, so no real damage, but I would be glad on some pointers on how to make grub recognize it again. I've tried booting by-id and old school /dev/sdaX directly but had no luck. It was once installed using the default guided lvm partition from debian installer. I've been seeing this issue on a machine I have with root on LVM. My own suspicion is that it's an initramfs problem. I've been working around it by, at the initramfs prompt, entering: $ lvm lvm vgscan lvm vgchange -ay lvm ^D $ ^D and boot-up continues. Now, I'm not certain about this, but I suspect that either the initramfs hasn't recognised that I'm using LVM, or it just isn't starting the LVM on its own. I haven't actually investigated this, but it might be related to bug #616689. TIA -- André N. Batista GNUPG/PGP KEY: 6722CF80 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1395520074.21009.26.camel@tagesuhu-pc signature.asc Description: Digital signature
Re: Grub does not recognize lvm physical volume by uuid after restart
On Mon, 24 Mar 2014 11:17:53 + Darac Marjal mailingl...@darac.org.uk wrote: Now, I'm not certain about this, but I suspect that either the initramfs hasn't recognised that I'm using LVM, or it just isn't starting the LVM on its own. I haven't actually investigated this, but it might be related to bug #616689. Except... both the OP's initramfs and mine do recognise the swap partition within LVM, but not any others. And my system is (apparently) OK after downgrading grub from the latest version. -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140324121717.7105a...@jretrading.com
Re: Grub does not recognize lvm physical volume by uuid after restart
On Mon, Mar 24, 2014 at 12:17:17PM +, Joe wrote: On Mon, 24 Mar 2014 11:17:53 + Darac Marjal mailingl...@darac.org.uk wrote: Now, I'm not certain about this, but I suspect that either the initramfs hasn't recognised that I'm using LVM, or it just isn't starting the LVM on its own. I haven't actually investigated this, but it might be related to bug #616689. Except... both the OP's initramfs and mine do recognise the swap partition within LVM, but not any others. And my system is (apparently) OK after downgrading grub from the latest version. Ah. Sorry for the noise, then. signature.asc Description: Digital signature
Re: Grub does not recognize lvm physical volume by uuid after restart
On Sat, 2014-03-22 at 21:29 +, Joe wrote: On Sat, 22 Mar 2014 17:27:54 -0300 André Nunes Batista andrenbati...@gmail.com wrote: Hello dear debian users! Recently, one jessie notebook I administer went through a forceful shutdown (holding down the power button) and after that grub cannot see the lvm physical volume by uuid. After trying to load the volume for some seconds, it gives the following message and drops to a minimal initramfs shell: Gave up waiting for root device. Common problems: - Boot args - check rootdelay=(long enough?) - check root=(right device?) - Missing modules ALERT! /dev/disk/by-uuid/090f9d09g0f9g-xx-xx does not exist. Dropping to a shell Using this minimal shell I'm able to go to this path and it actually does not contain any reference to this physical volume. Also, on /dev/mapper/ there is no reference to the root and home logical volumes, but there is a reference to the swap logical volume. Using a live distribution I had no problem mounting this volume and accessing its contents, so no real damage, but I would be glad on some pointers on how to make grub recognize it again. I've tried booting by-id and old school /dev/sdaX directly but had no luck. It was once installed using the default guided lvm partition from debian installer. Hi André, Could you please confirm which version of grub-pc-bin you are running? I have recently had something very similar happen to an upgraded sid installation, that was fixed by downgrading to the previous version of this and other grub files. I have reported the bug but still do not know if the issue is with the grub files directly or whether there is an interaction with something else. I could only see my one non-LVM partition and also the swap partition within the LVM volume, but none of the other LVM partitions. I got the same messages you are seeing. The version of grub-pc-bin I had trouble with is the (sid) current 2.02~beta2-7, the version I downgraded to is 2.00-22, but that one is shown on the Debian packages page as the current version in jessie. If you still have 2.00-22 then this is a red herring, and the problem lies somewhere else, and I will amend the bug report. But 2.02~beta2-7 is still in sid, and about the right time has elapsed for it to be moved to jessie. If that has happened, and the packages page has not yet registered the fact, then you should be able to temporarily fix things by going back to 2.00-22. Out of curiosity, what filesystem(s) are you using in the LVM? I would have expected many more reports of this problem, but I am using reiserfs (a legacy from a long time ago) and it may be that not many other people are. -- Joe Hello Joe! It's amazing how I am always capable of omitting the most relevant info: yes, you correctly guessed, this machine was upgraded before the hard-shutdown and is using grub 2.02~beta2-7, so we might be facing the same bug. How did you downgrade grub? rescue-cd + chroot? Also, which bug number was assigned to you bug report? BTW, I'm using ext4 both on / and /home partition so the problem might not be related to the filesystem of choice. -- André N. Batista GNUPG/PGP KEY: 6722CF80 signature.asc Description: This is a digitally signed message part
Re: Grub does not recognize lvm physical volume by uuid after restart
On Mon, 24 Mar 2014 14:29:02 -0300 André Nunes Batista andrenbati...@gmail.com wrote: It's amazing how I am always capable of omitting the most relevant info: yes, you correctly guessed, this machine was upgraded before the hard-shutdown and is using grub 2.02~beta2-7, so we might be facing the same bug. How did you downgrade grub? rescue-cd + chroot? Yes, annoyingly my Wheezy netboot disc was miles away, so I burned another, I still had the iso laying around. I think it's a bit hairy to chroot with a different kernel, but I got away with it for long enough to run a couple of dpkg downgrades, and carefully avoided doing anything unnecessary. I needed grub-pc-bin and another, presumably grub-common, to boot (I was informed that grub-pc-bin could not be configured without the other, whichever it was) and once it booted I checked for other 2.02~beta2.7 items and downgraded them also. Also, which bug number was assigned to you bug report? Mine is 741652, but I had previously found 741464 which refers to a boot problem with grub 2.02~beta2.7. It's not the same problem but I thought the same treatment was worth a try, as I could see from the dates that the upgrade had just occurred on my system. BTW, I'm using ext4 both on / and /home partition so the problem might not be related to the filesystem of choice. OK, though if it's now affecting jessie, I'd expect to see more people catching it. But even today, https://packages.debian.org/search?keywords=grub-pc-binsearchon=namessuite=allsection=all is returning 2.00-22 for jessie. Possibly a good thing, as if you don't have the older version in your cache, it's much easier to get from jessie than by poking around in the snapshots. I don't clear my sid cache very often... -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140324210342.0bf1e...@jretrading.com
Re: Grub does not recognize lvm physical volume by uuid after restart
On 2014-03-24 22:03 +0100, Joe wrote: On Mon, 24 Mar 2014 14:29:02 -0300 André Nunes Batista andrenbati...@gmail.com wrote: Also, which bug number was assigned to you bug report? Mine is 741652, but I had previously found 741464 which refers to a boot problem with grub 2.02~beta2.7. #741464 appears to be unique to my old laptop, since I could not found a similar bug described anywhere on the Internet. OTOH #741652, #741342 and #741726 seem all to be the same problem, affecting everyone who has their root filesystem on LVM. Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87y4zzqn3m@turtle.gmx.de
Grub does not recognize lvm physical volume by uuid after restart
Hello dear debian users! Recently, one jessie notebook I administer went through a forceful shutdown (holding down the power button) and after that grub cannot see the lvm physical volume by uuid. After trying to load the volume for some seconds, it gives the following message and drops to a minimal initramfs shell: Gave up waiting for root device. Common problems: - Boot args - check rootdelay=(long enough?) - check root=(right device?) - Missing modules ALERT! /dev/disk/by-uuid/090f9d09g0f9g-xx-xx does not exist. Dropping to a shell Using this minimal shell I'm able to go to this path and it actually does not contain any reference to this physical volume. Also, on /dev/mapper/ there is no reference to the root and home logical volumes, but there is a reference to the swap logical volume. Using a live distribution I had no problem mounting this volume and accessing its contents, so no real damage, but I would be glad on some pointers on how to make grub recognize it again. I've tried booting by-id and old school /dev/sdaX directly but had no luck. It was once installed using the default guided lvm partition from debian installer. TIA -- André N. Batista GNUPG/PGP KEY: 6722CF80 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1395520074.21009.26.camel@tagesuhu-pc
Re: Grub does not recognize lvm physical volume by uuid after restart
On 20140322_172754, André Nunes Batista wrote: Hello dear debian users! Recently, one jessie notebook I administer went through a forceful shutdown (holding down the power button) and after that grub cannot see the lvm physical volume by uuid. After trying to load the volume for some seconds, it gives the following message and drops to a minimal initramfs shell: Gave up waiting for root device. Common problems: - Boot args - check rootdelay=(long enough?) - check root=(right device?) - Missing modules ALERT! /dev/disk/by-uuid/090f9d09g0f9g-xx-xx does not exist. Dropping to a shell Using this minimal shell I'm able to go to this path and it actually does not contain any reference to this physical volume. Also, on /dev/mapper/ there is no reference to the root and home logical volumes, but there is a reference to the swap logical volume. Using a live distribution I had no problem mounting this volume and accessing its contents, so no real damage, but I would be glad on some pointers on how to make grub recognize it again. I've tried booting by-id and old school /dev/sdaX directly but had no luck. It was once installed using the default guided lvm partition from debian installer. TIA If lvm was installed by debian-installer, grub should be looking for a separate physical partition for /boot , not something within lvm purview. Of course / is within lvm, but /boot is not. Look at /etc/fstab to see what I talking about. Use supergrub2 disk to reinstall grub2. HTH -- André N. Batista GNUPG/PGP KEY: 6722CF80 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1395520074.21009.26.camel@tagesuhu-pc -- Paul E Condon pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140322211602.ga13...@big.lan.gnu
Re: Grub does not recognize lvm physical volume by uuid after restart
On Sat, 22 Mar 2014 17:27:54 -0300 André Nunes Batista andrenbati...@gmail.com wrote: Hello dear debian users! Recently, one jessie notebook I administer went through a forceful shutdown (holding down the power button) and after that grub cannot see the lvm physical volume by uuid. After trying to load the volume for some seconds, it gives the following message and drops to a minimal initramfs shell: Gave up waiting for root device. Common problems: - Boot args - check rootdelay=(long enough?) - check root=(right device?) - Missing modules ALERT! /dev/disk/by-uuid/090f9d09g0f9g-xx-xx does not exist. Dropping to a shell Using this minimal shell I'm able to go to this path and it actually does not contain any reference to this physical volume. Also, on /dev/mapper/ there is no reference to the root and home logical volumes, but there is a reference to the swap logical volume. Using a live distribution I had no problem mounting this volume and accessing its contents, so no real damage, but I would be glad on some pointers on how to make grub recognize it again. I've tried booting by-id and old school /dev/sdaX directly but had no luck. It was once installed using the default guided lvm partition from debian installer. Hi André, Could you please confirm which version of grub-pc-bin you are running? I have recently had something very similar happen to an upgraded sid installation, that was fixed by downgrading to the previous version of this and other grub files. I have reported the bug but still do not know if the issue is with the grub files directly or whether there is an interaction with something else. I could only see my one non-LVM partition and also the swap partition within the LVM volume, but none of the other LVM partitions. I got the same messages you are seeing. The version of grub-pc-bin I had trouble with is the (sid) current 2.02~beta2-7, the version I downgraded to is 2.00-22, but that one is shown on the Debian packages page as the current version in jessie. If you still have 2.00-22 then this is a red herring, and the problem lies somewhere else, and I will amend the bug report. But 2.02~beta2-7 is still in sid, and about the right time has elapsed for it to be moved to jessie. If that has happened, and the packages page has not yet registered the fact, then you should be able to temporarily fix things by going back to 2.00-22. Out of curiosity, what filesystem(s) are you using in the LVM? I would have expected many more reports of this problem, but I am using reiserfs (a legacy from a long time ago) and it may be that not many other people are. -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140322212940.0861a...@jretrading.com
