Ask Your Question

Fedora Hangs on Booting

asked 2015-10-15 20:55:52 -0500

Nerdsturm gravatar image

I recently moved some harddrives over to this workstation, and since then it has been unable to boot into Fedora. It reaches the splash screen with the "f" symbol that fills up, but once done just displays a black screen with some (~10) random multicolored characters. Pressing esc returns me to the "f" splash screen, but I'm unable to do anything (e.g. ctrl+alt+F2 does nothing).

I've tried booting off of a live USB, but I can't mount the harddrive with the Fedora install on it. This is a picture of the harddrive in the disk explorer, and the output from fdisk for the drive is at the bottom of this post. Do anyone here know why I can't mount it to at least start looking into bug checking, or recovering data?

fdisk output:

Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: FEFF9455-CCC7-4AEC-AFFC-EB8CD9B45989

Device       Start        End    Sectors  Size Type
/dev/sdb1     2048       4095       2048    1M BIOS boot
/dev/sdb2     4096    1028095    1024000  500M Linux filesystem
/dev/sdb3  1028096 7814035455 7813007360  3.7T Linux LVM
edit retag flag offensive close merge delete



don't mount /dev/sdb3; instead, do vgchange -ay; mount /dev/mapper/$something. If I understand you correctly, you moved drives with a Fedora installation over to a different computer; if that's the case, the rescue boot option should work . Whether you get in by the rescue option or by [link text]( "setting up a chroot")your next step should be to rebuild the initramfs with dracut --regenerate-all --force. Not sure that I have a clear idea of the issue, though.

randomuser gravatar imagerandomuser ( 2015-10-15 23:26:00 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2015-10-15 23:22:55 -0500

Nerdsturm gravatar image

Looks like this was a problem with harddrives sharing the same group name. I used this and vgrename to change the duplicated group names and it seems to have fixed both the harddrive access and boot issues.

edit flag offensive delete link more


How did you use vgrename? It doesn't seem to allow a vg_uuid parameter. And giving the existing ground name (of 'fedora') doesn't identify one because both drives have the same group name.

wallyk gravatar imagewallyk ( 2017-03-02 15:38:16 -0500 )edit

Question Tools

1 follower


Asked: 2015-10-15 20:55:52 -0500

Seen: 109 times

Last updated: Oct 15 '15