mainboard fix

[fvdw]

ok that is good news.
This is the output of my isp1 when booting

Code: Select all

U-Boot 1.1.1 (Jun 15 2007 - 08:56:23) Marvell version: 1.7.3



| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__| ** LOADER **
** MARVELL BOARD: DB-88F5182-EDmini-V2 LE


U-Boot 1.1.1 (Sep 3 2008 - 07:36:51) Marvell version: 1.7.3 - LaCie version: 1


DRAM CS[0] base 0x00000000 size 64MB
DRAM Total size 64MB
Flash: flashStructGet manu 0xff id 0xff
[0kB@fff80000] ## Unknown FLASH at fff80000: Size = 0x00000000 = 0 MB
Flash: 0 kB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done
*** Warning - bad CRC, using default environment


Soc: MV88F5182 Rev 2
CPU: ARM926 (Rev 0) running @ 400Mhz
SysClock = 200Mhz , TClock = 166Mhz


USB 0: host mode
USB 1: device mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Net: egiga0 [PRIME]
Hit any key to stop autoboot: 0
Waiting for LUMP (2)
Using egiga0 device
no lump receive; continuing

Reset IDE:
Marvell Serial ATA Adapter
Intergrated Sata device found
StartChannel
Device 1: OK
Model: Hitachi HDP725050GLA360 Firm: GM4OA5CA Ser#: GEC5J
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)

** Bad partition - 1:9 1:9 **

Loading from IDE device 1, partition 6: Name: hdb6
Type: U-Boot
Image Name: Linux-2.6.12.6-arm1-lacie5b
Created: 2007-04-20 15:44:19 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1662140 Bytes = 1.6 MB
Load Address: 00008000
Entry Point: 00008000
## Booting image at 00400000 ...
Image Name: Linux-2.6.12.6-arm1-lacie5b
Created: 2007-04-20 15:44:19 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1662140 Bytes = 1.6 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK


As you can see until hit any key to stop autoboot the same.

What you should do when having the marvel prompt and a disc (this may be an empty disk) give this command

Code: Select all

ide reset

this should give output similar to this,

Code: Select all

Reset IDE:
Marvell Serial ATA Adapter
Intergrated Sata device found
StartChannel
Device 1: OK
Model: Hitachi HDP725050GLA360 Firm: GM4OA5CA Ser#: GEC5J
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)

if the disk is not found then it means there is a problem with the sata interface and thethen there is no way to install or run firmware.
If the the disk is found and correct size is determined it should be possible to try to install fvdw-sl firmware either using fvdw-sl console install feature or using manually commands in uboot (marvell>> prompt) and tftp server of the fvdw-sl console

[matt_max]

I can confirm that after I connected some spare disk (WD 500 Gb) this is my output:

Code: Select all

Reset IDE:
Marvell Serial ATA Adapter
Intergrated Sata device found
StartChannel
  Device 1: OK
Model: WDC WD5000LPVX-22V0TT0                   Firm: 01.01A01 Ser#:      WD-WX31A258V55J
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)


So far so good :woohoo

[matt_max]

Ok. I connect my target drive. This is the output from serial console:

Code: Select all

Reset IDE:
Marvell Serial ATA Adapter
Intergrated Sata device found
StartChannel
  Device 1: OK
Model: TOSHIBA HDWD120                          Firm: MX4OACF0 Ser#:            78DJVT0CS
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512)


Next I will try to install fvdw using fvdw-sl-console. I'm not sure which file to choose: UIMAGE-3136-ISP1-14-standalone or UIMAGE-3142-KIRKWOOD-158-standalone?

[fvdw]

UIMAGE-3136-ISP1-14-standalone

[matt_max]

Well... no luck. In FVDW-SL console the ip address of NAS is set to 192.168.1.252 and my laptop have ip address 192.168.1.109. Both devices are in the same network - connected to my router by wires.
When I choose right file (UIMAGE-3136-ISP1-14-standalone) and turn on NAS console cannot "find" it.
I can wait indefinitely with "waiting for u-boot.." message.

Errata. After a few attempts scripts start and then at the end console show this massage:

Code: Select all

mke2fs 1.41.14 (22-Dec-2010)
/dev/sda8: Memory allocation failed while setting up superblock

There was an error formatting /dev/sda8.
Installer will exit.
Disk will boot but partition for shared folders will be not availailable
root@(fvdw-isp1):/ #


Errata2: Huuray :bananadance It's alive and kicking! There is only one small problem: Failed to connect to [http://plugout.net]
Error 200. But I'm a donator.

[fvdw]

Nice to hear that you got it working. :thumbup
About this error , You need to set your plugout credentials in the webinterface (system management>setup tab firmware interface)

[matt_max]

Something is not quite right. When I connected Lacie in my office it is not working again. I mean network leds are blinking but I can't hear disc spinning or any other sounds and I wasn't able to find it on my network.
That was the original fault. I think it is not initialized for some reason.

Tomorrow I will take FT232 usb connector with me and I'm gonna check u-boot status. I've already tried to reconnect nas after 15 minutes but it did not help :scratch

P.S. Yesterday when I was playing with fvdw I set up my credentials in the webinterface and after I click "Save" a message appeared that login was successful. So I was a little bit confused when I wasn't able to update firmware from 18.1 to 18.2.

[Jocko]

Hi

P.S. Yesterday when I was playing with fvdw I set up my credentials in the webinterface and after I click "Save" a message appeared that login was successful. So I was a little bit confused when I wasn't able to update firmware from 18.1 to 18.2.

This is related with the error

Code: Select all

mke2fs 1.41.14 (22-Dec-2010)
/dev/sda8: Memory allocation failed while setting up superblock

There was an error formatting /dev/sda8.
Installer will exit.

That means the data partition is not formatted and then not mounted after rebooting. So you can not create the share fvdw and install the requiring patch (see the topic https://plugout.net/viewtopic.php?f=3&t=3532)


To be able to upgrade the firmware, you have first to fix sda8 formatting error. Open a shell window, and run again this command

Code: Select all

mke2fs-ext3 -t ext4 -m 1 /dev/sda8

[matt_max]

@Jocko You are right but I've already done this. Partition was formatted and after restart I was able to log in. I think something is going on after I fully unplug NAS from powersource. It seems that Lacie cannot initialize itself.
I will be sure after I check it with FT232 serial connection.

[Jocko]

Ok, but did you get the error message (code 200) after installing the following patch : fvdw-sl-18.1-loginPlugout-v3-04jul2021.zip
(viewtopic.php?f=7&t=3078&p=35895#p35895)
Without it, you can never install version 18-2 from version 18-1