FedoraForum.org - Fedora Support Forums and Community
Page 1 of 2 12 LastLast
Results 1 to 15 of 16
  1. #1
    Join Date
    Mar 2006
    Location
    Portland, Oregon
    Posts
    33
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    F19 won't boot after swap's UUID was changed

    The other day, I installed a new distro on my computer. This involved reformatting 3 partitions, one of which was swap. When partitions are reformatted, their UUIDs are changed.

    I used the new distro to go into my Fedora 19's fstab and change the existing UUIDs to the new ones.

    However, F19 now will not boot, and the last few lines of the "sosreport.txt" file that the emergency shell generated read as follows:

    [ 2.159705] hatbox systemd[1]: Found device Hitachi_HDS722020ALA330.
    [ 184.695497] hatbox dracut-initqueue[104]: Warning: Could not boot.
    [ 184.710123] hatbox dracut-initqueue[104]: Warning: /dev/disk/by-uuid/3a9b0fe5-06b3-4897-a878-ced87d469da2 does not exist
    [ 184.713173] hatbox systemd[1]: Starting Dracut Emergency Shell...

    The UUID it can't find was that of my swap file, prior to the reformat. It now has a new UUID.

    From this, I conclude 4 things:
    1: The UUID of my swap file is written into the initramfs.
    2. It takes forever to get to an "emergency shell" after this problem occurs (note the difference in the timestamps). One might think the computer's simply hung.
    3. Fedora does not play well with others.
    4. <redacted due to use of inappropriate language>

    Can someone tell me how to regenerate the initramfs, or otherwise get around this problem?

  2. #2
    Join Date
    Aug 2009
    Location
    Waldorf, Maryland
    Posts
    7,343
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F19 won't boot after swap's UUID was changed

    Well... It wouldn't be writing the UUID into the initrd.

    The initrd gets that information from the /etc/fstab file.

    You can fix it by changing the UUID of the swap entry there. Use blkid to identify the new UUID.

    UNFORTUNATELY - you will have to use a rescue disk to fix it. Either by commenting out the swap line (I think it will boot without a swap partition), or getting the UUID value and setting it.

    This error, in my opinion, should not have prevented a boot.

    Have you tried a single user mode boot?

  3. #3
    Join Date
    Mar 2004
    Location
    In your closet
    Posts
    16,567
    Mentioned
    19 Post(s)
    Tagged
    0 Thread(s)

    Re: F19 won't boot after swap's UUID was changed

    This happens often when installing another OS. The swap partition gets formatted changing the UUID. I simply get the new UUID and make the change in /etc/fstab. Reboot and I'm good to go.

  4. #4
    Join Date
    Mar 2006
    Location
    Portland, Oregon
    Posts
    33
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F19 won't boot after swap's UUID was changed

    To quote what I wrote in the original post:

    I used the new distro to go into my Fedora 19's fstab and change the existing UUIDs to the new ones.

    In other words, the problem occurred after F19's fstab was edited and the correct UUID added.

    Also, the emergency shell I'm dumped into is the "Dracut Emergency Shell," complete with a "dracut:/#" prompt. That would seem to indicate a problem with the initial ramdisk, not a problem with fstab.

  5. #5
    Join Date
    Mar 2004
    Location
    In your closet
    Posts
    16,567
    Mentioned
    19 Post(s)
    Tagged
    0 Thread(s)

    Re: F19 won't boot after swap's UUID was changed

    Quote Originally Posted by eco2geek
    To quote what I wrote in the original post:

    I used the new distro to go into my Fedora 19's fstab and change the existing UUIDs to the new ones.
    It's my glasses I tell ya. Can't see with 'em, can't see without 'em.

  6. #6
    Join Date
    Mar 2006
    Location
    Portland, Oregon
    Posts
    33
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F19 won't boot after swap's UUID was changed

    Quote Originally Posted by glennzo
    It's my glasses I tell ya. Can't see with 'em, can't see without 'em.
    You're telling me! Which brings up another, totally unrelated, question: If a man speaks in the forest, and there's no woman around to hear him, is he still wrong?

  7. #7
    Join Date
    Jan 2010
    Posts
    8,698
    Mentioned
    41 Post(s)
    Tagged
    0 Thread(s)

    Re: F19 won't boot after swap's UUID was changed

    Out of idle curiosity, what happens if you change the uuid to /dev/sdwhatever.

  8. #8
    Join Date
    Aug 2011
    Posts
    433
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F19 won't boot after swap's UUID was changed

    Quote Originally Posted by glennzo
    This happens often when installing another OS. The swap partition gets formatted changing the UUID. I simply get the new UUID and make the change in /etc/fstab. Reboot and I'm good to go.
    Same here.

    This shouldn't be a problem.

  9. #9
    Join Date
    May 2011
    Location
    Confoederatio Helvetica (Swissh)
    Age
    46
    Posts
    4,526
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F19 won't boot after swap's UUID was changed

    Personaly i favor the /etc/default/grub setting:
    GRUB_DISABLE_LINUX_UUID=”true”
    Which will use /dev/sda instead of uuids for grub.

    hth
    * Shell Wrapper and Runtime Modifier (SWARM): https://github.com/sri-arjuna/SWARM
    * Yet Another Simple Script Installer (YASSI): https://forums.fedoraforum.org/showthread.php?323099
    * EFI Cheatsheet :: http://forums.fedoraforum.org/showthread.php?t=298546
    * Windows 8+ & Fedora 20+ Dualboot :: http://forums.fedoraforum.org/showthread.php?t=298161

  10. #10
    Join Date
    Jan 2010
    Posts
    8,698
    Mentioned
    41 Post(s)
    Tagged
    0 Thread(s)

    Re: F19 won't boot after swap's UUID was changed

    I don/t do that, figuring I should give in, but UUID seems to be another good idea which in practice hasn't worked that well. I've actually never had problems with renaming new drives, whereas, since UUID became the default, installations and even moving disks around has often resulted in a system that fails to boot due to an incorrect UUID. On rare occasions, even updates (probably the kernel--this hasn't happened for awhile, and at the time I just fixed it and forgot it, so don't remember what updates caused it--and this hasn't happened for a long time), would break it.

    As that hasn't happened in awhile, I guess it's improving, but as I understood it, it was to make things more robust, not more fragile.

    Although if we still used /dev/sdX by default, we'd probably see different sorts of problems when people add disks.

  11. #11
    Join Date
    Aug 2009
    Location
    Waldorf, Maryland
    Posts
    7,343
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F19 won't boot after swap's UUID was changed

    The problem is by people adding disks...

    such as USB disks, or any hotplug disk (all of mine are hotplug, even the SATA system disks).

    The problem is that all disks don't spin up at the same rate - normally all are STARTED at the same time, but the powersupply may sequence them however it wants, plus each disk is unique - so they will spin up in a different order at random. This makes physical names (sda/sdb/...)impossible. Instead you would have to something more like "adapter/controller/drive/partition" naming. And the "adapter/controller" sequence would have to have a "slot number" defined by how things are wired together. Unfortunately that crappy "plug and play" stuff removes the ability to have fixed naming standards. And then there are things like fibre channel that are also random... even to the controller (single attached/dual attached/alternate controllers...) that do provide the same disk... with different names to allow for controller failures with automatic fail over.

  12. #12
    Join Date
    May 2009
    Location
    Manorville, New York, USA
    Posts
    1,677
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F19 won't boot after swap's UUID was changed

    I guess I didn't see this thread before I posted this: http://forums.fedoraforum.org/showpo...4&postcount=43

    F19 gives you a rescue kernel in grub. Enter, list the blkid's. Copy new UUID for swap into fstab, then run:

    dracut --regenerate-all --force

    Seems that someone thought this through before changing what dracut puts into the intramfs.
    Registered Linux User #348347
    Have you been seduced by siduction? http://siduction.org/index.php
    Running Fedora 19/20, siduction and openSUSE 13.1 with KDE

  13. #13
    Join Date
    Aug 2009
    Location
    Waldorf, Maryland
    Posts
    7,343
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F19 won't boot after swap's UUID was changed

    You don't need to use dracut at all. Once it is in the /etc/fstab file you are done.

  14. #14
    Join Date
    Jul 2011
    Location
    Birmingham, UK
    Age
    44
    Posts
    2,759
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F19 won't boot after swap's UUID was changed

    Regenerate the initramfs image, as mentioned. (It can take a copy of fstab in some circumstances, although as far as I know it’s unusual).

  15. #15
    Join Date
    Mar 2006
    Location
    Portland, Oregon
    Posts
    33
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F19 won't boot after swap's UUID was changed

    Quote Originally Posted by GoinEasy9
    dracut --regenerate-all --force

    Seems that someone thought this through before changing what dracut puts into the intramfs.
    I would hope so! Imagine your computer being rendered unbootable simply because your swap partition was reformatted!

    Thanks for the information. I already reinstalled Fedora 19, but that's good to know.

Page 1 of 2 12 LastLast

Similar Threads

  1. UUID Changed
    By drnetsys in forum Using Fedora
    Replies: 4
    Last Post: 13th June 2012, 01:04 PM
  2. Replies: 1
    Last Post: 11th March 2010, 05:56 PM
  3. FC10 custom kernel won't boot root via UUID
    By llowrey in forum Using Fedora
    Replies: 4
    Last Post: 19th January 2009, 04:45 PM
  4. changed HW,now FC9 won't boot
    By mborgerd in forum Hardware
    Replies: 0
    Last Post: 2nd October 2008, 06:27 AM
  5. Changed monitor model. Now it won't boot
    By dlr739604 in forum Installation, Upgrades and Live Media
    Replies: 1
    Last Post: 11th July 2007, 05:12 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •