.
I suggest you use fvdw-sl console and load the kirkwood standalone kernel. I assume you are familiar with the use of the fvdw-sl console.
The approach will be step 1 try to repair file system on sda7 and sda8 and step 2 install a new firmware version on sda1
Step 1 try to repair file system on sda8 and sda7.
Using fvdw-sl console load and start standalone kernel.
After having connected with the telnet client run the command
- Code: Select all
fvdw-sl-programs
From the menu that appears choose option to upload glibc and tools. This will enable you to run e2fsck.
This should be done for sda7 and sda8.
I would advise to do it first for sda7 using command as given by Jocko and report output here before proceeding further
There is a second option you could try that doesn't reauire using the fvdw-sl console. This is forcing the cloudbox to boot from sda2. That also should contain an (older) version of fvdw-sl. If that is undamaged you could try to use it to repair sda8.
To boot from sda2 boot your nas as usual on the command line give these commands
- Code: Select all
cd /lacie-boot
mv sda1boot sda2boot
cd /
Reboot the nas and try the e2fsck command for sda8 as jocko posted earlier.
If this doesn't work the only alternative left is using fvdw-sl console
