[solved] RAID fails to boot in 2.6.17

[BLASTER_]

I may have a problem here my RAID array is very old. (3+ ? years)

I use /dev/md0 (raid0) as a root device, On upgrading from 2.6.15 to 2.6.17 my system will no longer boot. I recently installed mdadm and it says I have no identity information.

# mdadm -D /dev/md0

Code: Select all

mdadm: bad uuid: UUID=e68852fa:0e3e6c6c:8fe28a2b:d8835a2
mdadm: ARRAY line /dev/md0 has no identity information.
/dev/md0:
        Version : 00.90.03
  Creation Time : Thu Jan  6 10:00:16 2005
     Raid Level : raid0
     Array Size : 76967168 (73.40 GiB 78.81 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Thu Jan  6 10:00:16 2005
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

     Chunk Size : 32K

           UUID : e68852fa:0e3e6c6c:8fe28a2b:d8835a22
         Events : 0.3

    Number   Major   Minor   RaidDevice State
       0       3        3        0      active sync   /dev/hda3
       1      22        3        1      active sync   /dev/hdc3

(I just noticed it says creation time, I actually erased it then but reimaged the filesystem on it.)


# cat /etc/raidtab

Code: Select all

raiddev /dev/md0
        raid-level      0
        nr-raid-disks   2
        persistent-superblock 1
        chunk-size      32
        device          /dev/ide/hd/c0b0t0u0p3
        raid-disk       0
        device          /dev/ide/hd/c0b1t0u0p3
        raid-disk       1

# cat /etc/fstab

Code: Select all

/dev/md0                /               reiserfs        notail,noatime,user_xattr       0 1

# fdisk info

Code: Select all

/dev/hda3              75        4865    38483707+  fd  Linux raid autodetect

and

/dev/hdc3              75        4865    38483707+  fd  Linux raid autodetect

When I try to boot on it, I get "Please enter in your root device or type shell for a shell" I enter in /dev/md0 and it fails saying something about invalid raid device. When I go into a shell and check out the demesg I can see that the kernel finds the /dev/hdc3 disk but not /dev/hda3. 2.6.15 still boots without a problem so I'm kinda stuck.. I'm going to double check my kernel config I guess. One of the big things I'm wondering about is "mdadm: ARRAY line /dev/md0 has no identity information."

hmm...

[BLASTER_]

got it, partly..

ls /dev/hda
ls: /dev/hda: No such file or directory

So.. where did my hard disk go? Bios sees it.. 2.6.15 sees it.. hmmm..

[BLASTER_]

ok fixed it.

Disabled Device Drivers > ATA/ATAPI/MFM/RLL support > "Use old disk-only driver on primary interface"

Some sort of evil switch in 2.6.17