Save original firmware for later restoration

[fvdw]

mine is different

root@fvdwsl-base:/ # ls -al /dev/sda
brw-rw---- 1 root root 8, 16 2014-06-08 09:45 /dev/sda
root@fvdwsl-base:/ # ls -al /dev/sdb4
brw-rw---- 1 root root 8, 4 2014-06-08 09:45 /dev/sdb4

please list full output of

Code: Select all

ls -al /dev/sd*

[matzi]

I think you meant this:

root@fvdwsl-base:/ # ls -al /dev/sd*
brw-rw---- 1 root root 8, 16 2014-06-08 09:45 /dev/sda
brw-rw---- 1 root root 8, 17 2014-06-08 09:45 /dev/sda1
brw-rw---- 1 root root 8, 18 2014-06-08 09:45 /dev/sda2
brw-rw---- 1 root root 8, 19 2014-06-08 21:06 /dev/sda3
brw-rw---- 1 root root 8, 20 2014-06-08 09:45 /dev/sda4
brw-rw---- 1 root root 8, 21 2014-06-08 09:45 /dev/sda5
brw-rw---- 1 root root 8, 22 2014-06-08 09:45 /dev/sda6
brw-rw---- 1 root root 8, 23 2014-06-08 09:45 /dev/sda7
brw-rw---- 1 root root 8, 24 2014-06-08 09:45 /dev/sda8
brw-rw-rw- 1 root root 8, 9 2013-08-09 20:22 /dev/sda9
brw-rw---- 1 root root 8, 0 2014-06-08 09:45 /dev/sdb
brw-rw---- 1 root root 8, 1 2014-06-08 09:45 /dev/sdb1
brw-rw---- 1 root root 8, 2 2014-06-08 09:45 /dev/sdb2
brw-rw---- 1 root root 8, 3 2014-06-08 09:45 /dev/sdb3
brw-rw---- 1 root root 8, 4 2014-06-08 09:45 /dev/sdb4
brw-rw---- 1 root root 8, 5 2014-06-08 09:45 /dev/sdb5
brw-rw---- 1 root root 8, 6 2014-06-08 09:45 /dev/sdb6
brw-rw---- 1 root root 8, 7 2014-06-08 09:45 /dev/sdb7
brw-rw---- 1 root root 8, 8 2014-06-08 09:45 /dev/sdb8

[Jocko]

Now
device 3: is the one on bus number 0:3:0:0 (= slot 1)
device 2: is the one on bus 0:2:0:0 (=slot 2)

This confirms my idea :
WD20 is in slot 1 and should be 0:3:0:0 and WD25 in slot 2 and should be 0:2:0:0 but in the following dmesg (dmesg2), we have the opposite case.

Jocko maybe I wasn't precise enough. The dmesg you checked first is made with the desired disc WD25.. in slot2. I added dmeg2 then were WD25 is in slot1

Sorry I did not read carefully this.

You have: WDC WD20 in slot1 and its devicename should be sda and WDC WD25 in slot2 and its devicename should be sdb

But I read in your dmesg2 this :

Code: Select all

scsi 0:2:0:0: Direct-Access     ATA      WDC WD20EARS-00M 50.0 PQ: 0 ANSI: 5
[   21.064261] fvdw1 disk index before get_sd_name = 0
[   21.069169] device-name= sata_mv
[   21.072384] fvdw2 disk index after get_sd_name = 1
[   21.077182] fvdw3 prefix[0]=s  prefix[1]=d
[   21.081257] fvdw4 diskname = sdb
sd 0:2:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

and

[   21.093209] scsi 0:3:0:0: Direct-Access     ATA      WDC WD25EZRX-00A 80.0 PQ: 0 ANSI: 5
[   21.115968] fvdw1 disk index before get_sd_name = 1
[   21.120820] device-name= sata_mv
[   21.124032] fvdw2 disk index after get_sd_name = 0
[   21.129699] fvdw3 prefix[0]=s  prefix[1]=d
[   21.133780] fvdw4 diskname = sda
[   21.137473] sd 0:3:0:0: [sda] 4883781168 512-byte logical blocks: (2.50 TB/2.27 TiB)

WDC WD20 in slot1 and its devicename is sdb and WDC WD25 in slot2 and its devicename is sda :pound

So I assume that you have an internal cable issue (plug swap)...and it is why you must plug in the system disk in the 2d slot.

fvdw has to confirm this and in this case you need a special kernel version...

[matzi]

and this with swapped discs

root@fvdwsl-base:/ # ls -al /dev/sd*
brw-rw---- 1 root root 8, 16 2014-06-08 08:50 /dev/sda
brw-rw---- 1 root root 8, 17 2014-06-08 08:50 /dev/sda1
brw-rw---- 1 root root 8, 18 2014-06-08 08:50 /dev/sda2
brw-rw---- 1 root root 8, 19 2014-06-08 20:30 /dev/sda3
brw-rw---- 1 root root 8, 20 2014-06-08 08:50 /dev/sda4
brw-rw---- 1 root root 8, 21 2014-06-08 08:50 /dev/sda5
brw-rw---- 1 root root 8, 22 2014-06-08 08:50 /dev/sda6
brw-rw---- 1 root root 8, 23 2014-06-08 08:50 /dev/sda7
brw-rw---- 1 root root 8, 24 2014-06-08 08:50 /dev/sda8
brw-rw-rw- 1 root root 8, 9 2013-08-09 19:22 /dev/sda9
brw-rw---- 1 root root 8, 0 2014-06-08 09:16 /dev/sdb
brw-rw---- 1 root root 8, 1 2014-06-08 08:50 /dev/sdb1
brw-rw---- 1 root root 8, 2 2014-06-08 08:50 /dev/sdb2
brw-rw---- 1 root root 8, 3 2014-06-08 08:50 /dev/sdb3
brw-rw---- 1 root root 8, 4 2014-06-08 08:50 /dev/sdb4
brw-rw---- 1 root root 8, 5 2014-06-08 08:50 /dev/sdb5
brw-rw---- 1 root root 8, 6 2014-06-08 08:50 /dev/sdb6
brw-rw---- 1 root root 8, 7 2014-06-08 08:50 /dev/sdb7
brw-rw---- 1 root root 8, 8 2014-06-08 08:50 /dev/sdb8

[fvdw]

this is ok

in which slot was the 2.5TB disk when you produced the "ide part" output in the u-boot console ?

[matzi]

in slot1, most left slot

[fvdw]

thats a pity if it would have been in slot 2 I would have agreed with a cable issue

this is in the output you posted

Code: Select all

    [0 0 3]: Enable DMA mode
    Device 3 @ 0 0 3:
    Model: WDC WD25EZRX-00AZ6B0 Firm: 80.00A80 Ser#: WD-WCC
    190001482
    Type: Hard Disk
    Supports 48-bit addressing
    Capacity: 2384658.7 MB = 2328.7 GB (0 x 1)
    Port Multiplier found @ 0 1. Vendor: 11ab ports: 4

and the boot loader looks at this device first for the kernel so it should boot from the disk in slot 1

I saw in your dmesg output (dmesg and dmeg2) that it mentions the same kernel (3.13.6)
What kernel is present on the disk with fvdw-sl 15-1 ?

Do you also still remember which disk was in which slot when you made output dmesg and dmesg2
(sorry for all the questions)

[matzi]

It is getting more astonishing. I did tries with one disc only and both disc. Result as follows, pay attention to the fvdw version!
Note: I always closed and opened the browser tab.


single boot in slot1
kernel 3.16.6 on wdc20 fvdw 15-3
kernel 3.13.6 on wdc25 fvdw 15-3


double disc
kernel 3.13.6 on wdc25 fvdw 15-1 wdc25 in slot1
kernel 3.13.6 on wdc25 fvdw 15-3 wdc20 in slot1
dmesg2 was taken with wdc25 in slot1

[fvdw]

so you have the 3.13.6 kernel on both disks

The output of dmesg2 gives the the wdc25 was on device 0:3:00 and you say it was in slot 1 that is as it should and means the cables are connected correctly

single disk boot (I assume the disks are in slot 1)
as well wdc25 and 20 give fvdw-sl-15-3

double disk
wdc25 in slot 1 gives fvdw-15-1
wdc20 in slot 1 gives fvdw-15-3

I think the nas boots from the right disk, in both cases it loads the kernel from the disk in slot 1 but it seems to load the firmware from the wrong partition, the question is why. This can only be the case when the device nodes are wrong

it would be helpfull if you post for both situations the output of

Code: Select all

cat /proc/partitions

[matzi]

with WDC20 in slot1

root@fvdwsl-base:/ # cat /proc/partitions
major minor #blocks name

31 0 500 mtdblock0
31 1 4 mtdblock1
8 0 2441890584 sdb
8 1 516096 sdb1
8 2 515072 sdb2
8 3 516096 sdb3
8 4 1024 sdb4
8 5 802816 sdb5
8 6 8192 sdb6
8 7 515072 sdb7
8 8 2439014400 sdb8
8 16 1953514584 sda
8 17 514080 sda1
8 18 514080 sda2
8 19 514080 sda3
8 20 1 sda4
8 21 835380 sda5
8 22 64260 sda6
8 23 514080 sda7
8 24 1950234772 sda8
8 32 4096000 seh

with wdc25 in slot1

root@fvdwsl-base:/ # cat /proc/partitions
major minor #blocks name

31 0 500 mtdblock0
31 1 4 mtdblock1
8 0 1953514584 sdb
8 1 514080 sdb1
8 2 514080 sdb2
8 3 514080 sdb3
8 4 1 sdb4
8 5 835380 sdb5
8 6 64260 sdb6
8 7 514080 sdb7
8 8 1950234772 sdb8
8 16 2441890584 sda
8 17 516096 sda1
8 18 515072 sda2
8 19 516096 sda3
8 20 1024 sda4
8 21 802816 sda5
8 22 8192 sda6
8 23 515072 sda7
8 24 2439014400 sda8