Install fvdw-sl in new hard disk

[treybal]

ok

So you have to stop the nas and get again a telnet access.

About installer.log

Code: Select all

mkdir /sda5
mount /dev/sda5 /sda5
busybox tftp -r installer.log -l /sda5/installer.log -p ip-pc

where ip-pc is the ip address of your laptop. Then you should see a file installer.log in tftp folder on your laptop and post it

other point, please to post

Code: Select all

mkdir /sda7
mount /dev/sda7 /sda7
ls /sda7

Dear Jocko, I cannot insert the content of the "Install.log" file because it is too long.

I have tried to send it by private message but the extension is not allowed so I do not know what I have to do to send it.


In relation to the second thing you ask me, that is the output:

Code: Select all

root@fvdw-sta-kirkwood:/ # mkdir /sda7
root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
root@fvdw-sta-kirkwood:/ # ls /sda7
bin         boot        dev         etc         linuxrc     mail        opt         root        share       usr
bin_cab     clunc       direct-usb  lib         lost+found  nowhere     proc        sbin        sys         var

very Thank you for you help :applause

[Jocko]

Indeed log extension is not allowed because it is a text file which may be strongly compressed.
So you just have to compress it and you should be able to post it either here or in a pm.

About your last output, it seems even by loading an external kernel, the firmware is not loaded (still no boot.log) Then that means the bootloader does not detect the disk.

With such issue, fvdw has much more acknowledge. So wait him for additional test on bootloader side.

[treybal]

Indeed log extension is not allowed because it is a text file which may be strongly compressed.
So you just have to compress it and you should be able to post it either here or in a pm.

About your last output, it seems even by loading an external kernel, the firmware is not loaded (still no boot.log) Then that means the bootloader does not detect the disk.

With such issue, fvdw has much more acknowledge. So wait him for additional test on bootloader side.

Attached to this thread the file "Installer.log" in case fvwd or any other friend of the forum, would like to see it

[Jocko]

Ok, there is no kernel on sda6

Code: Select all

writing kernel to partition 6
mounting sda 5 succeeded
getting kernel from tftp server
writing kernel to partition 6
0+0 records in
0+0 records out
0 bytes (0B) copied, 0.000236 seconds, 0B/s
writing kernel to partition 6 succeeded

So the script wrote nothing

You can try to do it manually

Code: Select all

mkdir /sda5
mount /dev/sda5 /sda5
busybox tftp -r firmware/kirkwood/UIMAGE-414133-KIRKWOOD-1 -l /sda5/kernel.img -g ip-pc
busybox md5sum UIMAGE-414133-KIRKWOOD-1
dd if=/sda5/kernel.img of=/dev/sda6
busybox rm /sda5/kernel.img

and try to reboot the nas

if /dev/sda5 is still mounted, no need to run the mount command (and also mkdir)
ip-pc is still the ip address of your laptop
if md5sum does not return the value: 2f791aece45389418973c103a88e64fb
that means either the uploaded kernel image is corrupted or the one on your laptop

[fvdw]

Thats odd, no kernel although no error while uploading. It could mean the firmware files in his laptop are corrupt. Also the fact that loading external kernel did not load firmware means that more firmware files are corrupt or missing. If it was only the kernel missing on sda6 then the action with loading external kernel should have been successful. Of course if kernel file is corrupt on the laptop then loading it as external kernel will fail.
Think we should check firmware files in the laptop

[treybal]

Ok, there is no kernel on sda6

Code: Select all

writing kernel to partition 6
mounting sda 5 succeeded
getting kernel from tftp server
writing kernel to partition 6
0+0 records in
0+0 records out
0 bytes (0B) copied, 0.000236 seconds, 0B/s
writing kernel to partition 6 succeeded

So the script wrote nothing

You can try to do it manually

Code: Select all

mkdir /sda5
mount /dev/sda5 /sda5
busybox tftp -r firmware/kirkwood/UIMAGE-414133-KIRKWOOD-1 -l /sda5/kernel.img -g ip-pc
busybox md5sum UIMAGE-414133-KIRKWOOD-1
dd if=/sda5/kernel.img of=/dev/sda6
busybox rm /sda5/kernel.img

and try to reboot the nas

if /dev/sda5 is still mounted, no need to run the mount command (and also mkdir)
ip-pc is still the ip address of your laptop
if md5sum does not return the value: 2f791aece45389418973c103a88e64fb
that means either the uploaded kernel image is corrupted or the one on your laptop

Hi Jock,

These are the outputs to the commands that you indicate to me:

root@fvdw-sta-kirkwood:/ # mkdir /sda5
root@fvdw-sta-kirkwood:/ # mount /dev/sda5 /sda5
root@fvdw-sta-kirkwood:/ # busybox tftp -r firmware/kirkwood/UIMAGE-414133-KIRKWOOD-1 -l /sda5/kernel.img -g 192.
168.1.18
firmware/kirkwood/UI 100% |****************************************************************| 4664k 0:00:00 ETA
root@fvdw-sta-kirkwood:/ # busybox md5sum UIMAGE-414133-KIRKWOOD-1
md5sum: can't open 'UIMAGE-414133-KIRKWOOD-1': No such file or directory
root@fvdw-sta-kirkwood:/ # dd if=/sda5/kernel.img of=/dev/sda6
9328+1 records in
9328+1 records out
4776328 bytes (4.6MB) copied, 0.340523 seconds, 13.4MB/s
root@fvdw-sta-kirkwood:/ # busybox rm /sda5/kernel.img

the command md5sum does not return the value: 2f791aece45389418973c103a88e64fb.... :scratch

Given this, I have downloaded the five files "rar" from the console again and I have performed the operation again to rule out that the files on my computer were corrupt, and the result has been the same.

I am attaching a new "Installer.log" file in case you need it to do some analysis.

[treybal]

Thats odd, no kernel although no error while uploading. It could mean the firmware files in his laptop are corrupt. Also the fact that loading external kernel did not load firmware means that more firmware files are corrupt or missing. If it was only the kernel missing on sda6 then the action with loading external kernel should have been successful. Of course if kernel file is corrupt on the laptop then loading it as external kernel will fail.
Think we should check firmware files in the laptop

Hi fvwd,

In my previous post I have already indicated to my friend Jock that I do not believe that the files are corrupt, since I have deleted them from my computer and I have downloaded them from the forum (the five rar files).
Therefore I do not know what may be happening.

[fvdw]

The installer log still mentions 0 bytes written when writing kernel to sda6
Do not reinstall the firmware again but load standalone kernel and repeat only these commands

Code: Select all

mkdir /sda5
mount /dev/sda5 /sda5
busybox tftp -r firmware/kirkwood/UIMAGE-414133-KIRKWOOD-1 -l /sda5/kernel.img -g ip-pc
busybox md5sum /sda5/kernel.img
dd if=/sda5/kernel.img of=/dev/sda6


Replace ip-pc by ip of your laptop
Your previous md5sum command failed because you used wrong name for file to check (error in instruction from jocko)
When again 9328 records are written by dd command reboot the nas and see if firmware is loaded

Ps are you using wired connection between laptop and your LAN?

[treybal]

The installer log still mentions 0 bytes written when writing kernel to sda6
Do not reinstall the firmware again but load standalone kernel and repeat only these commands

Code: Select all

mkdir /sda5
mount /dev/sda5 /sda5
busybox tftp -r firmware/kirkwood/UIMAGE-414133-KIRKWOOD-1 -l /sda5/kernel.img -g ip-pc
busybox md5sum /sda5/kernel.img
dd if=/sda5/kernel.img of=/dev/sda6


Replace ip-pc by ip of your laptop
Your previous md5sum command failed because you used wrong name for file to check (error in instruction from jocko)
When again 9328 records are written by dd command reboot the nas and see if firmware is loaded

Ps are you using wired connection between laptop and your LAN?

Hi friend,

Now it has worked. Thank you very much for the help to both you and Jocko.
The strange thing about all this is because it did not work from the console and this process had to be carried out ...
But the important thing is that in the end everything went well. :applause

[fvdw]

Glad to hear that the cloudbox is up and running now.
It remains strange that the installer script did not upload the kernel. It uses the same commands that you have used manually. :scratch

Just to try to find the reason why the script failed, can you have a look into the fvdw-sl console files on your laptop in folder tftp/firmware/kirkwood and post what is inside the file with name KERNELVERSION