Results 1 to 4 of 4
Hi, I'm totaly newb when it comes to disk and volume management in linux,
I'm attempting to install a new 1TB disk to remove the current 250GB disk, the system ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 08-17-2010 #1Just Joined!
- Join Date
- Aug 2010
- Location
- sweden
- Posts
- 2
removing a disk causes boot error
Hi, I'm totaly newb when it comes to disk and volume management in linux,
I'm attempting to install a new 1TB disk to remove the current 250GB disk, the system also has a 37GB disk.
What I did was that I added to new 1TB disk to the system with the LVM tool, I added it with a mountpoint of /storage2. Then I removed the old disk with the LVM tool and moved it's data to the remaining disks (the 37GB and the new 1TB) with the LVM tool.
Everything looks ok so far.
When I reboot with the old 250GB disk still in the system it's all fine. But when I remove it, the system won't reboot. I get to the point of where the fedora screen usually turns up.
The old disk had 2 partitions, the new one has only one, I'm starting to think there's something in there causing the issue? Can't load that big partion at boot or something?
As I said, complete newb when it comes tho theses things, can anyone help?
If I'm missing to fill in some details, just ask and I'll try to answere. I now has the old disk back in the system to be able to boot.
Anyone?
- 08-17-2010 #2Linux Guru
- Join Date
- Oct 2007
- Location
- Tucson AZ
- Posts
- 2,517
Fedora usually defaults to creating a separate boot partition which you probably don't have now, it was likely on the 250GB if it works when it is in and does not work when it is not. Can you log in to a terminal as root and run the command: fdisk -l (lower case Letter L) to post your partition information. I'm not familiar with LVM so hopefully someone else will see your post and advise.
- 08-17-2010 #3Just Joined!
- Join Date
- Aug 2010
- Location
- sweden
- Posts
- 2
Thanks for the quick reply,
here's what the readout says when I do a fdisk -l:
The whole story is that I before had two 250GB disks in raid 1 and now I'm attempting to have two of the new 1TB disk in raid. The raid was hardware controlled and will be again, for now it's turned off.Code:# fdisk -l Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/sda doesn't contain a valid partition table Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00062991 Device Boot Start End Blocks Id System /dev/sdb1 1 121601 976760001 83 Linux Disk /dev/sdc: 37.0 GB, 37019566080 bytes 255 heads, 63 sectors/track, 4500 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xfef8fef8 Device Boot Start End Blocks Id System /dev/sdc1 1 4500 36146218+ 8e Linux LVM Disk /dev/sdd: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x26a17395 Device Boot Start End Blocks Id System /dev/sdd1 * 1 26 204800 83 Linux Partition 1 does not end on cylinder boundary. /dev/sdd2 26 30401 243991201 8e Linux LVM Disk /dev/dm-0: 250.0 GB, 250059348992 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x26a17395 Device Boot Start End Blocks Id System /dev/dm-0p1 * 1 26 204800 83 Linux Partition 1 does not end on cylinder boundary. /dev/dm-0p2 26 30401 243991201 8e Linux LVM Disk /dev/dm-1: 209 MB, 209715200 bytes 255 heads, 63 sectors/track, 25 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-1 doesn't contain a valid partition table Disk /dev/dm-2: 249.8 GB, 249846989824 bytes 255 heads, 63 sectors/track, 30375 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-2 doesn't contain a valid partition table Disk /dev/dm-3: 282.6 GB, 282645757952 bytes 255 heads, 63 sectors/track, 34363 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-3 doesn't contain a valid partition table Disk /dev/dm-4: 4211 MB, 4211081216 bytes 255 heads, 63 sectors/track, 511 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-4 doesn't contain a valid partition table Disk /dev/dm-5: 746.2 GB, 746250567680 bytes 255 heads, 63 sectors/track, 90726 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-5 doesn't contain a valid partition table
I see alot of "xx doesn't contain a valid partition table", guessing it's a part of the problem? Can I fixed that without having to remove the data on the new disk?
Otherwise I guess I need to add the data to the old disk somehow and partition the new disk somehow?
- 08-18-2010 #4Linux Guru
- Join Date
- Oct 2007
- Location
- Tucson AZ
- Posts
- 2,517
Your 250GB drive had/has the boot and Fedora system files? That would be the sdd drive. Are you keeping it attached? Do you have it set to first boot priority? If the answers to all the above are yes, it should boot. I doubt I'll be much help as I'm totally unfamiliar with LVM and/or RAID.


Reply With Quote
