Page 1 of 1

18.2 Firmware Update Failure 5big

PostPosted: Sun Dec 22, 2019 5:49 pm
by knisa
Tried to update from 18.1 to 18.2 just now and it failed.

=> Firmware upgrade step 1 started:
Search firmware version information for 5big1 ...
The latest version available from http://plugout.net is: fvdw-sl 18.2

Check free space on system partition ... OK
Get the bound upgrade files list
Retrieve the firmware package
Try to download part 1 on 5...
Attempt 1: OK, got successful the firmware package part1 file
Try to download part 2 on 5...
Attempt 1: OK, got successful the firmware package part2 file
Try to download part 3 on 5...
Attempt 1: OK, got successful the firmware package part3 file
Try to download part 4 on 5...
Attempt 1: OK, got successful the firmware package part4 file
Try to download part 5 on 5...
Attempt 1: OK, got successful the firmware package part5 file
Extract firmware package...
OK, extract successful the firmware package
Retrieve kernel image file for 5big1...
Attempt 1: OK, got successful the kernel image file

OK: Retrieve the latest firmware image file successful


=> Firmware upgrade step 2 started:
Firmware package uploaded via fvdw-sl server
package type: new configuration (version > 16.1)
firmware image type: extended file system (version > 17.0)
Check firmware files archive ... OK
Detect family type... OK
Check kernel version... OK
Check DATABASE file... OK
Check active partition... OK
Install new common firmware files on /dev/sda1, ... Fail
can not mount the new system partition

I tired it more times and it do not success.

Re: 18.2 Firmware Update Failure 5big

PostPosted: Sun Dec 22, 2019 6:46 pm
by fvdw
Seems there is a problem with partition sda1, this could be a disk issue. Are you able to connect via ssh server and give these commands on the linux command line
Code: Select all
df -h

Code: Select all
ls -al /lacieboot

Code: Select all
mount

Code: Select all
mkdir sda1
mount /dev/sda1 /sda1

And post output of these commands

Re: 18.2 Firmware Update Failure 5big

PostPosted: Sun Dec 22, 2019 8:11 pm
by knisa
Thanks! I will try it.

Re: 18.2 Firmware Update Failure 5big

PostPosted: Sun Dec 22, 2019 8:27 pm
by knisa
I tried it:

root@KINAS:/ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 479M 143M 332M 31% /
/dev/sda5 787M 79M 700M 11% /rw_fs
tmpfs 4.9M 104K 4.8M 3% /rw_fs/tmp/usr/var
root@KINAS:/ # ls -al /lacieboot
ls: /lacieboot: No such file or directory

:please

Re: 18.2 Firmware Update Failure 5big

PostPosted: Sun Dec 22, 2019 8:34 pm
by fvdw
Sorry type error
Code: Select all
ls -al /lacie-boot
please post output, this to be sure the nas has booted from sda2

Also please try the commands and post what output they give
Code: Select all
mount

And
Code: Select all
mkdir sda1
mount /dev/sda1 /sda1

Re: 18.2 Firmware Update Failure 5big

PostPosted: Mon Dec 23, 2019 4:40 pm
by knisa
Thanks! I will try it later. I sended Donate now.

Re: 18.2 Firmware Update Failure 5big

PostPosted: Fri Dec 27, 2019 10:27 am
by knisa
I have one 1Tb HDD on the first slot (left).

root@KINAS:/ # ls -al /lacie-boot
total 2
drwxrwxr-x 2 root root 1024 1970-01-01 01:00 .
drwxr-xr-x 23 root root 1024 2019-12-27 10:52 ..
root@KINAS:/ # mount
/dev/sda7 on / type ext3 (rw,relatime,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
/dev/sda5 on /rw_fs type ext3 (rw,noatime,data=ordered)
tmpfs on /rw_fs/tmp/usr/var type tmpfs (rw,relatime,size=5000k)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
root@KINAS:/ #

But I think I have disk initializing problem. Please see "Disk initializing problem" topic.

Re: 18.2 Firmware Update Failure 5big

PostPosted: Fri Dec 27, 2019 11:28 am
by knisa
During I re-install 18.1 fw and update 18.2.
It is successfully !!

Thanks your advice !

Re: 18.2 Firmware Update Failure 5big

PostPosted: Fri Dec 27, 2019 11:32 am
by Jocko
Hi knisa,

Please to note you can not reset fully sda because it contains the firmware and then you will erase it !. On sda disk, the firmware reset only the data partition (sda8)

The issue was on the partition sda1. So a reinstall solved it.