Save original firmware for later restoration

[Jocko]

I could compare with my 5big2 and your output is good.

sda on the bus 0:3:0:0: and sdb on 0:2:0:0: :scratch

How do you see that the kernel is loaded from sdb6 ?

And sda is the 1er left slot when you see the back side

[matzi]

And this is dmesg with the swapped discs (desired configuration)

Kernel is Linux 3.13.6 #19 PREEMPT Sun Apr 6 21:15:00 GMT+1 2014

[matzi]

I say the firmware is shown in the webinterface as V15-1 which is installed in slot2.

[matzi]

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

[Jocko]

So if I understood well you swapped the two disk and now the AF disk is on the 1st left slot.

I don't see no error in the two dmesg output : the device mapper update rightly sda and sdb in accordance with your swapping.

So to be sure your issue is this :
when the AF is in the 1st left slot and only in this case, it seems that the kernel is loaded from the sdb6 ?

If it is the case, then there is an issue with the sda6 partition or the kernel is corrupted on it.

Please to post the partition table of the AF disk and try to rewrite the kernel on it (UIMAGE-3136-NWSP2CL-19)

[matzi]

P Table is

Number Start (sector) End (sector) Size Code Name
1 2048 1034239 504.0 MiB 8300
2 1034240 2064383 503.0 MiB 8300
3 2064384 3096575 504.0 MiB 8200
4 3096576 3098623 1024.0 KiB 8300
5 3098624 4704255 784.0 MiB 8300
6 4704256 4720639 8.0 MiB 8300
7 4720640 5750783 503.0 MiB 8300
8 5750784 4883779583 2.3 TiB 8300

But the problem is not exactly what you said. It always shows the firmware from the disc in slot2. Whatever sequence the discs are installed. Both discs run fine if installed alone.

[matzi]

Could it be the kernel? You are saying "UIMAGE-3136-NWSP2CL-19" is the right one. I have setup the discs with fvdw console which comes with "UIMAGE-395-NWSP2CL-199". Can that be the fault?

[Jocko]

So only vs 15-3 is installed on the 2TB disk (AF is the 2,5TB disk) ?

And how do you make the partition table on the AF disk because your values are not the same than those set for a gpt disk by the install script:

Code: Select all

x
l
4096
m
n
1

+512M
8300
n
2

+512M
8300
n
3

+512M
8200
n
4

+8M
8300
n
5

+768M
8300
n
6

+8M
8300
n
7

+512M
8300
n
8


8300
w

and you must get this partition table

Code: Select all

Number  Start (sector)    End (sector)  Size       Code  Name
   1            4096         1052671   512.0 MiB   8300  Linux filesystem
   2         1052672         2101247   512.0 MiB   8300  Linux filesystem
   3         2101248         3149823   512.0 MiB   8200  Linux swap
   4         3149824         3166207   8.0 MiB     8300  Linux filesystem
   5         3166208         4739071   768.0 MiB   8300  Linux filesystem
   6         4739072         4755455   8.0 MiB     8300  Linux filesystem
   7         4755456         5804031   512.0 MiB   8300  Linux filesystem
   8         5804032      5860533134   2.7 TiB     8300  Linux filesystem


[matzi]

yes the wd25 has gpt - i guess AF is linked to that.

I was wrong the wd25 was not setup with fvdw console. It was setup long time ago manually. I think I was a first timer using gpt on an nwsp2 http://www.plugout.net/viewtopic.php?f=4&t=581

the current discs have vs15-1 on the 2TB, vs 15-3 on the 2,5TB.

I just double checked it:
Booting with both discs shows 15-1 in the webinterface. When I unplug and reboot slot2 it shows 15-3.

[Jocko]

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...