lacie 5 big network v.1 please support for fvdw

[taetae]

ahahaha I had seen the greatness I thought it was normal for the changes made in any case 19 kernel:


is very much along the log maybe I can not take it all ....
you also need the kernel log 17??

putty log : 19 kernel log.doc Attachment

[fvdw]

log of kernel 19 is rubish, yes I need the output of kernel 17

seems the adapatations I made confuses the kernel, in 17 only print messages were added

[taetae]

17 kernel attached
kernel 17 log:

[fvdw]

mmm...doesn't seem to like my printk statements, give me a minute..

[fvdw]

ok kernel 20 sent, its the same as 19 (so modified for diskmap but adapted print commands)

[taetae]

kernel 20:

[fvdw]

:punk
this one produces the printk and has a disk map

Code: Select all

ata5.00: configured for UDMA/133
scsi 4:0:0:0: Direct-Access     ATA      WDC WD5000AADS-0 01.0 PQ: 0 ANSI: 5
fvdw1 disk index 0
fvdw2 disk indexfvdw 0
fvdw3 disk indexfvdw 0
fvdw4 disk diskname= sda
sd 4:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
sd 4:0:0:0: [sda] Write Protect is off
sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
sd 4:0:0:0: [sda] Attached SCSI disk


Now repeat but with an additional disk in slot 5

[taetae]

slot1 + slot5

[fvdw]

ok we are making progress

Code: Select all

ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      WDC WD20EZRX-00D 80.0 PQ: 0 ANSI: 5
fvdw1 disk index 0
fvdw2 disk indexfvdw 0
fvdw3 disk indexfvdw 4
fvdw4 disk diskname= sde
sd 0:0:0:0: [sde] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 0:0:0:0: [sde] 4096-byte physical blocks
sd 0:0:0:0: [sde] Write Protect is off
sd 0:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata2: SATA link down (SStatus 0 SControl 300)
ata9: failed to resume link (SControl 0)
ata9: SATA link down (SStatus 0 SControl 0)
 sde: sde1
sd 0:0:0:0: [sde] Attached SCSI disk
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata5.00: ATA-8: WDC WD5000AADS-00S9B0, 01.00A01, max UDMA/133
ata5.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata5.00: configured for UDMA/133
scsi 4:0:0:0: Direct-Access     ATA      WDC WD5000AADS-0 01.0 PQ: 0 ANSI: 5
fvdw1 disk index 1
fvdw2 disk indexfvdw 1
fvdw3 disk indexfvdw 0
fvdw4 disk diskname= sda
sd 4:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)


It now detects both disks and assigns the correct name to it doesn't seems to create a kernel panic anymore
I think the "dev nodes" now needs to be updated as it fails to mount sda2, probably because the device node for sda2 is wrong. Due to deviation sequence lacie uses. The device node is file in the folder /dev and it is probably pointing to disk 5 now.

Code: Select all

Freeing init memory: 128K
start rcS
set global environment params
mount proc
remount root file system rw
EXT3-fs (sda7): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (sda7): using internal journal
mount sysfs
start boot log
booting using sda2 file system...
mount: mounting /dev/sda2 on /fvdw-chroot failed: No such device or address
chroot: can't execute '/etc/init.d/rcS': No such file or directory


We need to run the program udevstart to correct this, let me think a few minutes to think over how to do this
In the meantime you could also try what happens if you put the disk that is now in slot 5 in slot 2 to see if the kernel now is able to find a disk in slot 2.

[taetae]

in slot 5 there is no kernel

kernel only in the disc slot 1 reverse it?