Two little bugs

[Aled72]

Hi,
I detected two small bugs,
1- when trying to activate afp server the system fails and error 6.
Message: Current System Status: Fail: start command failed (6)

2- when the raid is disassembled the system no longer recognizes the disk sda, gives it to zero bytes and can no longer format it.
look the image: download/file.php?mode=view&id=5136

[Jocko]

Hi Aled72,

For bug 1,it is an error when I built the update package for version 17.0. I included a file with a bad version (file for the next firmware version).

So attached a patch to fix it :
Store the attached archive in the share fvdw, and do

Code: Select all

tar -xf fvdw-sl-17-0-fix-api-version-19feb18.tar.gz -C /

Then you should be able to start again the afp server.

About bug 2, I need more time to detect your issue. (Last WE, I destroyed an usb raid with the same settings as yours, without issue).
At least I need more information after destroying the raid:
- post the content of the setup log file (you should still have it in /etc/.setup.fs
-

Code: Select all

fdisk -l /dev/sda

-

Code: Select all

file -bs /dev/sda8

-

Code: Select all

 /etc/api/nasapi.php "mrvlGetDisk high all"
/etc/api/nasapi.php "mrvlGetVolume high all"

[Jocko]

Hi,

I fixed the other bug and it is not a minor bug as data volume settings are corrupted in the nas data base and there is no easy way to restore them manually!
This is a bug on version 17.0. The issue was on two global variables which were not set at the right level...

But fortunately, this happens only when the data volume of a NAS with a single internal disk is included in a raid. So, not the common case :whistle

Attached a patch to fix it :
Store the attached archive in the share fvdw, and do

Code: Select all

tar -xf fvdw-sl-17-x-restore-vol-sda8-20feb18.tar.gz -C /

Note: You should not be able to use this way to install it (and also with the previous archive) as no fvdw share should exist.

So a work around is to use the firmware upgrade menu, click on the small button '+' :
* upload the attached file (step1) but do not run step2
* open a shell terminal and do

Code: Select all

cd /tmp
mv firmware.bin fvdw-sl-17-x-restore-vol-sda8-20feb18.tar.gz
tar -xf fvdw-sl-17-x-restore-vol-sda8-20feb18.tar.gz -C /

Reload the upgrade firmware menu and repeat with fvdw-sl-17-0-fix-api-version-19feb18.tar.gz file

Then reboot the nas.

[Aled72]

Little trouble:

root@BKP-Central:/tmp # mv firmware.bin fvdw-sl-17-x-restore-vol-sda8-20feb18.tar.gz
mv: cannot stat `firmware.bin': No such file or directory

firmware.bin is not present in /tmp directory

[Jocko]

Ok I think you did not click on the button "update firmware with an upgrade file" (this starts only the step1) after selecting the tar file

[Aled72]

The problem with upload is this in the image.
download/file.php?mode=view&id=5144

can't upload the file and if I upload via ftp in root dir I can't see it.

Can I copy firmware.bin from another location?

[Jocko]

You did not use the right menu. This one is for installing a patch (and it can not be use as there is no data partition)

So use the upgrade firmware menu (first sub-menu)

So a workaround is to use the firmware upgrade menu, click on the small button '+' :

[Aled72]

Hi applied patch and now I see sda but unformatted.
When I try to initialize it can't do it and this show this message:

Code: Select all

Reported message:
   Fail (volume unknown)

Restart the NAS to switch in regular mode.

More detail in:  /etc/.setup.fs/setupjob.log

setupjob.log text is this:

Code: Select all

root@BKP-Central:/etc/.setup.fs # cat setupjob.log                           
<b>Setup task reset.sh is now running</b><br>
Found disk: sda(JK1105B8GYG4VX) <br>
Found disk: seg(00D04BA71808948A) <br>
Format partition sda8 with file system ext4: <br>
=>mke2fs 1.43.4 (31-Jan-2017)
Creating filesystem with 487653137 4k blocks and 121913344 inodes
Filesystem UUID: 86232a11-2f45-4339-aaa1-9c0a3faf414a
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848

Allocating group tables: done                           
Writing inode tables: done                           
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done       

=>Formatting sda8 succeeded<br>
Update partition type on sda8: OK<br>
Remove orphan shares:<span style="color:red;"><b>Fail (volume unknown)</b></span><br>
root@BKP-Central:/etc/.setup.fs #

Alternatives?!? Disassemble disk again and format it for reinstall?!? :thinking

[Jocko]

Ok so not fully fixed :mrgreen: :scratch

Please do not run more setup job : more you run setup jobs less I wil understand what is the current state of your NAS.

As sda8 was formatted after destroying the raid (ext4), you should not need to run a reset or format setup job on it.

So this time I really need these outputs

Code: Select all

mount
fdisk -l /dev/sda
file -bs /dev/sda8
/etc/api/nasapi.php "mrvlGetDisk high all"
/etc/api/nasapi.php "mrvlGetVolume high all"


Alternatives?!? Disassemble disk again and format it for reinstall?!? :thinking

Please do not do that. Your issue is a major bug on platform with only one internal disk and we need to fix it.
It seems I failed to reproduce your bug, as with the patch I succeeded to restore the data volume after destroying the raid on my nwsp2 (similar platform). This evening, I go to check if I made an error when I built the posted patch.

[Aled72]

What about .... happy to be helpful :lmao

Mount

Code: Select all

root@BKP-Central:/ # 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@BKP-Central:/ #


fdisk -l /dev/sda

Code: Select all

root@BKP-Central:/ # fdisk -l /dev/sda

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1      242252  1953514583+ ee EFI GPT
root@BKP-Central:/ #

file -bs /dev/sda8

Code: Select all

[code]root@BKP-Central:/ # file -bs /dev/sda8
Linux rev 1.0 ext4 filesystem data, UUID=86232a11-2f45-4339-aaa1-9c0a3faf414a (extents) (large files) (huge files)
root@BKP-Central:/ #
[/code]

/etc/api/nasapi.php "mrvlGetDisk high all"
[code]
root@BKP-Central:/ # /etc/api/nasapi.php "mrvlGetDisk high all"
PHP Warning:  filesize(): stat failed for /rw_fs/tmp/etc/nas_conf_vltl.xml in /etc/finc/configfunc_read.finc on line 33

Warning: filesize(): stat failed for /rw_fs/tmp/etc/nas_conf_vltl.xml in /etc/finc/configfunc_read.finc on line 33
root@BKP-Central:/ #
[/code]

/etc/api/nasapi.php "mrvlGetVolume high all"
[code]
root@BKP-Central:/ # /etc/api/nasapi.php "mrvlGetVolume high all"
PHP Warning:  filesize(): stat failed for /rw_fs/tmp/etc/nas_conf_vltl.xml in /etc/finc/configfunc_read.finc on line 33

Warning: filesize(): stat failed for /rw_fs/tmp/etc/nas_conf_vltl.xml in /etc/finc/configfunc_read.finc on line 33
root@BKP-Central:/ #