drive doesn't boot

[conjuring]

do i need to adapt the conf file as it seems to be written for a hitatchi 500gb drive and mine got a 1tb samsung hdd?
or does this have no effect?(don't know anything about linux and boot sequences).

[conjuring]

Does there have to happen something to the third partition?
You create it but don't format it in the partition nor do you write an image to it

[fvdw]

No nothing needs to be present in partition 3, it is partion used as swap, it will be set up by the firmware and the kernel at boot

yes this seems to be the main board of an internet space 1 the cpu number I cannot read on your picture
it should 88F5182-A2. But I think it will match looking to the rest of the board

Then the only possibility left can be corrupt files. or a main board with hardware problem.
Did the board worked before you tried to install the firmware.

[conjuring]

yes thats the cpu number indeed,
yes the board worked pre install.
when you look at the disk trough gparted, is it normal it displays an exclamaition mark next to sdb6 and sdb3

[fvdw]

I nver used gparted but I think it is correct, sdb3 is not formatted only a partition.
sda6 contains a raw uImage file so also not a formatted partition.

The boot loader of lacie on this device only recognizes disks with a ms-dos partition table, that's why you should use fdisk to set it up.

Did you check the md5 checksums of the files ?

if they are ok we can use the fvdw-sl console running under ms-windows to do some checks using the u-boot console

[conjuring]

md5 sum is correct

[fvdw]

:scratch

ok then connect the disk to your pc running linux and check if sda5 contains the right files
assuming the disk is sdb

Code: Select all

mkdir /sdb5
sudo mount /dev/sdb5 /sdb5
ls -al /sdb5


If thats ok we are going to try to load the kernel using the fvdw-sl console running under ms windows

[fvdw]

you can download the fvdw-sl console here
viewtopic.php?f=7&t=1271

Install it on your windows pc and put the disk in the isp1 and connect it to your LAN
Do not switch it on
start the fvdw-sl console on your windows PC (password is 33305) and choose action "U-boot console"
A command window will pop up saying it waits for u-boot.
Now start you isp1 and see if the fvdw-sl console detcts it and interupt pboot.
It should come back with a prompt like this

Code: Select all

marvell>>

[conjuring]

i just erased the partition table so i'll have to redo everything again, then i'll check

Thanks for all your help btw.

[fvdw]

when you don't get this something is wrong with the Network connection of your isp1.

If you get this we can proceed.
First check if the disk is recognized
on the marvell prompt give command

Code: Select all

ide reset

it should return with some info that it found a disk and a valid partition table

to test if it can read the partition table give this command

Code: Select all

ide part

it should list the table you have made.

If thats ok we are going to boot the kernel from sda6
first check if boot arguments are set ok
give this command

Code: Select all

printenv bootargs

it should give output and check if this ouput contains this

Code: Select all

bootargs=console=ttyS0,115200 root=/dev/sda7 ro reset=0

if not, set this variable using this command

Code: Select all

setenv bootargs console=ttyS0,1152000 root=/dev/sda7 ro reset=0

Check with the previous printenv if the bootargs variable now contains the text as mentioned befor

Now load the kernel in RAM with this command

Code: Select all

disk 0x800000 0:6

(it can be that you need to use diskboot instead of disk in this command)
it should give as output something like this
Loading from IDE device ) partion 6 .....
and then something on image name when it was created, size...

if that is the case you can boot it by entering

Code: Select all

bootm

It should mention that it is booting the image at 00800000...
image name, creation date, size...
It should finish with
ok

starting kernel...

Now see if the isp1 comes alive and that you can connect to it with the web interface.