Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RAID 1 failure



I wrote:
>I have been using two SCSI disk partitions in a RAID 1 configuration
>for several months.  However, I now get this message at system boot:
>
>  fsck.ext3: Invalid argument while trying to open /dev/md0
>  /dev/md0:
>  The superblock could not be read or does not describe a correct ext2
...

I took /dev/md0 out of /etc/fstab, and the system booted fine.  I then
ran "startraid /dev/md0" and it started syncing the RAID volume.  That
finished about 20 min later.  In the mean time, I mounted the volume.
No complaints to any of this.

Remember that I'd left the partition IDs at 0x83:

>  vanzandt:/proc# fdisk -l
>     Device Boot    Start       End    Blocks   Id  System
>  /dev/sda1             1         5     40131   83  Linux
>  /dev/sda2             6      3895  31246425   83  Linux
>  /dev/sda3          3896      4381   3903795   83  Linux
>  /dev/sda4          4382      4492    891607+  82  Linux swap
...
>  /dev/sdb1             1       596   4787338+  83  Linux
>  /dev/sdb2           597      4486  31246425   83  Linux
>  
>(I've not changed the partition IDs to 0xfd for autodetection.)

Maybe RAID detection only worked by luck.  Anyway, I unmounted the
volume, changed the IDs to 0xfd, and rebooted.  No problems so far.

		- Jim Van Zandt




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org