| 1 |
Hi, |
| 2 |
|
| 3 |
thanks a lot for both answers. |
| 4 |
|
| 5 |
I've just checked my kernel config and CONFIG_SCSI_SCAN_ASYNC is not setted |
| 6 |
so gonna take a look at it all with "set -x". |
| 7 |
|
| 8 |
Thanks :) |
| 9 |
|
| 10 |
2012/10/26 J. Roeleveld <joost@××××××××.org> |
| 11 |
|
| 12 |
> Pau Peris <sibok1981@×××××.com> wrote: |
| 13 |
>> |
| 14 |
>> Hi, |
| 15 |
>> |
| 16 |
>> |
| 17 |
>> i'm running GNU/Gentoo Linux with a custom compiled kernel and i've just |
| 18 |
>> migrated from a 2.6 kernel to a 3.5. |
| 19 |
>> |
| 20 |
>> |
| 21 |
>> As my HD's are on raid 0 mode i use a custom initrd file in order to be |
| 22 |
>> able to boot. While kernel 2.6 is able to boot without problems the new 3.5 |
| 23 |
>> compiled kernel fails to boot complaining about "no block devices found". |
| 24 |
>> After taking a look at initrd.cpio contained scripts i can see the failure |
| 25 |
>> message is given by mdadm tool. |
| 26 |
>> |
| 27 |
>> |
| 28 |
>> Does anyone has a clue about that? Thansk in advanced. :) |
| 29 |
>> |
| 30 |
>> |
| 31 |
> Paul, |
| 32 |
> |
| 33 |
> I had a similar issue with a new system. There it was caused by mdadm |
| 34 |
> trying to start the raid devices before all the drives were identified. |
| 35 |
> Try disabling "Asynchronous SCSI scanning" in the kernel config. |
| 36 |
> (CONFIG_SCSI_SCAN_ASYNC) |
| 37 |
> Or add "scsi_mod.scan=sync" to the kernel commandline to see if it's the |
| 38 |
> same cause. |
| 39 |
> |
| 40 |
> -- |
| 41 |
> Joost |
| 42 |
> -- |
| 43 |
> Sent from my Android phone with K-9 Mail. Please excuse my brevity. |
| 44 |
> |
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
-- |
| 49 |
Pau Peris Rodriguez |
| 50 |
http://www.pauperis.com |
| 51 |
|
| 52 |
Aquest correu electrònic conté informació de caràcter confidencial dirigida |
| 53 |
exclusivament al seu/s destinatari/s tant mateix va dirigit exclusivament |
| 54 |
als seu/s destinatari/s primari/s present/s. Així, queda prohibida la seva |
| 55 |
divulgació, copia o distribució a tercers sense prèvia autorització escrita |
| 56 |
per part de Pau Peris Rodriguez. En cas d'haver rebut aquesta informació |
| 57 |
per error, es demana que es notifiqui immediatament d'aquesta circumstancia |
| 58 |
mitjançant la direcció electrònica de la persona del emissor. |
Archives