[opensuse] can't boot (wrong UUID?)
openSUSE Tumbleweed here on a multi-boot system. One of the other Linux installs reformatted the swap partition, so it has a different UUID now. As far as I can tell, that's keeping SUSE from booting, because it drops to an emergency shell and one of the last messages I see says that the UUID for the swap partition doesn't exist. I edited /etc/fstab to change it to match /dev/disk/by-uuid, and I also edited the "resume=" lines in grub.cfg, but it still won't boot (with the same message referencing the old UUID). I can't find anyplace else where the old UUID is specified. Anybody have any ideas? -- Glenn Holmer (Linux registered user #16682) "After the vintage season came the aftermath -- and Cenbe." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/02/2015 07:57 PM, Glenn Holmer wrote:
openSUSE Tumbleweed here on a multi-boot system. One of the other Linux installs reformatted the swap partition, so it has a different UUID now. As far as I can tell, that's keeping SUSE from booting, because it drops to an emergency shell and one of the last messages I see says that the UUID for the swap partition doesn't exist.
I edited /etc/fstab to change it to match /dev/disk/by-uuid, and I also edited the "resume=" lines in grub.cfg, but it still won't boot (with the same message referencing the old UUID). I can't find anyplace else where the old UUID is specified.
Anybody have any ideas? .............
- i have every confidence that some kind person like mr jan is going to shout at me , but , as a temporary experiment , it might be worth a try editing /etc/fstab to something like : /dev/sda1 / /dev/sda2 /home /dev/sda3 swap - slim hope . buy maybe worth a try [ hold your horses mr jan , please ] ................. regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/02/2015 01:09 PM, ellanios82 wrote:
it might be worth a try editing /etc/fstab to something like :
/dev/sda1 / /dev/sda2 /home /dev/sda3 swap
Oh what a coincidence! In my fstab I have lines like that. I also have lines like LABEL=TMP /tmp ext4 noacl,noexec,nosuid,nodev 1 2 What I don't have is lines that invole a UUID. Portability? To what? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Jul 2, 2015 at 10:57 AM, Glenn Holmer
openSUSE Tumbleweed here on a multi-boot system. One of the other Linux installs reformatted the swap partition, so it has a different UUID now. As far as I can tell, that's keeping SUSE from booting, because it drops to an emergency shell and one of the last messages I see says that the UUID for the swap partition doesn't exist.
I edited /etc/fstab to change it to match /dev/disk/by-uuid, and I also edited the "resume=" lines in grub.cfg, but it still won't boot (with the same message referencing the old UUID). I can't find anyplace else where the old UUID is specified.
Anybody have any ideas?
This sounds like a dracut bug, where the initramfs has that UUID baked into it. Try rebuilding the initramfs and see if that fixes the problem. In my case it was the EFI system partition that it was hanging up on https://bugzilla.redhat.com/show_bug.cgi?id=1187007 For swap, what's supposed to work these days with systemd and GPT disks, is autodiscovery. If you set the swap partition type GUID correctly, it doesn't need to be in fstab at all, systemd will create swapon unit for it automatically. Sadly with recent versions of systemd this is no longer working for me. https://bugzilla.redhat.com/show_bug.cgi?id=1212591 -- Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/02/2015 01:23 PM, Chris Murphy wrote:
On Thu, Jul 2, 2015 at 10:57 AM, Glenn Holmer
wrote: openSUSE Tumbleweed here on a multi-boot system. One of the other Linux installs reformatted the swap partition, so it has a different UUID now. As far as I can tell, that's keeping SUSE from booting, because it drops to an emergency shell and one of the last messages I see says that the UUID for the swap partition doesn't exist.
I edited /etc/fstab to change it to match /dev/disk/by-uuid, and I also edited the "resume=" lines in grub.cfg, but it still won't boot (with the same message referencing the old UUID). I can't find anyplace else where the old UUID is specified.
Anybody have any ideas?
This sounds like a dracut bug, where the initramfs has that UUID baked into it. Try rebuilding the initramfs and see if that fixes the problem.
That's what I was starting to think. How do you re-create the initramfs from an emergency shell?
In my case it was the EFI system partition that it was hanging up on https://bugzilla.redhat.com/show_bug.cgi?id=1187007
Harald's workaround (hostonly_cmdline="no") didn't work for me. -- Glenn Holmer (Linux registered user #16682) "After the vintage season came the aftermath -- and Cenbe." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/02/2015 01:23 PM, Chris Murphy wrote:
On Thu, Jul 2, 2015 at 10:57 AM, Glenn Holmer
wrote: openSUSE Tumbleweed here on a multi-boot system. One of the other Linux installs reformatted the swap partition, so it has a different UUID now. As far as I can tell, that's keeping SUSE from booting, because it drops to an emergency shell and one of the last messages I see says that the UUID for the swap partition doesn't exist.
I edited /etc/fstab to change it to match /dev/disk/by-uuid, and I also edited the "resume=" lines in grub.cfg, but it still won't boot (with the same message referencing the old UUID). I can't find anyplace else where the old UUID is specified.
Anybody have any ideas?
This sounds like a dracut bug, where the initramfs has that UUID baked into it. Try rebuilding the initramfs and see if that fixes the problem.
Yes, that definitely seems to be it. From the rescue system, lsinitrd shows some files with names including that UUID. I don't quite understand that; hard-coding something like that into the initrd seems... how shall I put it... unwise. But now I'm stuck. How do I re-create the initrd if I can only get to an emergency shell (or boot from the rescue DVD)? Does anyone know how to do this? It's complicated by the fact that I keep /boot on a separate partition. -- Glenn Holmer (Linux registered user #16682) "After the vintage season came the aftermath -- and Cenbe." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
You should be able to accomplish this by using live media. Once you've booted into an openSUSE live system, you should be able to drop to the rescue.target either using systemctl(1) or the "single" kernel parameter at the boot menu. Then mount your root partition: mount /dev/sdXY /mnt Then mount the boot partition: mount /dev/sdXZ /mnt/boot Then you'll need to do a few bind mounts: mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys mount --bind /dev /mnt/dev Then chroot to the installed instance of openSUSE: chroot /mnt Then rebuild the initramfs: dracut -f <image> <kernel-version> Obviously, you'll need to find out the proper names of your block devices to mount and the name of the kernel and the initramfs image you wish to rebuild. Brandon Vincent-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/02/2015 05:14 PM, Brandon Vincent (Student) wrote:
You should be able to accomplish this by using live media.
Once you've booted into an openSUSE live system, you should be able to drop to the rescue.target either using systemctl(1) or the "single" kernel parameter at the boot menu.
Then mount your root partition: mount /dev/sdXY /mnt
Then mount the boot partition: mount /dev/sdXZ /mnt/boot
Then you'll need to do a few bind mounts: mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys mount --bind /dev /mnt/dev
Then chroot to the installed instance of openSUSE: chroot /mnt
Then rebuild the initramfs: dracut -f <image> <kernel-version>
Obviously, you'll need to find out the proper names of your block devices to mount and the name of the kernel and the initramfs image you wish to rebuild.
Thanx 10E6, that worked a treat. For future generations finding this message with the help of Mr Google, note that the dracut command looks something like this: dracut -f initrd-4.0.3-1-desktop 4.0.3-1-desktop (i.e. use the version only for the kernel, not "vmlinuz-..."). -- Glenn Holmer (Linux registered user #16682) "After the vintage season came the aftermath -- and Cenbe." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Glenn Holmer composed on 2015-07-02 16:43 (UTC-0500): [TW discussion belongs in opensuse-factory]
Chris Murphy wrote:
This sounds like a dracut bug, where the initramfs has that UUID baked into it. Try rebuilding the initramfs and see if that fixes the problem.
Yes, that definitely seems to be it. From the rescue system, lsinitrd shows some files with names including that UUID. I don't quite understand that; hard-coding something like that into the initrd seems... how shall I put it... unwise.
I think it's supposed to be a fallback for when root= is omitted from cmdline.
But now I'm stuck. How do I re-create the initrd if I can only get to an emergency shell (or boot from the rescue DVD)?
: Boot prior kernel. Remove swap from /etc/fstab. Boot other multiboot installation and chroot to TW to build initrd. Boot installation media and chroot... Copy /lib/modules/<kernel-version> from another installation, and use its kernel and initrd to boot your TW installation. Boot something else, and change the swapper's UUID back to what it was. Append noresume to kernel cmdline. *** When done fixing, set a volume label on swapper, and use label (memorable) or device name (memorable) in fstab instead of UUID (only memorable by eidetics and puters). Just because the installer mounts swap by UUID doesn't mean it must stay that way. *** I filed a bug for this problem: https://bugzilla.opensuse.org/show_bug.cgi?id=936964 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/02/2015 05:43 PM, Glenn Holmer wrote:
hard-coding something like that into the initrd seems... how shall I put it... unwise.
+1 -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/02/2015 06:11 PM, Anton Aylward wrote:
On 07/02/2015 05:43 PM, Glenn Holmer wrote:
hard-coding something like that into the initrd seems... how shall I put it... unwise.
+1
Indeed, https://dracut.wiki.kernel.org/index.php/Main_Page says: "Unlike existing initramfs's, dracut's framework attempts at having as little as possible hard-coded into the initramfs as possible." And why is the swap UUID also hardcoded in /etc/default/grub? -- Glenn Holmer (Linux registered user #16682) "After the vintage season came the aftermath -- and Cenbe." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/02/2015 10:33 PM, Glenn Holmer wrote:
On 07/02/2015 06:11 PM, Anton Aylward wrote:
On 07/02/2015 05:43 PM, Glenn Holmer wrote:
hard-coding something like that into the initrd seems... how shall I put it... unwise.
+1
Indeed, https://dracut.wiki.kernel.org/index.php/Main_Page says:
"Unlike existing initramfs's, dracut's framework attempts at having as little as possible hard-coded into the initramfs as possible."
And why is the swap UUID also hardcoded in /etc/default/grub?
I don't know about "hardcoded" Mine has GRUB_CMDLINE_LINUX_DEFAULT=" resume=/dev/disk/by-label/SWAP splash=silent quiet showopts" lets face it, label makes more sense. I'm on the verge of giving up on BtrFS for my RootFS. LVM means I can easily create a new LV and use rsync, excluding .snapshot, to copy it across to a extNFS or ResierFS, or even experiment with XFS or NilFS2 should i be so inclined. I don't have to worry about UUID, I just rename the relevant file systems. heck, typing UUIDs by hand is so error prone! Typing "ROOT" or "SWAP" is so much easier :-) Further down in that config file I also have # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux GRUB_DISABLE_LINUX_UUID=true YMMV. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
The way forward is GPT and discoverable partitions spec, so such things don't need to be either in fstab or grub, both of which are rather antiquated+fragile ways to do this. When using GPT partitioning, the partition type GUID tells systemd that this is a swap partition. Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Fri, 17 Jul 2015 09:28:02 -0600
Chris Murphy
The way forward is GPT and discoverable partitions spec, so such
bye bye dual boot ...
things don't need to be either in fstab or grub, both of which are rather antiquated+fragile ways to do this. When using GPT partitioning, the partition type GUID tells systemd that this is a swap partition.
Chris Murphy
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Jul 17, 2015 at 10:37 AM, Andrei Borzenkov
В Fri, 17 Jul 2015 09:28:02 -0600 Chris Murphy
пишет: The way forward is GPT and discoverable partitions spec, so such
bye bye dual boot ...
Why? -- Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Andrei Borzenkov
-
Anton Aylward
-
Brandon Vincent (Student)
-
Chris Murphy
-
ellanios82
-
Felix Miata
-
Glenn Holmer