[Eisfair] [e1] Fehler nach update auf base v2.8.5 und eiskernel-smp v4.4.0

[Marcus Röckrath]

Hallo Wolfgang,

W. Loefstedt wrote:

>> Kannst du bitte mal die Ausgabe von dmesg des Boots vom 4.9.196; etwa so
>> etwas wie hier:
> 
> [   14.734469] md: bind<sdb1>
> [   14.749356] md: bind<sdb2>
> [   14.764462] md: bind<sdb3>
> [   14.836633] md: bind<sda2>
> [   14.863688] random: fast init done
> [   14.873474] md/raid1:md2: active with 2 out of 2 mirrors
> [   14.874785] md: bind<sda1>
> [   14.877315] md: bind<sda3>
> [   14.896261] md/raid1:md1: active with 2 out of 2 mirrors
> [   14.896338] md1: detected capacity change from 0 to 65667072
> [   14.897211]  md1:
> [   14.899197] md/raid1:md3: active with 2 out of 2 mirrors
> [   14.899274] md3: detected capacity change from 0 to 77802831872
> [   14.947564] md2: detected capacity change from 0 to 2154954752
> [   17.206512] EXT4-fs (md3): mounting ext3 file system using the ext4
> subsystem
> [   17.248469] EXT4-fs (md3): mounted filesystem with ordered data mode.
> Opts: (null)
> [   22.788599] udevd[1378]: starting version 3.2.8
> [   22.887548] urandom_read: 4 callbacks suppressed
> [   22.887552] random: udevd: uninitialized urandom read (16 bytes read)
> [   22.924318] random: udevd: uninitialized urandom read (16 bytes read)
> [   22.950626] random: udevd: uninitialized urandom read (16 bytes read)
> [   23.172304] udevd[1379]: starting eudev-3.2.8
> 
>> Mich interessiert, wie bei diesem erfolgreichen Boot die md nummeriert
>> sind.

Vom erfolgreichen Boot des 4.9.196.

-- 
Gruß Marcus
[eisfair-Team]