Last week I added another drive to my backup server.
I then reshaped the RAID arrays and then resize2fs'd the main partition.
All looked fine until I rebooted, at which point it failed after loading the
kernel.
Last time I got round this by upgrading from FC7 to FC8, during which time it
re-installed the boot loader and installed the latest HDD image and all such
*stuff*.
I tried this again, upgrading from FC8 to FC9, but this time it isn't working.
However, it didn't work but in a way I didn't expect.
My boot partition partition is mirrored on the 1st and 2nd HDD's as it always
has been. The boot loader then booted from the copy on /dev/sda1, and then
remounted later as normal using /dev/md0.
However, now I get the following displayed on screen. It looks like the boot
loader doesn't like the partition type - but this hasn't changed. The splash
screen and menu all appear on-screen so GRUB at least can see the /boot/
partition to do this. (The following were collected having booted from the
rescue CD).
I have noticed that the mirror isn't symetrical either as there seems to be an
extra partition (
Anyone got any ideas
Booting 'Fedora (2.6.25-14.FC9)'
root(hd0,0)
Filesystem type ext2fs, partition type 0xfd
kernel /vmlinuz-2.6.25-14.fc9 ro root=/dev/md2 rhgb quiet
Error 15: File not found
Press any key to continue...
sh-3.2# mdadm -D /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Thu Dec 6 10:53:13 2007
Raid Level : raid1
Array Size : 1020032 (996.29 MiB 1044.51 MB)
Used Dev Size : 1020032 (996.29 MiB 1044.51 MB)
Raid Devices : 3
Total Devices : 3
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Tue Aug 26 12:43:54 2008
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Number Major Minor RaidDevice State
0 8 5 0 active sync /dev/sda5
1 8 19 1 active sync /dev/sdb3
2 8 66 2 active sync /dev/sde2
3 8 50 3 active sync /dev/sdd2
4 8 34 4 active sync /dev/sdc2
--
Gary Stainburn
This email does not contain private or confidential material as it
may be snooped on by interested government parties for unknown
and undisclosed purposes - Regulation of Investigatory Powers Act, 2000
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
08-26-2008, 02:22 PM
Gary Stainburn
more RAID whoe's
Part of the problem is that the /boot/grub/menu.lst wasn't written properly.
The initrd line was completely missing and the kernel line didn't have the
filename correct. The working entry now looks like:
Now when I boot up I'm back where I started with the two RAID devices not
working. I get:
Decompressing Linux... done.
Booting the kernel.
Red Hat mash version 6.0.52 starting
mdadm: no devices found for /dev/md2
mdadm: no devices found for /dev/md1
EXT3-fs: unable to read superblock
............
If I then re-boot using the rescure CD and run mdadm --examine /dev/md2 I get:
sh-3.2# mdadm --examine /dev/md2
mdadm: No md superblock detected on /dev/md2
If I unmount everything and do it on /tmp/md2 I get the same result, and also
with /dev/md0 and /tmp/md0.
I presume this is the problem, how do I fix it?
--
Gary Stainburn
This email does not contain private or confidential material as it
may be snooped on by interested government parties for unknown
and undisclosed purposes - Regulation of Investigatory Powers Act, 2000
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
more RAID whoe's
