upgrade to 16.1 not without issues

Re: upgrade to 16.1 not without issues

Postby Jocko » Wed Jan 06, 2016 3:35 pm

knielen wrote:Looks like it works, even after a reboot, RPi is much more responsive as well.
So the patch seems ok.

Now we try to reboot the NAS in the same context than after upgrading :
restore the former diskid value and reboot the NAS.

I assume the share "temp" still exists:
- backup the nas database
Code: Select all
cp /etc/nas_conf_db.xml  /share/1000/temp/nas_conf_db.xml.org1

- copy the nas database
Code: Select all
cp /etc/nas_conf_db.xml  /share/1000/temp

- edit the nas database : remove the string "-0:0" in diskid node of sda disk to get the former diskid "DE177DE8040000BF_Samsung_M3_Portable"
- overwrite the nas database in /etc
Code: Select all
cp /share/1000/temp/nas_conf_db.xml /etc

- check if there is nothing wrong (load disk setup menu)

-If yes, you can reboot the NAS and see if the disk is mounted again (usb disks menu), the shares are restored on it (main share menu) and only one USB disk (disk setup menu).

Note: indeed with version 16.1, web-interface is more responsive as fvdw-sl handles better the browser cache.
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: upgrade to 16.1 not without issues

Postby knielen » Wed Jan 06, 2016 5:30 pm

This is the end result:
Code: Select all
root@fvdwsl-base:/ # grep -A 20 '<disk>' etc/nas_conf_db.xml
                        <disk>
                                <device>/dev/sda</device>
                                <inactivityperiod>15</inactivityperiod>
                                <lastselftest>0</lastselftest>
                        </disk>
                        <usbguard>
                                <enable>true</enable>
                                <inactivityperiod>15</inactivityperiod>
                        </usbguard>
                </hdparams>
                <notify>
                        <eventbmp>3</eventbmp>
                        <email>
                                <enable>false</enable>
                                <address/>
                                <smtpip/>
                        </email>
                        <icq>
                                <enable>false</enable>
                                <idnum/>
                                <passwd/>
--
                <disk>
                        <size>2.39004135132</size>
                        <internal>true</internal>
                        <name>Single</name>
                        <system>true</system>
                        <blockdev>/dev/mmcblk0</blockdev>
                        <diskid>035344534c303847801977366300e900</diskid>
                        <model>SL08G</model>
                        <usb>false</usb>
                        <freesize>0</freesize>
                        <init>true</init>
                        <partitions>
                                <partition>
                                        <lvname>/dev/mmcblk0p4</lvname>
                                        <volid>1000</volid>
                                        <color>#9d773e</color>
                                        <index>0</index>
                                        <size>2.39004135132</size>
                                </partition>
                        </partitions>
                </disk>
                <disk>
                        <size>1863.01269531</size>
                        <internal>true</internal>
                        <name>USB-A</name>
                        <system>false</system>
                        <blockdev>/dev/sda</blockdev>
                        <diskid>DE177DE8040000BF_Samsung_M3_Portable</diskid>
                        <model>Samsung_M3_Portable</model>
                        <usb>true</usb>
                        <freesize>0</freesize>
                        <init>true</init>
                        <partitions>
                                <partition>
                                        <lvname>/dev/sda5</lvname>
                                        <volid>2001</volid>
                                        <color>#71d975</color>
                                        <index>0</index>
                                        <size>1863.01269531</size>
                                </partition>
                        </partitions>
                </disk>
root@fvdwsl-base:/ # grep -A 11 '<vol>' etc/nas_conf_db.xml
                <vol>
                        <volid>1000</volid>
                        <md>/dev/mmcblk0p4</md>
                        <fs>1000</fs>
                        <lastindex>1</lastindex>
                        <name>SD-Card</name>
                        <devices/>
                        <raidtype>single</raidtype>
                        <color>#9d773e</color>
                        <formatting>0</formatting>
                        <size>2.39004135132</size>
                </vol>
                <vol>
                        <volid>2001</volid>
                        <md>/dev/sda5</md>
                        <fs>2001</fs>
                        <lastindex>1</lastindex>
                        <name>USB-A-5</name>
                        <devices/>
                        <raidtype>single</raidtype>
                        <color>#71d975</color>
                        <formatting>0</formatting>
                        <size>1863.01269531</size>
                </vol>

If I check my file shares it says : /share/1000 & /share/2000
Output in the terminal still says volid 2001, not sure if that's normal. Everything else looks fine and functions fine
knielen
Donator VIP
Donator VIP
 
Posts: 16
Joined: Tue Dec 30, 2014 12:20 pm

Re: upgrade to 16.1 not without issues

Postby Jocko » Wed Jan 06, 2016 6:12 pm

No it is not fully nice :
At NAS booting it reuses the disk node with the former diskid :thumbup but it did not update it (not added the instance value)
If I check my file shares it says : /share/1000 & /share/2000

And it should say /share/2001. Or a cache issue of your file browser (do you use winscp ?)

So need some outputs:
Code: Select all
mount
ls -l /direct-usb /usr/local
ls -l /share
grep -A 1 '<sharemount>' /etc/nas_conf_db.xml
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: upgrade to 16.1 not without issues

Postby knielen » Wed Jan 06, 2016 6:45 pm

No, I don't use winscp, and a clear of my browser cache makes no difference. here's the requested output:
Code: Select all
root@fvdwsl-base:/ # mount
rootfs on / type rootfs (rw)
/dev/root on / type ext4 (rw,relatime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=85060k,nr_inodes=21265,mode=755)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
/dev/mmcblk0p7 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/mmcblk0p6 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)
/dev/mmcblk0p4 on /share/1000 type ext3 (rw,relatime,data=ordered)
/dev/sda5 on /share/2001 type ext4 (rw,noatime,data=ordered)
/dev/root on /lacie-boot type ext4 (rw,relatime,data=ordered)
root@fvdwsl-base:/ # ls -l /direct-usb /usr/local
lrwxrwxrwx  1 root root 11 2011-11-16 12:00 /direct-usb -> /share/2001
lrwxrwxrwx  1 root root 23 2011-11-16 12:00 /usr/local -> /share/2001/fvdw/addons
root@fvdwsl-base:/ # ls -l /share
total 8
drwxrwxrwx   5 root root 4096 2016-01-06 09:13 1000
drwxrwxrwx  11 root root 4096 2016-01-06 09:31 2001
lrwxrwxrwx   1 root root    4 2011-11-16 12:00 SD-Card -> 1000
lrwxrwxrwx   1 root root    4 2011-11-16 12:00 USB-A-5 -> 2001
root@fvdwsl-base:/ # grep -A 1 '<sharemount>' /etc/nas_conf_db.xml
                        <sharemount>1000</sharemount>
                        <volid>1000</volid>
--
                        <sharemount>2001</sharemount>
                        <volid>2001</volid>
--
                        <sharemount>2001</sharemount>
                        <volid>2001</volid>
--
                        <sharemount>2001</sharemount>
                        <volid>2001</volid>
--
                        <sharemount>2001</sharemount>
                        <volid>2001</volid>
--
                        <sharemount>1000</sharemount>
                        <volid>1000</volid>
--
                        <sharemount>2001</sharemount>
                        <volid>2001</volid>
--
                        <sharemount>2001</sharemount>
                        <volid>2001</volid>
--
                                <sharemount>2000</sharemount>
                        </webshare>
root@fvdwsl-base:/ #
knielen
Donator VIP
Donator VIP
 
Posts: 16
Joined: Tue Dec 30, 2014 12:20 pm

Re: upgrade to 16.1 not without issues

Postby Jocko » Wed Jan 06, 2016 6:59 pm

Your last outputs are not so bad :
all main settings are ok disk mounted on /share/2001 and shares settings are related with 2001 so on this side is Ok

Now I understand what you mean by "f I check my file shares it says " : you use webexplorer and indeed the mount point of the webshares is not updated
Code: Select all
<sharemount>2000</sharemount>
                        </webshare>
Need to deepen this point but currently I believe the firmware does not handle this case (you must manually disable and enable again the share in webexplorer menu)

So currently the issue would be only disk id is not updated (strange as on my side it is :scratch )

Need to do some more test on my side.

See you later
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: upgrade to 16.1 not without issues

Postby Jocko » Wed Jan 06, 2016 7:33 pm

On my 5big2, I don't have this issue (diskid not updated) and I confirm you have an issue with webexplorer because you have a corrupted nas database and we forgot to restore the mount point settings on the web shares when you had two disks.

So for this last point you must disable/enable again the share set on the usb disk in webexplorer menu.

I go to send you some new files to trace what happens when the usb disk is mounted.

after installing them :
- enable the debug mode
Code: Select all
/etc/nas_status.sh --start-debug

- repeat this sequence fully (best after fixing your issue with webexplorer):
*backup the nas database
Code: Select all
cp /etc/nas_conf_db.xml  /share/1000/temp/nas_conf_db.xml.org2

* copy the nas database
Code: Select all
cp /etc/nas_conf_db.xml  /share/1000/temp

* edit the nas database : remove the string "-0:0" in diskid node of sda disk to get the former diskid "DE177DE8040000BF_Samsung_M3_Portable"
* overwrite the nas database in /etc
Code: Select all
cp /share/1000/temp/nas_conf_db.xml /etc


restart the nas
and post the file /var/log/messages

Note: better to disable the debug mode
Code: Select all
/etc/nas_status.sh --stop-debug
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: upgrade to 16.1 not without issues

Postby knielen » Thu Jan 07, 2016 6:13 pm

Hi Jocko,
Here we go again :-)
I'm not sure if this is what you expect, nothing special with the date of today :
Code: Select all
Nov 16 12:00:13 (none) syslog.info syslogd started: BusyBox v1.21.0
Nov 16 12:00:15 (none) local0.warn API[2011/11/16 12:00:15] nasapi.inc(36)[308]: nasapi: lock time = 0
Nov 16 12:00:16 (none) local0.warn API[2011/11/16 12:00:16] nasapi.inc(46)[308]: calling mrvlUdevdAttached sda5
Nov 16 12:00:16 (none) local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/cat /etc/platform
Nov 16 12:00:16 (none) local0.warn API[2011/11/16 12:00:16] udevfunc_attached.finc(34)[308]: Request to attach sda5 for rspb2
Nov 16 12:00:16 (none) local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/vol_id -t /dev/sda5
Nov 16 12:00:17 (none) local0.warn API[2011/11/16 12:00:17] exthddfunc_mountUsbRpiHdd.finc(22)[308]: Request to mount for sda5
Nov 16 12:00:17 (none) local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/usb_id -x /block/sda
Nov 16 12:00:17 (none) local0.warn API[2011/11/16 12:00:17] exthddfunc_mountUsbRpiHdd.finc(50)[308]: Warning: former diskid [DE177DE8040000BF_Samsung_M3_Portable] on sda5
Nov 16 12:00:17 (none) local0.warn API[2011/11/16 12:00:17] exthddfunc_mountUsbRpiHdd.finc(79)[308]: disk sda was known with devicename /dev/sda
Nov 16 12:00:17 (none) local0.warn API[2011/11/16 12:00:17] exthddfunc_mountUsbRpiHdd.finc(165)[308]: Found a partition for sda5 with volid 2001
Nov 16 12:00:17 (none) local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/vol_id -l /dev/sda5
Nov 16 12:00:17 (none) local0.warn API[2011/11/16 12:00:17] exthddfunc_mountUsbRpiHdd.finc(211)[308]: Found volume for sda5 with volid 2001
Nov 16 12:00:17 (none) local0.warn API[2011/11/16 12:00:17] exthddfunc_mountUsbRpiHdd.finc(215)[308]: sda5 is not in a RAID ARRAY
Nov 16 12:00:17 (none) local0.warn API[2011/11/16 12:00:17] exthddfunc_mountUsbRpiHdd.finc(310)[308]: try to restore backup shares
Nov 16 12:00:17 (none) local0.warn API[2011/11/16 12:00:17] exthddfunc_mountUsbRpiHdd.finc(328)[308]: backup conf file, search records
Nov 16 12:00:17 (none) local0.warn API[2011/11/16 12:00:17] nasapi.inc(670)[308]: mrvlUdevdAttached sda5 Return Code: 0
Nov 16 12:00:17 (none) local0.warn API[2011/11/16 12:00:17] nasapi.inc(36)[307]: nasapi: lock time = 2
Nov 16 12:00:18 (none) local0.warn API[2011/11/16 12:00:18] nasapi.inc(46)[307]: calling mrvlUdevdAttached sda1
Nov 16 12:00:18 (none) local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/cat /etc/platform
Nov 16 12:00:18 (none) local0.warn API[2011/11/16 12:00:18] udevfunc_attached.finc(34)[307]: Request to attach sda1 for rspb2
Nov 16 12:00:18 (none) local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/vol_id -t /dev/sda1
Nov 16 12:00:18 (none) local0.warn API[2011/11/16 12:00:18] exthddfunc_mountExtHdd.finc(35)[307]: Request to mount sda1
Nov 16 12:00:18 (none) local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/vol_id -l /dev/sda1
Nov 16 12:00:18 (none) local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sda
Nov 16 12:00:18 (none) local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sda
Nov 16 12:00:18 (none) local0.warn API[2011/11/16 12:00:18] exthddfunc_mountExtHdd.finc(112)[307]: unknown filesystem f
Nov 16 12:00:18 (none) local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/mv_reg_bit_set 0x10108 6 1
Nov 16 12:00:23 (none) local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/mv_reg_bit_set 0x10108 6 0
Nov 16 12:00:24 (none) local0.warn API[2011/11/16 12:00:24] nasapi.inc(670)[307]: mrvlUdevdAttached sda1 Return Code: 1
Nov 16 12:00:25 (none) local2.notice sudo:     root : TTY=console ; PWD=/ ; USER=root ; COMMAND=/usr/bin/lsscsi -t
Nov 16 12:00:25 (none) local2.notice sudo:     root : TTY=console ; PWD=/ ; USER=root ; COMMAND=/usr/bin/lsscsi -t
Nov 16 12:00:26 (none) local2.notice sudo:     root : TTY=console ; PWD=/ ; USER=root ; COMMAND=/bin/cat /sys/class/mmc_host/mmc0/mmc0:aaaa/name
Nov 16 12:00:26 (none) local2.notice sudo:     root : TTY=console ; PWD=/ ; USER=root ; COMMAND=/bin/cat /sys/class/mmc_host/mmc0/mmc0:aaaa/cid
Nov 16 12:00:26 (none) local2.notice sudo:     root : TTY=console ; PWD=/ ; USER=root ; COMMAND=/bin/cat /sys/block/mmcblk0/mmcblk0p4/size
Nov 16 12:00:26 (none) local2.notice sudo:     root : TTY=console ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --examine --brief /dev/mmcblk0p4
Nov 16 12:00:26 (none) local2.notice sudo:     root : TTY=console ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --examine --brief /dev/sda5
Nov 16 12:00:26 (none) local2.notice sudo:     root : TTY=console ; PWD=/ ; USER=root ; COMMAND=/sbin/vol_id -l /dev/sda5
Nov 16 12:00:28 (none) local0.warn API[2011/11/16 12:00:28] exthddfunc_wait_allmountExtHdd.finc(65)[237]: check [DE177DE8040000BF-0:0_Samsung_M3_Portable]:[DE177DE8040000BF-0:0_Samsung_M3_Portable]
Nov 16 12:00:28 (none) local0.warn API[2011/11/16 12:00:28] exthddfunc_wait_allmountExtHdd.finc(80)[237]: vol:1000:
Nov 16 12:00:28 (none) local0.warn API[2011/11/16 12:00:28] exthddfunc_wait_allmountExtHdd.finc(80)[237]: vol:2001:
knielen
Donator VIP
Donator VIP
 
Posts: 16
Joined: Tue Dec 30, 2014 12:20 pm

Re: upgrade to 16.1 not without issues

Postby Jocko » Thu Jan 07, 2016 6:31 pm

Good evening, Knielen

You have the same trace than on my 5big2 :
Code: Select all
Nov 16 12:00:17 (none) local0.warn API[2011/11/16 12:00:17] exthddfunc_mountUsbRpiHdd.finc(50)[308]: Warning: former diskid [DE177DE8040000BF_Samsung_M3_Portable] on sda5

Nov 16 12:00:28 (none) local0.warn API[2011/11/16 12:00:28] exthddfunc_wait_allmountExtHdd.finc(65)[237]: check [DE177DE8040000BF-0:0_Samsung_M3_Portable]:[DE177DE8040000BF-0:0_Samsung_M3_Portable]


=> the boot script detected the former diskid and updated it :scratch

Maybe you used a wrong datafile when you read the nas database. Can you post again
Code: Select all
grep  '<diskid>' /etc/nas_conf_db.xml
(use full path !)

About webexplorer, the issue is now fixed ?
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: upgrade to 16.1 not without issues

Postby knielen » Thu Jan 07, 2016 6:38 pm

Code: Select all
root@fvdwsl-base:/var/log # grep  '<diskid>' /etc/nas_conf_db.xml
                        <diskid>035344534c303847801977366300e900</diskid>
                        <diskid>DE177DE8040000BF-0:0_Samsung_M3_Portable</diskid>


web-explorer does run now, but can't find the root folder, this is the message:
Unauthorized login !
Error : Root folder :USB-A-5/Ftp/Kay, is not available !

Allready re-created the authentication and folder, but still not working
knielen
Donator VIP
Donator VIP
 
Posts: 16
Joined: Tue Dec 30, 2014 12:20 pm

Re: upgrade to 16.1 not without issues

Postby Jocko » Thu Jan 07, 2016 6:52 pm

So the path fixes fully the diskid issue

As the last debug patch is too verbose, you should install again the first patch.

About webexplorer, I think the best way is to make a reset (from webexplorer menu) : you will lost all webexplorer settings but not data.
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

PreviousNext

Return to Raspberry Pi 1, 2, 3 and 4

Who is online

Users browsing this forum: No registered users and 1 guest