Save original firmware for later restoration

[matzi]

So let us summarise and wait for fvdw to help:

I have to discs setup:
One WDC20 with fvdw 15-1
One WDC25 with fvdw 15-3

when only one disc is plugged in slot 1 it is all OK
when two discs are plugged (slot1 and 2), the webinterface shows fvdw version installed in slot2 -> ergo it is booting from slot2

the file structure in folder /etc is from slot2

In the webinterface under disc setup, setup, manage disks and volumes: Disk-A is the size of the disk in slot 1, Disk-B is the size of the disk in slot 2

Can this be a cable issue?

Remark: If so, I can dismount the housing and change it, rather than having a patch that I have to trace on every update.

[Jocko]

the file structure in folder /etc is from slot2
Can this be a cable issue?

Remark: If so, I can dismount the housing and change it, rather than having a patch that I have to trace on every update.

Yes because, the file system is a chroot system which mount the partition sda2 or sda1 and so if sda is not the right device then you don't have the rigth system version.

and it is why in a first time you thought that it is required to load the firmware on the data disks

[matzi]

That sounds reasonable.

I also found that I cannot access usb devices when both discs are installed. Is that also a related problem?

[Jocko]

yes because the usb driver modules don't have the right version (kernel version 3.13.6) but the modules version is 3.9.5 with firmware version 15.1

Temporarily to restore USB, you can add the modules for version 3.13.6 by creating a folder '3.13.6' in /lib/modules and save here the files present of the 15-3 firmware image from its own folder /lib/modules/3.13.6

[fvdw]

the problem must be in the boot loader, that loads the initial file system with the rcS boot script.
Seems on your system it finds a kernel on disk2 and then loads the file system present on this disk in partition7.
This should not happen as the bootloader should start with searching for a kernel on the disk in slot and boot it when it finds one.

Please delete the kernel that you have on the disk in slot 2.
This must be done by using this command

Code: Select all

dd if=/dev/zero of=/dev/sdb6

(be sure not to make a type error as this command will erase the partition or whole disk that you specified after of= !)
Now try again after you have done this

We also nee to check your boot loader, to do this switch off the 5big2 en open an u-boot command window with the fvdw-sl console.
switch on the 5big2 and when the u-boot window interrupts boot give the command (in the u-boot window)

Code: Select all

printenv

and post the output here
Also post the output of

Code: Select all

ide reset

and

Code: Select all

ide part

[matzi]

printenv gives:

provided by fvdw
waiting for u-boot..
starting u-boot net console click on window and press enter


Marvell>> printenv
printenv
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
stderr=serial
console=console=ttyS0,115200 mtdparts=spi_flash:0x80000@0(uboot)ro,0x300000@0x10
0000(root)
mainlineLinux=no
CASset=min
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
MALLOC_len=1
ethprime=egiga0
netbsd_en=no
vxworks_en=no
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/m
tdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x20
00000;
disaMvPnp=no
ethmtu=1500
eth1mtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
enaAutoRecovery=yes
uboot_capabilities=gpt,lba64
start_lump=lump 3
pre_lump=lump 1
resetdisk=ide reset
bootdelay=0
boot_fail=lump
kernel_addr=0x800000
productType_env=BIG5_KW
primaryPart=6
secondaryPart=A
boot_usb=usb start;usbboot 0x800000 0:1;bootm;
resetFlag_env=0
bootargs=console=ttyS0,115200 root=/dev/sda7 ro reset=0 productType=PRO_KW
bootcmd=run disk_disk
boot_disk10=disk ${kernel_addr} 5:${primaryPart}; setenv rootfs /dev/sde7;
boot_disk9=if disk ${kernel_addr} 6:${primaryPart}; then setenv rootfs /dev/sdd7
; else run boot_disk10; fi
boot_disk8=if disk ${kernel_addr} 1:${primaryPart}; then setenv rootfs /dev/sdc7
; else run boot_disk9; fi
boot_disk7=if disk ${kernel_addr} 2:${primaryPart}; then setenv rootfs /dev/sdb7
; else run boot_disk8; fi
boot_disk6=if disk ${kernel_addr} 3:${primaryPart}; then setenv rootfs /dev/sda7
; else run boot_disk7; fi
boot_disk5=if disk ${kernel_addr} 5:${secondaryPart}; then setenv rootfs /dev/sd
e7; else run boot_disk6; fi
boot_disk4=if disk ${kernel_addr} 6:${secondaryPart}; then setenv rootfs /dev/sd
d7; else run boot_disk5; fi
boot_disk3=if disk ${kernel_addr} 1:${secondaryPart}; then setenv rootfs /dev/sd
c7; else run boot_disk4; fi
boot_disk2=if disk ${kernel_addr} 2:${secondaryPart}; then setenv rootfs /dev/sd
b7; else run boot_disk3; fi
boot_disk1=if disk ${kernel_addr} 3:${secondaryPart}; then setenv rootfs /dev/sd
a7; else run boot_disk2; fi
boot_disk=if test ${resetFlag_env} -eq 0; then run boot_disk1; else run boot_dis
k6; fi
disk_disk=run boot_disk; setenv bootargs console=ttyS0,115200 root=${rootfs} ro
reset=${resetFlag_env} productType=${productType_env}; bootm ${kernel_addr};
ethaddr=00:D0:4B:91:93:42
eth1addr=00:D0:4B:91:93:43
ethact=egiga0
ipaddr=192.168.1.252
ncip=192.168.1.2
serverip=192.168.1.2
stdin=nc
stdout=nc

Environment size: 2716/4092 bytes

ide reset:

Environment size: 2716/4092 bytes
Marvell>> ide reset
ide reset

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
Port Multiplier found @ 0 0. Vendor: 11ab ports: 4
[0 0 2]: Enable DMA mode
Device 2 @ 0 0 2:
Model: WDC WD20EARS-00MVWB0 Firm: 50.0AB50 Ser#: WD-WMA
Z20054920
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1907729.0 MB = 1863.0 GB (-0 x 0)
[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

ide part

Marvell>> ide part
ide part

## Testing for valid DOS partition ##

Partition Map for IDE device 2 -- Partition Type: DOS

Partition Start Sector Num Sectors Type
1 128520 1028160 83
2 1156680 1028160 83
3 2184840 1028160 82
4 3213000 -391156231 5 Extd
5 3341520 1670760 83
6 5140800 128520 83
7 5397840 1028160 83
8 6554520 -394497751 83

## Testing for valid EFI partition ##

Partition Map for IDE device 3 -- Partition Type: EFI

Part Start LBA End LBA
gpt1 0x0 0x800
gpt2 0x0 0xFC800
gpt3 0x0 0x1F8000
gpt4 0x0 0x2F4000
gpt5 0x0 0x2F4800
gpt6 0x0 0x47C800
gpt7 0x0 0x480800
gpt8 0x0 0x57C000

Before I erase sdb6 I would like to wait for the problem is identified, because I expect to be back where I came from: Not booting with 2 discs. By the way is it possible to erase sdb6 while it is running from sdb6?

[fvdw]

well your boot loader has the normal content
the boot command used by the loader is
run disk_disk
as you can see by reading the commands
it first looks for a kernel of device 3 in secondary partition (=A),
if it doesn't find a kernel it proceeds to device 2 and partition A
we don't use a partition A (=10) so it will proceed until boot_disk6
Here it looks for a kernel on device 3 and partition primary (=6)and if it finds one it is loaded and booted,
if not it proceed to look in device 2 partition 6.

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)

You can see this in the ide reset and ide part output.

this bootloader has gpt support (uboot_capabilities=gpt,lba64) so it should be able to read the disks

conclusion I do not know why it loads the firmware on disk sdb..

Did you modify the boot scripts ? :tapfoot

[fvdw]

there is also possibility that we get erratic resutks when for hatever reasons the device nodes are not update correctly
This should automatically happen but who knows something might go wrong there.
However in all case the kernel should have been loaded from slot 1, so i think this will not be the cause

use this command for both cases and post output

Code: Select all

root@fvdwsl-base:/ # ls -al /dev/sd*

it should give this on a 5big2

Code: Select all

brw-rw----  1 root root 8, 32 2014-02-15 00:18 /dev/sda
brw-rw----  1 root root 8, 33 2014-02-15 00:18 /dev/sda1
brw-rw----  1 root root 8, 34 2014-02-15 00:18 /dev/sda2
brw-rw----  1 root root 8, 35 2014-06-08 14:02 /dev/sda3
brw-rw----  1 root root 8, 36 2014-02-15 00:18 /dev/sda4
brw-rw----  1 root root 8, 37 2014-02-15 00:18 /dev/sda5
brw-rw----  1 root root 8, 38 2014-04-06 22:31 /dev/sda6
brw-rw----  1 root root 8, 39 2014-02-15 00:18 /dev/sda7
brw-rw----  1 root root 8, 40 2013-09-29 22:27 /dev/sda8
brw-rw-rw-  1 root root 8,  9 2013-08-09 21:22 /dev/sda9
brw-rw----  1 root root 8, 16 2008-01-03 21:06 /dev/sdb
brw-rw----  1 root root 8, 17 2008-01-03 21:06 /dev/sdb1
brw-rw----  1 root root 8, 18 2008-01-03 21:06 /dev/sdb2
brw-rw----  1 root root 8, 19 2008-01-03 21:06 /dev/sdb3
brw-rw----  1 root root 8, 20 2008-01-03 21:06 /dev/sdb4
brw-rw----  1 root root 8, 21 2008-01-03 21:06 /dev/sdb5
brw-rw----  1 root root 8, 22 2008-01-03 21:06 /dev/sdb6
brw-rw----  1 root root 8, 23 2008-01-03 21:06 /dev/sdb7
brw-rw----  1 root root 8, 24 2014-01-25 23:33 /dev/sdb8
brw-

[matzi]

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

[matzi]

I modified rcS in one of the discs for wpa_supplicant call

wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf -B >> /etc/iface_scripts/udev.log

I do not think this can cause confusion.