Upgrade failed and gone to hell

[firwareslut]

I installed the 18 firmware a while ago and shut down my NAS at xmas when i went away. When I came back it wouldn't boot.

Finally, after looking at it properly today I found a similar thread about the NAS not booting after an upgrade to 18.

I renamed the /sda2/lacie-boot/ file to sda1 (don't remember exactly what it was called) and the NAS booted back to v17 firmware. I tried the web upgrade again to 18.2 and it failed.

Now when I boot I get this

Warning: session_start(): open(/tmp/sess_c168a0a4f18d61d1361926042d920b65, O_RDWR) failed: Read-only file system (30) in /usr/htdocs/home.hm on line 2 Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /usr/htdocs/home.hm:2) in /usr/htdocs/home.hm on line 2

The homepage doesn't load anything and nothing is working.

[Jocko]

Hi

So you can still go back to version 17.0

Warning: session_start(): open(/tmp/sess_c168a0a4f18d61d1361926042d920b65, O_RDWR) failed: Read-only file system (30) in /usr/htdocs/home.hm on line 2 Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /usr/htdocs/home.hm:2) in /usr/htdocs/home.hm on line 2

This would mean a permission issue on /rw_fs/tmp

Previously did you change it ? It must be 777

[Jocko]

CHeck also if sda5 is not mounted readonly after some errors

Code: Select all

mount

[firwareslut]

I have taken the disk out and run a check on each partition.

I set the rw_fs/tmp to 777 on both partitions.

I am unsure if SDA5 is mounting r/o or not but it isn't in Ubuntu when I mount it.

I have rebooted and now I get

The connection has timed out

The server at 192.168.0.150 is taking too long to respond.

and the blue lamp on NAS is fluttering like crazy...presumably some kind of disk process is going on?

[firwareslut]

I am a bit lost trying to find the setup disk guide for Linux for the NS2...where can I find it?

Might just be easier to start over and copy the public drive again.

[Jocko]

Hi

Indeed, the current nas status is understandable for me and a fresh install would be better.

First why do not you want to use fvdw-sl console ? which will be the easiest to do it (and also backup your data if it is required via a ftp access ?)

Otherwise you will find how to set up the disk here on a linux environment: http://plugout.net/viewtopic.php?f=7&t=336
you will start to install version 11.0 and step by step upgrade the fw to version 18.2: http://plugout.net/viewtopic.php?f=7&t=3059

[firwareslut]

To be honest, I looked at the Console thing and really didn't understand how to use it all and was confused by its purpose. It seemed far easier to load it into my Linux installation and manipulate it from there, since I know what I am doing.

[Jocko]

Maybe this page will help you
http://crecimiento-sostenible.blogspot.com/2017/03/repairing-and-updating-lacie-nas-fvdw.html?m=1 a

[firwareslut]

I reinstalled the firmware with the console and that worked ok. I did the reboot command and then nothing happened.

I started up the console again and tried to mount sda1 or sda2 to get a look at the log file and i get this

mount: mounting /dev/sda1 on /sda1 failed: Function not implemented

When I mount /sda7 there is no boot.log file in the root.

I reboot the NAS again and the front light is blinking and no reply to ping. THe assistant doesn't find any IP for the NAS.

[fvdw]

Seems you have a disk problem ( bad sectors). I suggest you start at command line when running the standalone kernel the e2fsck command

Code: Select all

e2fsck -y /dev/sda1

And see if it finds and repairs problems, suggest to do the same for sda2, 5 and 7.
Note that the command must not be executed if the partition is mounted