Install fvdw-sl in new hard disk

[treybal]

More:

root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
mount: mounting /dev/sda7 on /sda7 failed: Device or resource busy

[treybal]

More:

root@fvdw-sta-kirkwood:/ # cat /sda7/boot.log
cat: can't open '/sda7/boot.log': No such file or directory

[treybal]

More:

root@fvdw-sta-kirkwood:/ # mount /dev/sda5 /sda5
mount: mounting /dev/sda5 on /sda5 failed: Device or resource busy

[treybal]

And finally the last command:

usr/bin/smbstatus
....

---edit---
I removed the posted output (get later the log file on another post)

[Jocko]

Thank you for the outputs.

So no issue on the disk side (no error in dmesg output) but it seems the bootloader fails to use it (no boot.log in sda7). That would means either it fails to detect it or there is an issue with the kernel image on sda6. I can not check this point because your installer.log output is not complete.

Anyhow we can valid this last point by loading an external kernel.

Then stop fully the nas and on fvdw-sl console select the action "External kernel, load and start" the file "UIMAGE-414133-KIRKWOOD-1" its location is firmware\kirkwood in the folder tftp

So wait around two minutes and see if fvdw-sl assistant found it

[treybal]

Thank you for the outputs.

So no issue on the disk side (no error in dmesg output) but it seems the bootloader fails to use it (no boot.log in sda7). That would means either it fails to detect it or there is an issue with the kernel image on sda6. I can not check this point because your installer.log output is not complete.

Anyhow we can valid this last point by loading an external kernel.

Then stop fully the nas and on fvdw-sl console select the action "External kernel, load and start" the file "UIMAGE-414133-KIRKWOOD-1" its location is firmware\kirkwood in the folder tftp

So wait around two minutes and see if fvdw-sl assistant found it

Hello dear Jocko,

I have done what you have told me, but I don't see anything happening after waiting more than two minutes.
The fvdw-sl assistant doesn’t found any NAS…. :scratch

On the other hand, how can I put the full output of the installer.log?
Because the ms-dos windows won't let me ...

[Jocko]

You can run a new "auto scan" to confirm fvdw-sl assistant does not detect your cloudbox

[Jocko]

About installer.log, there is a way to get the file on laptop side but need to use the standalone mode. So check first if fvdw-sl assistant still does not find the nas

[treybal]

You can run a new "auto scan" to confirm fvdw-sl assistant does not detect your cloudbox

I already made an auto scan, and the NAS isn’t found.

[Jocko]

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