Re: Assemblaggio disco RAID all'avvio

[Dario Piantanida <dario.piantanida@gmail.com>]

L'idea che mi sono fatto è che non è mai stato il kernel o altro di sistema ad assemblare md2, ma lo script custom in python; avendo tentato di aggiornare python devo averlo mandato in crisi nel senso che non si accorge che il volume è disponibile per l'assemblaggio.

Alla fine ho trovato questo log:

2014-10-01 16:52:11,415 ERROR [SYSTEM] : Daemon could not start

Traceback (most recent call last):

  File "platformd/platformd.py", line 216, in <module>

  File "platformd/daemonize.py", line 137, in __init__

  File "platformd/core/library/initd.py", line 63, in bootup

  File "platformd/core/library/volume_monitor.py", line 33, in volume_status_check_and_report

  File "platformd/core/library/volume_monitor.py", line 137, in check_volume_status

  File "platformd/backend/storage/volume.py", line 2828, in get_raid_status

KeyError: 2

Il problema che non c'è il file .py ma il .pyc compilato, quindi... come faccio sapere che cosa cerca di fare??

Grazie!!!!

On Wed, Oct 1, 2014 at 2:17 PM, Dario Piantanida <dario.piantanida@gmail.com> wrote:

Aspetta... non credo che questa fosse la situazione precedente, perché quell'errore c'è sempre stato... e non vedo come possa essere cambiato da solo...

Ripesco il vecchio log, questo è quello che succedeva quando andava (saltando qualche riga) e con lo stesso errore:

Mar 12 20:12:50 LG-NAS kernel: [    0.493550] 2 cmdlinepart partitions found on MTD device spi_flash

Mar 12 20:12:50 LG-NAS kernel: [    0.499762] Creating 2 MTD partitions on "spi_flash":

Mar 12 20:12:50 LG-NAS kernel: [    0.504862] 0x000000000000-0x000000078000 : "uboot"

Mar 12 20:12:50 LG-NAS kernel: [    0.510989] 0x000000078000-0x000000079000 : "env"

Mar 12 20:12:50 LG-NAS kernel: [    0.587116] md: linear personality registered for level -1

Mar 12 20:12:50 LG-NAS kernel: [    0.592659] md: raid0 personality registered for level 0

Mar 12 20:12:50 LG-NAS kernel: [    0.598001] md: raid1 personality registered for level 1

Mar 12 20:12:50 LG-NAS kernel: [    1.100097] *****************************************

Mar 12 20:12:50 LG-NAS kernel: [    1.105175] Model: Hitachi HDS721010CLA332                 C, ssc word: 0c04

Mar 12 20:12:50 LG-NAS kernel: [    1.112261] SSC Status : ON

Mar 12 20:12:50 LG-NAS kernel: [    1.115069] *****************************************

Mar 12 20:12:50 LG-NAS kernel: [    1.120155] Turning on SATA Port SSC (On) (fed82050= 9b10d5)

Mar 12 20:12:50 LG-NAS kernel: [    1.140079] ata1.00: configured for UDMA/133

Mar 12 20:12:50 LG-NAS kernel: [    1.144727] scsi 0:0:0:0: Direct-Access     ATA      Hitachi HDS72101 JP4O PQ: 0 ANSI: 5

Mar 12 20:12:50 LG-NAS kernel: [    1.153795] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)

Mar 12 20:12:50 LG-NAS kernel: [    1.161974] sd 0:0:0:0: Attached scsi generic sg0 type 0

Mar 12 20:12:50 LG-NAS kernel: [    1.167644] sd 0:0:0:0: [sda] Write Protect is off

Mar 12 20:12:50 LG-NAS kernel: [    1.172495] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00

Mar 12 20:12:50 LG-NAS kernel: [    1.172612] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Mar 12 20:12:50 LG-NAS kernel: [    1.222533]  sda: sda1 sda2 sda3

Mar 12 20:12:50 LG-NAS kernel: [    1.227296] sd 0:0:0:0: [sda] Attached SCSI disk

Mar 12 20:12:51 LG-NAS kernel: [    1.510041] ata2: SATA link down (SStatus 0 SControl F300)

Mar 12 20:12:51 LG-NAS kernel: [    1.515632] md: Waiting for all devices to be available before autodetect

Mar 12 20:12:51 LG-NAS kernel: [    1.522462] md: If you don't use raid, use raid=noautodetect

Mar 12 20:12:51 LG-NAS kernel: [    1.528897] md: Autodetecting RAID arrays.

Mar 12 20:12:51 LG-NAS kernel: [    1.576559] md: invalid raid superblock magic on sda3

Mar 12 20:12:51 LG-NAS kernel: [    1.581653] md: sda3 does not have a valid v0.90 superblock, not importing!

Mar 12 20:12:51 LG-NAS kernel: [    1.588658] md: Scanned 3 and added 2 devices.

Mar 12 20:12:51 LG-NAS kernel: [    1.593126] md: autorun ...

Mar 12 20:12:51 LG-NAS kernel: [    1.595936] md: considering sda2 ...

Mar 12 20:12:51 LG-NAS kernel: [    1.599557] md:  adding sda2 ...

Mar 12 20:12:51 LG-NAS kernel: [    1.602822] md: sda1 has different UUID to sda2

Mar 12 20:12:51 LG-NAS kernel: [    1.607971] md: created md1

Mar 12 20:12:51 LG-NAS kernel: [    1.610795] md: bind<sda2>

Mar 12 20:12:51 LG-NAS kernel: [    1.613562] md: running: <sda2>

Mar 12 20:12:51 LG-NAS kernel: [    1.616927] bio: create slab <bio-1> at 1

Mar 12 20:12:51 LG-NAS kernel: [    1.621153] md/raid1:md1: active with 1 out of 2 mirrors

Mar 12 20:12:51 LG-NAS kernel: [    1.626570] md1: detected capacity change from 0 to 8000569344

Mar 12 20:12:51 LG-NAS kernel: [    1.632590] md: considering sda1 ...

Mar 12 20:12:51 LG-NAS kernel: [    1.636214] md:  adding sda1 ...

Mar 12 20:12:51 LG-NAS kernel: [    1.639462] md: created md0

Mar 12 20:12:51 LG-NAS kernel: [    1.642284] md: bind<sda1>

Mar 12 20:12:51 LG-NAS kernel: [    1.645043] md: running: <sda1>

Mar 12 20:12:51 LG-NAS kernel: [    1.648514] md/raid1:md0: active with 1 out of 2 mirrors

Mar 12 20:12:51 LG-NAS kernel: [    1.653949] md0: detected capacity change from 0 to 22999400448

Mar 12 20:12:51 LG-NAS kernel: [    1.660013] md: ... autorun DONE.

Mar 12 20:12:51 LG-NAS kernel: [    1.696908]  md0: unknown partition table

Mar 12 20:12:51 LG-NAS kernel: [    1.707581] EXT3-fs: barriers not enabled

Mar 12 20:12:51 LG-NAS kernel: [    1.720209] kjournald starting.  Commit interval 5 seconds

Mar 12 20:12:51 LG-NAS kernel: [    1.725782] EXT3-fs (md0): warning: maximal mount count reached, running e2fsck is recommended

Mar 12 20:12:51 LG-NAS kernel: [    1.770381] EXT3-fs (md0): using internal journal

Mar 12 20:12:51 LG-NAS kernel: [    1.775126] EXT3-fs (md0): mounted filesystem with writeback data mode

Mar 12 20:12:51 LG-NAS kernel: [    1.781740] VFS: Mounted root (ext3 filesystem) on device 9:0.

Mar 12 20:12:51 LG-NAS kernel: [    4.144861] md1: detected capacity change from 0 to 8000569344

Mar 12 20:12:51 LG-NAS kernel: [    4.181789]  md1: unknown partition table

Mar 12 20:12:51 LG-NAS kernel: [    4.434476] md1: detected capacity change from 0 to 8000569344

Mar 12 20:12:51 LG-NAS kernel: [    4.448924]  md1: unknown partition table

Mar 12 20:12:51 LG-NAS kernel: [   25.738145] md: md2 stopped.

Mar 12 20:12:51 LG-NAS kernel: [   25.746187] md: bind<sda3>

Mar 12 20:12:51 LG-NAS kernel: [   25.839677] md/raid1:md2: active with 1 out of 1 mirrors

Mar 12 20:12:51 LG-NAS kernel: [   25.845175] md2: detected capacity change from 0 to 968202510336

Mar 12 20:12:51 LG-NAS kernel: [   25.865579] md2: detected capacity change from 0 to 968202510336

Mar 12 20:12:51 LG-NAS kernel: [   25.950418]  md2: unknown partition table

Mar 12 20:12:51 LG-NAS kernel: [   26.150170] EXT4-fs (md2): warning: maximal mount count reached, running e2fsck is recommended

Mar 12 20:12:51 LG-NAS kernel: [   26.277719] EXT4-fs (md2): mounted filesystem with writeback data mode. Opts: data="">

On Wed, Oct 1, 2014 at 12:25 PM, Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org> wrote:

On 01/10/2014 12:11, Dario Piantanida wrote:
> Eccolo qua!
>
> root@LG-NAS:~# cat /proc/mdstat
> Personalities : [linear] [raid0] [raid1]
> md2 : active raid1 sda3[0]
>       945510264 blocks super 1.2 [1/1] [U]

allora il problema è che la sda3 ha il superblock in formato 1.2 mentre
il kernel la vuole in 0.90.

>     [...]
>     > Sep 28 20:53:27 LG-NAS kernel: [ 1.528890] md: Autodetecting RAID arrays.
>     > Sep 28 20:53:27 LG-NAS kernel: [ 1.575817] md: invalid raid superblock
>     > magic on sda3
>     > Sep 28 20:53:27 LG-NAS kernel: [ 1.580909] md: sda3 does not have a
>     > valid v0.90 superblock, not importing!

Dovresti convertirla, anche se in genere si fa il contrario: da 0.90 a
1.2. Non so quindi dirti come fare.

Ciao,
G