plugout.net

Hi, as I found that my sda8 partition is corrupted (e2fsck -n gives errors) I wanted to repair it.
So I downloaded the console and tried to detect the u-boot from my NAS.
I tried by restarting the NAS from the web console with an already ready uboot detection window open, and also from scratch, shutting down the nas before running the procedure on the console.

Since my network plug is distant from my station, I tried first using the (very stable) wifi and also a powerline adapter

In no case the NAS uboot was identified and the standalone kernel loaded. The black uboot detection screen remains black all the time.

I doubt it depends on the non cabled network, as the connection works perfectly...

Do you think this could be the only reason?

EDIT: I'm also trying with a cabled connection through a switch, but no success.

Thanks,
MDI

Hi mdi

If you used a version 18.x, you can do it directly from the firmware web-interface, from the main disks setup menu, click on the volume name to load the volume menu and here you will find a new button to run a fs repairing/checking action.

Hi Jocko, thanks for supporting so quickly!
I tried, and I got a message saying to reboot with the power botton, which I did.
Tried again, I got again the same message, but it looks that e2fsck is already running (I can see it with 'top' logging via ssh), even if the web console has all the 3 buttons disabled (Cancel task, re-start task, NAS restart).

I will let the e2fsck task finish its job.

Everything was ok and I was even able to convert the filesystem to ext4.

I also have some corruption on sda5, is there a way to fix that too?

Thanks!

Hi

With the last roll-up patch for version 18-2, the firmware tries to run quietly a checking/repairing task if it fails to mount sda5. On such a case, you have then additional information in boot.log file.

But you can force it by setting a file in etc

Code: Select all

touch /etc/sda5-scan

. Reboot the nas so that the firmware performs an e2fsck command on sda5 and open later the file /boot.log to read what it did

Superb! That fixed it as well, thanks a lot!