plugout.net

by **François Zeayon** » Tue Apr 19, 2016 8:44 pm

OK.

I tried several more times. I even set an extra variable with setenv. The result is the exact command repetition but environment variables are actualy set, with "printenv" confirmation.
That said "disk 0x800000 0:6" does nothing but command repetition too. :dry

by **François Zeayon** » Tue Apr 19, 2016 8:49 pm

I tried to call each "boot_disk" command listed in environment variables with no more succes and "Device 1 not available" from "boot_disk2" and "boot_disk4".

by **François Zeayon** » Tue Apr 19, 2016 8:59 pm

One thing is still surprising: why "gdisk -l /dev/sda" is giving

Code: Select all: ... Disk identifier (GUID): 00000000-0000-0000-0000-000000000000 ...

:?:

by **fvdw** » Tue Apr 19, 2016 9:01 pm

That the disk command doesn't load the kernel means nothing is present in partition 6. I suggest you repeat the installtion using the fvdw-sl console (version 6.0) and using the "install fvdw-sl firmware" action. The installer script will mention if it succeeded succesful or not. If it aborts before completion post the last message of the installer script

by **François Zeayon** » Tue Apr 19, 2016 9:51 pm

Hum... Repeated installation like you suggest.
This ended successfully and asked to run "reboot -f".
Once done, NAS restarted in the same post installation initial state : No NAS found by fvdw-sl-assistant and LED blinking red/blue.

In u-boot console, running "ide reset" still leads to :

François Zeayon wrote:[...]
Code: Select all
>>ide reset ide reset Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found [0 0 0]: Enable DMA mode Device 0 @ 0 0: Model: ST31000520AS Firm: CC32 Ser#: 9VX07HTQ Type: Hard Disk Supports 48-bit addressing Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)

[...]

Please note "Device 0 @ 0 0"...
Any clue ?

Thanks. :)

by **fvdw** » Wed Apr 20, 2016 10:57 am

This is normal output for ide reset command, it specifies the bus numbers were the disk is connected.

When installing the firmware did you select the right firmware package (for nwsp2) ?
You did not replace u-boot by a different version (you have in u-boot window a prompt like this "marvell>>" ?

If so then lets investigate as next step your disk
Use the fvdw-sl console and load the standalone kernel for nwsp2 (Kirkwood) and log in with telnet terminal
At the command prompt give following command

Code: Select all: mkdir sda5 mount /dev/sda5 /sda5 cd /sda5 ls -al

And post the output
There should be a file with name installer.log
If so also post output of this command

Code: Select all: cat installer.log

by **François Zeayon** » Wed Apr 20, 2016 9:15 pm

Hello.

OK.

I chose "UIMAGE-3142-KIRKWOOD-150-standalone" firmware.
u-boot prompts "Marvell>>", yes.

by **François Zeayon** » Wed Apr 20, 2016 9:20 pm

fvdw wrote:
Code: Select all
mkdir sda5 mount /dev/sda5 /sda5 cd /sda5 ls -al

And post the output

Code: Select all: root@fvdw-sta-kirkwood:/sda5 # ls -al total 44 drwxr-xr-x 7 root root 4096 Apr 19 21:39 . drwxrwxrwt 13 root root 360 Apr 20 21:14 .. drwxr-xr-x 2 root root 4096 Apr 19 21:31 etc -rw-r--r-- 1 root root 8114 Apr 19 21:39 installer.log drwx------ 2 root root 16384 Jan 1 2000 lost+found drwxr-xr-x 2 root root 4096 Aug 12 2011 tmp drwxr-xr-x 3 root root 4096 Apr 19 21:31 usr drwxr-xr-x 3 root root 4096 Apr 19 21:31 var

There should be a file with name installer.log
If so also post output of this command
Code: Select all
cat installer.log

Code: Select all: root@fvdw-sta-kirkwood:/sda5 # cat installer.log fvdw-sl-installer log tftpd ip address 192.168.1.67 getting required programs from tftp server 192.168.1.67 Dialog installed xterm installed mke2fs-ext3 present gdisk present Start fvdw-sl firmware installer version 3.0.0 selected nas type nwsp2 platform kirkwood selected disk /dev/sda gpt support bootloader selected yes selected partion table type gpt Deleting old gpt partiton table partitions found before GPTdeleting partition table = 8 7 6 5 4 3 2 1 \n del = d\n8\nd\n7\nd\n6\nd\n5\nd\n4\nd\n3\nd\n2\nd\n1\nw\nY\n\n partitions found after delete GPT partition table = \n deleting GPT partition succeeded, trying to delete protective ms-dos table\n The number of cylinders for this disk is set to 121126. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Command (m for help): Selected partition 1 Command (m for help): The partition table has been altered. Calling ioctl() to re-read partition table deleting ms-dos protective partition succeeded\n create new partiton table create new GPT partiton table GPT fdisk (gdisk) version 0.8.5 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: present Found valid MBR and GPT. Which do you want to use? 1 - MBR 2 - GPT 3 - Create blank GPT Your answer: Using GPT and creating fresh protective MBR. Command (? for help): Expert command (? for help): Enter the sector alignment value (1-65536, default = 2048): Expert command (? for help): Command (? for help): Partition number (1-128, default 1): First sector (34-1953525134, default = 4096) or {+-}size{KMGTP}: Last sector (4096-1953525134, default = 1953525134) or {+-}size{KMGTP}: Current type is 'Linux filesystem' Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux filesystem' Command (? for help): Partition number (2-128, default 2): First sector (34-1953525134, default = 1052672) or {+-}size{KMGTP}: Last sector (1052672-1953525134, default = 1953525134) or {+-}size{KMGTP}: Current type is 'Linux filesystem' Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux filesystem' Command (? for help): Partition number (3-128, default 3): First sector (34-1953525134, default = 2101248) or {+-}size{KMGTP}: Last sector (2101248-1953525134, default = 1953525134) or {+-}size{KMGTP}: Current type is 'Linux filesystem' Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux swap' Command (? for help): Partition number (4-128, default 4): First sector (34-1953525134, default = 3149824) or {+-}size{KMGTP}: Last sector (3149824-1953525134, default = 1953525134) or {+-}size{KMGTP}: Current type is 'Linux filesystem' Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux filesystem' Command (? for help): Partition number (5-128, default 5): First sector (34-1953525134, default = 3166208) or {+-}size{KMGTP}: Last sector (3166208-1953525134, default = 1953525134) or {+-}size{KMGTP}: Current type is 'Linux filesystem' Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux filesystem' Command (? for help): Partition number (6-128, default 6): First sector (34-1953525134, default = 4739072) or {+-}size{KMGTP}: Last sector (4739072-1953525134, default = 1953525134) or {+-}size{KMGTP}: Current type is 'Linux filesystem' Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux filesystem' Command (? for help): Partition number (7-128, default 7): First sector (34-1953525134, default = 4755456) or {+-}size{KMGTP}: Last sector (4755456-1953525134, default = 1953525134) or {+-}size{KMGTP}: Current type is 'Linux filesystem' Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux filesystem' Command (? for help): Partition number (8-128, default 8): First sector (34-1953525134, default = 5804032) or {+-}size{KMGTP}: Last sector (5804032-1953525134, default = 1953525134) or {+-}size{KMGTP}: Current type is 'Linux filesystem' Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux filesystem' Command (? for help): Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!! Do you want to proceed? (Y/N): OK; writing new GUID partition table (GPT) to /dev/sda. The operation has completed successfully. creating GPT partiton table succeeded format partition 5 mke2fs 1.41.14 (22-Dec-2010) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 49152 inodes, 196608 blocks 1966 blocks (1.00%) reserved for the super user First data block=0 Maximum filesystem blocks=201326592 6 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840 Writing inode tables: done Creating journal (4096 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. formatting sda5 succeeded writing kernel to partition 6 mounting sda 5 succeeded getting kernel from tftp server writing kernel to partition 6 9445+1 records in 9445+1 records out 4835944 bytes (4.6MB) copied, 0.362853 seconds, 12.7MB/s writing kernel to partition 6 succeeded Getting firmware image from tftp server firmware disk image uploaded succesfully\n Unpacking firmware image from archive firmware disk image extracted succesfully\n Adapting firmware image for nwsp2\n Transfer of firmware correction from tfp server succeeded, starting pacthing of firmware image mounting firmware image succeeded ./ ./etc/ ./etc/init.d/ ./etc/init.d/insert-modules ./etc/platform ./lib/ ./lib/modules/ ./lib/modules/3.14.2/ ./lib/modules/3.14.2/videobuf-core.ko ./lib/modules/3.14.2/ehci-pci.ko ./lib/modules/3.14.2/usb_f_mass_storage.ko ./lib/modules/3.14.2/readme.txt ./lib/modules/3.14.2/usblp.ko ./lib/modules/3.14.2/g_ether.ko ./lib/modules/3.14.2/ftdi-elan.ko ./lib/modules/3.14.2/iscsi_tcp.ko ./lib/modules/3.14.2/ftdi_sio.ko ./lib/modules/3.14.2/usb-storage.ko ./lib/modules/3.14.2/sg.ko ./lib/modules/3.14.2/pl2303.ko ./lib/modules/3.14.2/iscsi_trgt.ko ./lib/modules/3.14.2/cdrom.ko ./lib/modules/3.14.2/libiscsi.ko ./lib/modules/3.14.2/libcomposite.ko ./lib/modules/3.14.2/ehci-orion.ko ./lib/modules/3.14.2/configfs.ko ./lib/modules/3.14.2/scsi_transport_iscsi.ko ./lib/modules/3.14.2/g_mass_storage.ko ./lib/modules/3.14.2/ehci-hcd.ko ./lib/modules/3.14.2/usbserial.ko ./lib/modules/3.14.2/zr364xx.ko ./lib/modules/3.14.2/bonding.ko ./lib/modules/3.14.2/videobuf-vmalloc.ko ./lib/modules/3.14.2/libiscsi_tcp.ko ./lib/modules/3.14.2/btrfs.ko ./lib/modules/3.14.2/r8712u.ko ./lib/modules/3.14.2/pktgen.ko ./lib/modules/3.14.2/udc-core.ko ./lib/modules/3.14.2/mv_udc.ko ./lib/modules/3.14.2/modules.dep.bb ./lib/modules/3.14.2/wire.ko correcting firmware image for nwsp2 succeeded\n Writing firmware to partion 7 512000+0 records in 512000+0 records out 262144000 bytes (250.0MB) copied, 29.336066 seconds, 8.5MB/s writing firmware file to partition 7 succeeded writing firmware to partition 1 512000+0 records in 512000+0 records out 262144000 bytes (250.0MB) copied, 29.367511 seconds, 8.5MB/s writing firmware file to partition 1 succeeded writing firmware to partition 2 512000+0 records in 512000+0 records out 262144000 bytes (250.0MB) copied, 29.396204 seconds, 8.5MB/s writing firmware file to partition 2 succeeded write default database to partition 5 uploading default database on partition 5 succeeded extraction and installing of the default database on partition 5 succeeded format partition 8 shared folder partition formating partition 8 succeeded create shared folder public on partition 8 Installation completed root@fvdw-sta-kirkwood:/sda5 #

by **fvdw** » Wed Apr 20, 2016 9:28 pm

well the firmware is installed correctly but probably you have a nwsp2 classic wit a bootloader that doesn't support GPT partition table
As you use a 1 TB disk use ms-ds partition scheme when installing the firmware and everything will be fine

by **François Zeayon** » Wed Apr 20, 2016 9:31 pm

Fine, I'll have a try.

Thank you. :)

plugout.net

[u-boot] bootm command leads to "bad magic number"

Re: [u-boot] bootm command leads to "bad magic number"

Re: [u-boot] bootm command leads to "bad magic number"

Re: [u-boot] bootm command leads to "bad magic number"

Re: [u-boot] bootm command leads to "bad magic number"

Re: [u-boot] bootm command leads to "bad magic number"

Re: [u-boot] bootm command leads to "bad magic number"

Re: [u-boot] bootm command leads to "bad magic number"

Re: [u-boot] bootm command leads to "bad magic number"

Re: [u-boot] bootm command leads to "bad magic number"

Re: [u-boot] bootm command leads to "bad magic number"

Who is online