| 1 |
> On Tuesday 11 December 2012 05:18 PM, J. Roeleveld wrote: |
| 2 |
>> |
| 3 |
>> Ouch, auto-detect does not work with metadata 1.2. |
| 4 |
>> Please read the man-page section: |
| 5 |
>> === |
| 6 |
>> --auto-detect |
| 7 |
>> Request that the kernel starts any auto-detected arrays. This can |
| 8 |
>> only |
| 9 |
>> work if md is compiled into the kernel - not if it is a module. Arrays |
| 10 |
>> can be auto-detected by the kernel if all the components are in |
| 11 |
>> primary MS-DOS partitions with partition type FD, and all use v0.90 |
| 12 |
>> metadata. In-kernel autodetect is not recommended for new |
| 13 |
>> installations. Using mdadm to detect and assemble arrays - possibly in |
| 14 |
>> an initrd - is substantially more flexible and should be preferred. |
| 15 |
>> === |
| 16 |
>> |
| 17 |
>> Please rebuild the raid-device using v0.90 metadata and try again. |
| 18 |
>> |
| 19 |
> |
| 20 |
> I never had mdadm running in boot runlevel and I don't have a modular |
| 21 |
> kernel. I have compiled everything into the kernel and hence no initrd |
| 22 |
> either as I said earlier. |
| 23 |
> |
| 24 |
> Raid autodetection seems to work even _without_ mdadm running. |
| 25 |
> |
| 26 |
> ------------------------------ |
| 27 |
> |
| 28 |
> [ 1.202481] md: Waiting for all devices to be available before |
| 29 |
> autodetect |
| 30 |
> [ 1.204268] md: If you don't use raid, use raid=noautodetect |
| 31 |
> [ 1.206201] md: Autodetecting RAID arrays. |
| 32 |
> [ 1.232482] md: invalid raid superblock magic on sdb1 |
| 33 |
> [ 1.234306] md: sdb1 does not have a valid v0.90 superblock, not |
| 34 |
> importing! |
| 35 |
> [ 1.263187] md: invalid raid superblock magic on sdd1 |
| 36 |
> [ 1.265034] md: sdd1 does not have a valid v0.90 superblock, not |
| 37 |
> importing! |
| 38 |
> [ 1.285106] md: invalid raid superblock magic on sdc1 |
| 39 |
> [ 1.286960] md: sdc1 does not have a valid v0.90 superblock, not |
| 40 |
> importing! |
| 41 |
> [ 1.288787] md: Scanned 3 and added 0 devices. |
| 42 |
|
| 43 |
This clearly indicates that the "autostart" is not working |
| 44 |
|
| 45 |
|
| 46 |
> [ 3.087705] md/raid0:md0: md_size is 2266111488 sectors. |
| 47 |
> [ 3.087708] md: RAID0 configuration for md0 - 3 zones |
| 48 |
> [ 0.524821] ACPI: Invalid Power Resource to register! |
| 49 |
> [ 3.087711] md: zone0=[ |
| 50 |
> [ 3.087714] sdb1/sdc1/sdd1] |
| 51 |
> [ 3.087721] zone-offset= 0KB, device-offset= |
| 52 |
> 0KB, size= 468863328KB |
| 53 |
> [ 3.087723] md: zone1=[sdb1/sdc1] |
| 54 |
> [ 3.087730] zone-offset= 468863328KB, device-offset= |
| 55 |
> 156287776KB, size= 664191360KB |
| 56 |
> [ 3.087732] md: zone2=[sdb1] |
| 57 |
> [ 3.087737] zone-offset=1133054688KB, device-offset= |
| 58 |
> 488383456KB, size= 1056KB |
| 59 |
> |
| 60 |
> [ 3.087752] md0: detected capacity change from 0 to 1160249081856 |
| 61 |
> [ 3.098375] md0: unknown partition table |
| 62 |
|
| 63 |
Something found and started md0 after the autoraid-detect clearly failed. |
| 64 |
|
| 65 |
> Where did md0 come from if it was not setup by mdadm? |
| 66 |
|
| 67 |
What does "rc-status" show right after boot? |
| 68 |
|
| 69 |
-- |
| 70 |
Joost |
Archives