Fail to update to version 18.1

[maxdo]

Hi TEam,
i have a NAS 2BIG v2, with firmware 17.0, and i want to migrate it to version 18.1.

so, following your procedure:
- i have update the NAS to fvdw-sl-17.0-patch11-30jun2019.zip(17-0-patch11.sh)
- then afre reboot the NAS, i had click the button for have the new version.
The first STEP it is termiante with success:
=> Firmware upgrade step 1 started:
Search firmware version information for 2big2 ...
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 kirkwood...
Attempt 1: OK, got successful the kernel image file

OK: Retrieve the latest firmware image file successful

Then i have run the STEP 2, but here i have the follow error:
=> 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... new version must be installed
Check DATABASE file... OK
Check active partition... OK
Install new common firmware files on /dev/sda1, ... Fail
can not mount the new system partition

why can't mount the sda1?
and why i read that need to have the new version kernel, when in the STEP 1 the new kernel image it is conclude with success?

thanks

[fvdw]

about kernel question, the new kernel is only downloaded not yet installed that is only done if current kernel is older.
Thats the check in step 2.

Why you cannot mount sda1.

Login via ssh server and on linux command line give these commands to see if we can mout it manually or which error we get

Code: Select all

mkdir /sda1
mount /dev/sda1 /sda1

In principle mount will fail if no file system is present on that partition.
That would mean formatting of sda1 failed, maybe because a disk error ??

assume mount sda1 fails then we can try to format it manually to see if there is a problem.
IMPORTANT
Before attempting formatting we must be sure that your nas is using sda2 as active partition.
To find out give this command

Code: Select all

ls /lacie-boot

If it mentions sda2boot then it uses sda2 to boot and is it safe to attempt to format sda1
If it mentions sda1boot then do NOT not use following command

Code: Select all

mkfs.ext3 -m 1 -j /dev/sda1

[Jocko]

Hi maxdo

As you are the 2d member with this issue, please to post before formatting (mke2fs command line), the output of

Code: Select all

tune2fs -l /dev/sda1

[maxdo]

Hi team,
thanks for your answer.

follow the output of the console SSH:
login as: root
root@192.168.4.252's password:
root@fvdwsl-base:/ # mkdir /sda1
root@fvdwsl-base:/ # mount /dev/sda1 /sda1
mount: /sda1: /dev/sda1 is not a valid block device.
root@fvdwsl-base:/ #
root@fvdwsl-base:/ #
root@fvdwsl-base:/ # la /lacie-boot
-sh: la: not found
root@fvdwsl-base:/ # ls /lacie-boot
root@fvdwsl-base:/ # ls /lacie-boot
root@fvdwsl-base:/ #
root@fvdwsl-base:/ #
root@fvdwsl-base:/ #
root@fvdwsl-base:/ # tune2fs -l /dev/sda1
tune2fs 1.43.4 (31-Jan-2017)
tune2fs: No such device or address while trying to open /dev/sda1
Couldn't find valid filesystem superblock.

how you can see :
- i have not a valid block device
- the ls /lacie-boot command give me not any answer to screen
- the tune2fs doesn't find file system superblock

if you need of more inforamtion you are welcome.
ciao

[Jocko]

So run now the mke2fs command and post again tune2fs output. If you have a clean fs, you can make a new fw upgrade attempt

Note : you made on the first attempt an error on ls command, (you used 'la' instead of 'ls'). Currently you use sda7 as fw partition. So no issue to format sda1

[Jocko]

I checked the upgrade script again and plainly it is the mke2fs command which generates the error. Maybe because it is performed immediately after a dd command which destroys the previous superblock.
So perhaps an issue with the disk cache and a sync step running. I go to add a sync command before running the mke2fs command.

[maxdo]

So run now the mke2fs command and post again tune2fs output. If you have a clean fs, you can make a new fw upgrade attempt

Note : you made on the first attempt an error on ls command, (you used 'la' instead of 'ls'). Currently you use sda7 as fw partition. So no issue to format sda1

hi but tune2fs and mke2fs wich parameter i need to give us?
becasue alone give me back

root@fvdwsl-base:/ # mke2fs
Usage: mke2fs [-c|-l filename] [-b block-size] [-C cluster-size]
[-i bytes-per-inode] [-I inode-size] [-J journal-options]
[-G flex-group-size] [-N number-of-inodes] [-d root-directory]
[-m reserved-blocks-percentage] [-o creator-os]
[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
[-t fs-type] [-T usage-type ] [-U UUID] [-e errors_behavior][-z undo_file]
[-jnqvDFSV] device [blocks-count]
root@fvdwsl-base:/ # tune2fs
tune2fs 1.43.4 (31-Jan-2017)
Usage: tune2fs [-c max_mounts_count] [-e errors_behavior] [-f] [-g group]
[-i interval[d|m|w]] [-j] [-J journal_options] [-l]
[-m reserved_blocks_percent] [-o [^]mount_options[,...]]
[-p mmp_update_interval] [-r reserved_blocks_count] [-u user]
[-C mount_count] [-L volume_label] [-M last_mounted_dir]
[-O [^]feature[,...]] [-Q quota_options]
[-E extended-option[,...]] [-T last_check_time] [-U UUID]


thanks

[maxdo]

I checked the upgrade script again and plainly it is the mke2fs command which generates the error. Maybe because it is performed immediately after a dd command which destroys the previous superblock.
So perhaps an issue with the disk cache and a sync step running. I go to add a sync command before running the mke2fs command.

so i will downlaod the new upgrade and ifnd in it the fix of the my issue?

thanks

[Jocko]

so i will downlaod the new upgrade and ifnd in it the fix of the my issue?

Not sure it is an issue with the upgrade script or an issue with your disk.

So need first your output about

So run now the mke2fs command and post again tune2fs output. If you have a clean fs, you can make a new fw upgrade attempt

=>

Code: Select all

mkfs.ext3 -m 1 -j /dev/sda1

and

Code: Select all

tune2fs -l /dev/sda1

[maxdo]

here you are the output command

root@fvdwsl-base:/ # mkfs.ext3 -m 1 -j /dev/sda1
mke2fs 1.43.4 (31-Jan-2017)
Could not open /dev/sda1: No such device or address
root@fvdwsl-base:/ # tune2fs -l /dev/sda1
tune2fs 1.43.4 (31-Jan-2017)
tune2fs: No such device or address while trying to open /dev/sda1
Couldn't find valid filesystem superblock.
root@fvdwsl-base:/ #

thanks