| 1 |
On Dec 11, 2012 7:57 AM, "Nilesh Govindrajan" <me@××××××××.com> wrote: |
| 2 |
> |
| 3 |
> On Tuesday 11 December 2012 05:18 PM, J. Roeleveld wrote: |
| 4 |
> > |
| 5 |
> > Ouch, auto-detect does not work with metadata 1.2. |
| 6 |
> > Please read the man-page section: |
| 7 |
> > === |
| 8 |
> > --auto-detect |
| 9 |
> > Request that the kernel starts any auto-detected arrays. This can |
| 10 |
only |
| 11 |
> > work if md is compiled into the kernel - not if it is a module. Arrays |
| 12 |
> > can be auto-detected by the kernel if all the components are in |
| 13 |
> > primary MS-DOS partitions with partition type FD, and all use v0.90 |
| 14 |
> > metadata. In-kernel autodetect is not recommended for new |
| 15 |
> > installations. Using mdadm to detect and assemble arrays - possibly in |
| 16 |
> > an initrd - is substantially more flexible and should be preferred. |
| 17 |
> > === |
| 18 |
> > |
| 19 |
> > Please rebuild the raid-device using v0.90 metadata and try again. |
| 20 |
> > |
| 21 |
> |
| 22 |
> I never had mdadm running in boot runlevel and I don't have a modular |
| 23 |
> kernel. I have compiled everything into the kernel and hence no initrd |
| 24 |
> either as I said earlier. |
| 25 |
> |
| 26 |
> Raid autodetection seems to work even _without_ mdadm running. |
| 27 |
> |
| 28 |
> ------------------------------ |
| 29 |
> |
| 30 |
> [ 1.202481] md: Waiting for all devices to be available before |
| 31 |
autodetect |
| 32 |
> [ 1.204268] md: If you don't use raid, use raid=noautodetect |
| 33 |
> [ 1.206201] md: Autodetecting RAID arrays. |
| 34 |
> [ 1.232482] md: invalid raid superblock magic on sdb1 |
| 35 |
> [ 1.234306] md: sdb1 does not have a valid v0.90 superblock, not |
| 36 |
> importing! |
| 37 |
> [ 1.263187] md: invalid raid superblock magic on sdd1 |
| 38 |
> [ 1.265034] md: sdd1 does not have a valid v0.90 superblock, not |
| 39 |
> importing! |
| 40 |
> [ 1.285106] md: invalid raid superblock magic on sdc1 |
| 41 |
> [ 1.286960] md: sdc1 does not have a valid v0.90 superblock, not |
| 42 |
> importing! |
| 43 |
> [ 1.288787] md: Scanned 3 and added 0 devices. |
| 44 |
> [ 1.290590] md: autorun ... |
| 45 |
> [ 1.292380] md: ... autorun DONE. |
| 46 |
> [ 1.340838] UDF-fs: warning (device sda1): udf_fill_super: No |
| 47 |
> partition found (1) |
| 48 |
> [ 1.350473] XFS (sda1): Mounting Filesystem |
| 49 |
> [ 1.454096] usb usb5: suspend_rh (auto-stop) |
| 50 |
> [ 1.454130] usb usb4: suspend_rh (auto-stop) |
| 51 |
> [ 1.455673] usb usb2: suspend_rh (auto-stop) |
| 52 |
> [ 1.455698] usb usb3: suspend_rh (auto-stop) |
| 53 |
> [ 1.573933] XFS (sda1): Ending clean mount |
| 54 |
> [ 1.575762] VFS: Mounted root (xfs filesystem) readonly on device 8:1. |
| 55 |
> [ 1.578193] Freeing unused kernel memory: 456k freed |
| 56 |
> [ 1.580154] BFS CPU scheduler v0.425 by Con Kolivas. |
| 57 |
> [ 2.503599] systemd-udevd[974]: starting version 196 |
| 58 |
> [ 2.704048] hub 2-0:1.0: hub_suspend |
| 59 |
> [ 2.704063] usb usb2: bus auto-suspend, wakeup 1 |
| 60 |
> [ 2.704068] usb usb2: suspend_rh |
| 61 |
> [ 2.704091] hub 3-0:1.0: hub_suspend |
| 62 |
> [ 2.704098] usb usb3: bus auto-suspend, wakeup 1 |
| 63 |
> [ 2.704102] usb usb3: suspend_rh |
| 64 |
> [ 2.708031] hub 4-0:1.0: hub_suspend |
| 65 |
> [ 2.708041] usb usb4: bus auto-suspend, wakeup 1 |
| 66 |
> [ 2.708046] usb usb4: suspend_rh |
| 67 |
> [ 2.712023] hub 5-0:1.0: hub_suspend |
| 68 |
> [ 2.712030] usb usb5: bus auto-suspend, wakeup 1 |
| 69 |
> [ 2.712034] usb usb5: suspend_rh |
| 70 |
> [ 2.794061] hub 1-6:1.0: hub_suspend |
| 71 |
> [ 2.794072] usb 1-6: unlink qh256-0001/ffff8800bb832980 start 1 [1/0 |
| 72 |
us] |
| 73 |
> [ 2.797202] usb 1-6: usb auto-suspend, wakeup 1 |
| 74 |
> [ 2.973953] md: bind<sdb1> |
| 75 |
> [ 3.020879] md: bind<sdc1> |
| 76 |
> [ 3.086724] md: bind<sdd1> |
| 77 |
> [ 3.087690] bio: create slab <bio-1> at 1 |
| 78 |
> [ 3.087705] md/raid0:md0: md_size is 2266111488 sectors. |
| 79 |
> [ 3.087708] md: RAID0 configuration for md0 - 3 zones |
| 80 |
> [ 0.524821] ACPI: Invalid Power Resource to register! |
| 81 |
> [ 3.087711] md: zone0=[ |
| 82 |
> [ 3.087714] sdb1/sdc1/sdd1] |
| 83 |
> [ 3.087721] zone-offset= 0KB, device-offset= |
| 84 |
> 0KB, size= 468863328KB |
| 85 |
> [ 3.087723] md: zone1=[sdb1/sdc1] |
| 86 |
> [ 3.087730] zone-offset= 468863328KB, device-offset= |
| 87 |
> 156287776KB, size= 664191360KB |
| 88 |
> [ 3.087732] md: zone2=[sdb1] |
| 89 |
> [ 3.087737] zone-offset=1133054688KB, device-offset= |
| 90 |
> 488383456KB, size= 1056KB |
| 91 |
> |
| 92 |
> [ 3.087752] md0: detected capacity change from 0 to 1160249081856 |
| 93 |
> [ 3.098375] md0: unknown partition table |
| 94 |
> |
| 95 |
> ------------------------------------------------------------------------- |
| 96 |
> |
| 97 |
> Where did md0 come from if it was not setup by mdadm? |
| 98 |
|
| 99 |
Metadata format 0.9 supports auto-detection by the kernel. |
| 100 |
|
| 101 |
> |
| 102 |
> -- |
| 103 |
> Nilesh Govindarajan |
| 104 |
> http://nileshgr.com |
| 105 |
> |
Archives