plugout.net

the /usr/htdocs directory looks normal

the /rw-fs/tmp not, for instance it misse the folder etc
also subfolder var should contain more then the file you added there

these folders and files in /rw_fs/tmp are created at boot

did you delete any files or folders yourself ?

You can delete the firmware file

Code: Select all

unlink /rw_fs/tmp/firmware.bin

Now lets check if the database is still intact

Code: Select all

ls -al /rw_fs/etc

If this is ok we are going to reboot

output of

Code: Select all

ls -al /rw_fs/etc

Code: Select all

total 37
drwxrwxrwx  4 root    0 1024 2016-07-14 22:32 .
drwxrwxrwx  8 nobody 99 1024 2011-11-16 12:00 ..
drwxr-xr-x  2 root    0 1024 2012-05-17 15:59 dropbear
-rw-r--r--  1 nobody 99    0 2011-11-16 12:13 ledoffatboot
-rw-r--r--  1 root    0  101 2011-11-16 12:00 mdadm.conf
-rw-rw-rw-  1 nobody 99 6833 2011-11-16 12:00 nas_conf_db.xml
-rw-rw-rw-  1 nobody 99 6833 2011-11-16 12:00 nas_conf_db.xml.bak
-rw-r--r--  1 nobody 99 7235 2016-07-17 22:14 nas_conf_db.xml.try
-rw-r--r--  1 nobody 99 7235 2016-07-17 22:14 nas_conf_db.xml.update
-rw-rw-rw-  1 nobody 99  125 2016-04-24 18:26 nas_ext_hdd_db.xml
-rw-r--r--  1 root    0   41 2011-11-16 12:00 ntp.conf
drwxrwxrwx  2 root    0 1024 2012-03-24 13:37 ssl


good to go?

mm.. these files are strange

Code: Select all

-rw-r--r--  1 nobody 99 7235 2016-07-17 22:14 nas_conf_db.xml.try
-rw-r--r--  1 nobody 99 7235 2016-07-17 22:14 nas_conf_db.xml.update

I need to ask Jocko if these are from the upgrade script.
the normal ones are

Code: Select all

-rw-rw-rw-  1 nobody 99 6833 2011-11-16 12:00 nas_conf_db.xml
-rw-rw-rw-  1 nobody 99 6833 2011-11-16 12:00 nas_conf_db.xml.bak


also look to the dates, these strange ones are from date 17 july when did the upgrade.
While the good ones have a date in 2011, which is the date when booting the nas.

Anyhow I think it is safe to reboot the spd8020
But as i do not know exactly what happened here there remains a risk that boot will fail. In that case nothing is lost but to make it operational again if it fails we need to take out the disk and connect to a pc running linux to restore the firmware

Reboot successful - web interface up and running again.
Update has not taken place - still at the old version.

No guts, no glory - I am going to retry ..... will post my experience :-)

Thanks for the help !!

Rik

Reboot successful - web interface up and running again.
Update has not taken place - still at the old version.

No guts, no glory - I am going to retry ..... will post my experience :-)

Thanks for the help !!

Rik

OK, no upgrade success yet.

this time I have a working web interface and an error message from the upgrade:

Code: Select all

=> Firmware upgrade step 2 started...
Unpack firmware package...(please wait) OK
Check Platform... OK
Check Image file... OK
Check DATABASE file... OK
Check active partition... OK
Write fs image in /dev/sda1...(please wait)
firmware upgrade failed while writing image to disk partition using dd command
Firmware upgrade failed, upgrade process aborted, reason:
50


Would be grateful for hints :shock:

Cheers,

Rik

This indicate that you have a harddisk issue, bad sector?.
In the disk menu you can run some test to check condition of your harddisk

Test run without errors (had to switch on SMART on the command line first).

Running 'badblocks' on /dev/sda1, 2, 5 and 6 did also not yield any issues (0 bad blocks).

However, as this NAS is indeed VERY old by now, harddisk issues are getting more and more likely.

I'll leave it for now - the system works :-D

Thanks again for the assistance !

Rik

Hi,

fvdw wrote:these files are strange

Code: Select all

-rw-r--r--  1 nobody 99 7235 2016-07-17 22:14 nas_conf_db.xml.try
-rw-r--r--  1 nobody 99 7235 2016-07-17 22:14 nas_conf_db.xml.update

I need to ask Jocko if these are from the upgrade script.

These files are not created by the upgrade script but at each time the firmware must update the nas database:
Before overwriting the previous nas database, it creates a temp file 'nas_conf_db.xml.update' and if it succeeds to do it the script replaces the previous database by the temporary file. This is done to avoid to overwrite the nas database by a corrupted file (for example if there is no enough free space on sda5)

The firmware does the same sequence with the backup file by using a temporary file 'nas_conf_db.xml.try'.

So if all is ok, these 2 files exist no longer after saving the new database.

With your outputs, I can say the firmware failed to do these 2 steps (please to note the offset of time-stamp between nas_conf_db.xml.update and nas_conf_db.xml). That would mean there was not enough free space on sda5 at '2016-07-17' or there are some I/O errors on your disk