FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 08-26-2008, 12:17 PM
Gary Stainburn
 
Default more RAID whoe's

Hi folks.

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

UUID : 1f31c4b8:d602299e:6378c18c:1cc4f42f
Events : 0.18

Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 2 1 active sync /dev/sda2
2 8 17 2 active sync /dev/sdb1

sh-3.2# mdadm -D /dev/md2
/dev/md2:
Version : 00.90.03
Creation Time : Thu Dec 6 10:37:22 2007
Raid Level : raid5
Array Size : 1937180672 (1847.44 GiB 1983.67 GB)
Used Dev Size : 484295168 (461.86 GiB 495.92 GB)
Raid Devices : 5
Total Devices : 5
Preferred Minor : 2
Persistence : Superblock is persistent

Update Time : Tue Aug 26 12:44:15 2008
State : clean
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 256K

UUID : dee71d7b:567f2962:2d68770a:c36412ac
Events : 0.777308

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
 
Old 08-26-2008, 02:22 PM
Gary Stainburn
 
Default 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:

#boot=/dev/md0
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.25-14.fc9)
root (hd0,0)
kernel /vmlinuz-2.6.25-14.fc9.i686 ro root=/dev/md2 rhgb quiet
initrd /initrd-2.6.25-14.fc9.i686.img

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
 

Thread Tools




All times are GMT. The time now is 01:28 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org