Can't create shares anymore

[Flurkje]

Hi,

I'm rebuilding a 5BIG2. Originally it had the Lacie fireware on it and the raid volume/firmware got corrupted. I managed to recover the data by installing the disk in a PC and using a linux rescue CD.

After the data was recovered it became inpossible to get the Lacie firmware back online. I used FVDW and spend hours on replicating the succes stories on the forum and in the end I had the firmware back up and running but my data partition was 250MB instead of 2TB.

I decided to give up on the Lacie firmware and switched to the FVDW firmware (16.1) next I followed the instructions for the creation of a RAID6 volume and this is where something must have gone wrong. I have removed the sda8 partition and recreated it, causing the public share to disappear (there was no data on it)

Now, when I try to create a new share, I get an error message on the web interface after a second or so:
Current System Status: Can't create: test (1)

I've enabled debugging using

Code: Select all

 /etc/nas_status.sh --start-debug

and this shows an error 'volume is busy'

Code: Select all

Feb 18 00:10:14 fvdwsl-base syslog.info syslogd started: BusyBox v1.21.0
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(36)[1577]: nasapi: lock time = 0
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(46)[1577]: calling mrvlGetFTPStatus
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(670)[1577]: mrvlGetFTPStatus Return Code: 0
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(36)[1577]: nasapi: lock time = 0
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(46)[1577]: calling mrvlGetVolume high all
Feb 18 00:10:30 fvdwsl-base local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/df
Feb 18 00:10:30 fvdwsl-base local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/sbin/mdadm --detail /dev/md0
Feb 18 00:10:30 fvdwsl-base local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/sbin/mdadm --detail /dev/md0
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(667)[1577]: mrvlGetVolume high all Return Code: Array():0 => Array()...
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(36)[1577]: nasapi: lock time = 0
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(46)[1577]: calling mrvlAddShare test3  private 1100 0 0 0 0 0  internal_share  active
Feb 18 00:10:30 fvdwsl-base local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/sbin/mdadm --detail /dev/md0
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] sharefunc_add_share.finc(49)[1577]: sharefunc_add_share: volume is busy
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(670)[1577]: mrvlAddShare test3  private 1100 0 0 0 0 0  internal_share  active  Return Code: 1
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(36)[1577]: nasapi: lock time = 0
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(46)[1577]: calling mrvlGetCurrentNfsStatus
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(670)[1577]: mrvlGetCurrentNfsStatus Return Code: 0
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(36)[1577]: nasapi: lock time = 0
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(46)[1577]: calling mrvlGetAFPStatus
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(667)[1577]: mrvlGetAFPStatus Return Code: Array():enable => false...
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(36)[1577]: nasapi: lock time = 0
Feb 18 00:10:30 fvdwsl-base local0.warn API[2017/02/18 00:10:30] nasapi.inc(46)[1577]: calling mrvlUpdateAFPConf
Feb 18 00:10:30 fvdwsl-base local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/ps -C afpd -o pid=
Feb 18 00:10:30 fvdwsl-base local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/ps -C cnid_metad -o pid=
Feb 18 00:10:30 fvdwsl-base local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/ps -C avahi-daemon -o pid=
Feb 18 00:10:31 fvdwsl-base local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/ps -C dbus-daemon -o pid=
Feb 18 00:10:31 fvdwsl-base local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/ps -C smbd -o pid=
Feb 18 00:10:32 fvdwsl-base local0.warn API[2017/02/18 00:10:32] nasapi.inc(670)[1577]: mrvlUpdateAFPConf Return Code: 0
Feb 18 00:10:32 fvdwsl-base local0.warn API[2017/02/18 00:10:32] nasapi.inc(36)[1577]: nasapi: lock time = 0
Feb 18 00:10:32 fvdwsl-base local0.warn API[2017/02/18 00:10:32] nasapi.inc(46)[1577]: calling mrvlGetrsyncdCurrentStatus
Feb 18 00:10:32 fvdwsl-base local0.warn API[2017/02/18 00:10:32] nasapi.inc(670)[1577]: mrvlGetrsyncdCurrentStatus Return Code:
Feb 18 00:10:32 fvdwsl-base local0.warn API[2017/02/18 00:10:32] nasapi.inc(36)[1577]: nasapi: lock time = 0
Feb 18 00:10:32 fvdwsl-base local0.warn API[2017/02/18 00:10:32] nasapi.inc(46)[1577]: calling mrvlGetWebdavCurrentStatus
Feb 18 00:10:32 fvdwsl-base local0.warn API[2017/02/18 00:10:32] nasapi.inc(670)[1577]: mrvlGetWebdavCurrentStatus Return Code: 0
Feb 18 00:10:32 fvdwsl-base local0.warn API[2017/02/18 00:10:32] nasapi.inc(36)[1577]: nasapi: lock time = 0
Feb 18 00:10:32 fvdwsl-base local0.warn API[2017/02/18 00:10:32] nasapi.inc(46)[1577]: calling mrvlGetVolume high all
Feb 18 00:10:32 fvdwsl-base local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/df
Feb 18 00:10:32 fvdwsl-base local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/sbin/mdadm --detail /dev/md0
Feb 18 00:10:32 fvdwsl-base local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/sbin/mdadm --detail /dev/md0
Feb 18 00:10:32 fvdwsl-base local0.warn API[2017/02/18 00:10:32] nasapi.inc(667)[1577]: mrvlGetVolume high all Return Code: Array():0 => Array()...
Feb 18 00:10:32 fvdwsl-base local0.warn API[2017/02/18 00:10:32] nasapi.inc(36)[1577]: nasapi: lock time = 0
Feb 18 00:10:32 fvdwsl-base local0.warn API[2017/02/18 00:10:32] nasapi.inc(46)[1577]: calling mrvlGetShareUserList new
Feb 18 00:10:32 fvdwsl-base local0.warn API[2017/02/18 00:10:32] nasapi.inc(667)[1577]: mrvlGetShareUserList new Return Code: Array():0 => Array()...
Feb 18 00:10:32 fvdwsl-base local0.warn API[2017/02/18 00:10:32] nasapi.inc(36)[1577]: nasapi: lock time = 0
Feb 18 00:10:32 fvdwsl-base local0.warn API[2017/02/18 00:10:32] nasapi.inc(46)[1577]: calling mrvlGetVolumeAddons
Feb 18 00:10:32 fvdwsl-base local0.warn API[2017/02/18 00:10:32] nasapi.inc(670)[1577]: mrvlGetVolumeAddons Return Code: 1100
Feb 18 00:10:32 fvdwsl-base local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/ps -ef
Feb 18 00:10:41 fvdwsl-base syslog.info syslogd exiting


In the /share directory I have a 1100 folder, this used to be 1000 originally I believe. What else can I check?

Thank you

[Jocko]

Hi Flurkje,

I decided to give up on the Lacie firmware and switched to the FVDW firmware (16.1) next I followed the instructions for the creation of a RAID6 volume and this is where something must have gone wrong. I have removed the sda8 partition and recreated it, causing the public share to disappear (there was no data on it)

:scratch There is no support for a raid6 with 16.1 (and we do not plan to add it) but perhaps you may say raid5

Otherwise your issue is here

Code: Select all

sharefunc_add_share.finc(49)[1577]: sharefunc_add_share: volume is busy

So that would means the raid is not clean or there is no file system on it.

So post

Code: Select all

mount
cat /proc/mdstat
file -bs /dev/md0

Note: with a raid, the mount point is 110x

[Flurkje]

Thank you for your reaction. I did configure it as RADI6 :sob, it is working I believe but I guess I will have issues in the future once the webinterface supports the RADI config?

Here is the output:

Code: Select all

root@fvdwsl-base:/dev # mount
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (rw,relatime,errors=continue,barrier=1,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,errors=continue,barrier=1,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/md0 on /share/1100 type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered)

root@fvdwsl-base:/dev # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md0 : active raid6 sda8[0] sde8[4] sdd8[3] sdc8[2] sdb8[1]
      5850679680 blocks super 1.0 level 6, 64k chunk, algorithm 2 [5/5] [UUUUU]
      [====>................]  resync = 21.4% (418638152/1950226560) finish=2658.8min speed=9600K/sec

unused devices: <none>

root@fvdwsl-base:/dev # file -bs /dev/md0
Linux rev 1.0 ext3 filesystem data, UUID=fd84799e-00e8-40b9-9bb2-0087713a4eb1 (needs journal recovery) (large files)


Perhaps I should start over completely? Just changing the RAID level will probably not be enough will it?

[Jocko]

So you did not add the option "--assume-clean" when you created the raid and so you need to wait the end of this useless synchronization on empty disks...

Why currently we do not plan to add support for raid6 is its cost :if having a redundancy with 2 disks is not a real issue with big disks, it is not the same case with R/W performance.

Indeed without a hardware raid controller and a small cpu, you have a significant impact on I/O disks (in particular write speed)

[Flurkje]

Before I give myself too much freedom again, am I allowed to configure as a RAID5 with an hot spare?

Thank you