We need to investigate more what happens and then use telnet access with fvdw-sl console.
So stop your nas and select the action "Standalone kernel, load and start". Of course you need to use this time the standalone kernel version for 5big1.
Connect you and post the outputs of these commands
- Code: Select all
mkdir sda7 sda5 sda1 sda2
mount /dev/sda7 /sda7
ls -l /sda7/lacie-boot (please to see if it lists a file sda1boot or sda2boot)
cat /sda7/boot.log
mount /dev/sda5 /sda5
cat /sda5/etc/install-firmware.log (this will get the upgrade log of your last upgrade attempt)
# according the listed file (sda1boot or sda2boot), mount the related partition (sda1 or sda2)
mount /dev/sdax /sdax (x=1 or 2)
cat /sdax/boot.log
Note: there is another critical step : when the script swaps the firmware partition. So if it happens at the time as you did a roll-back, the nas will fail to restart because the nas database contains data not supported by the firmware version used at the first install.