NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
vaprasad
Feb 18, 2013Aspirant
"ReadyNAS is unable to access the data volume. media backup"
ReadyNAS Pro 6 system running fine for about a year now (since Feb 2012) with 6 WD1002FBYS-0 drives.
Running Radiator 4.2.22 since December 2012.
Sat Feb 9 received the following yellow alert: "The on-line filesystem consistency check detected problems with your data volume. Please reboot the system with the volume scan checkbox enabled to do a full filesystem consistency check and repair." I take yellow alert to mean a warning.
Sunday Feb 17, Performed a reboot with the "volume scan checkbox enabled" and started receiving the green alert: "The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. media backup" message. I take green alert to mean non-critical.
I used a search engine to see what others have done with this message.
In one case, a ReadyNAS user in NZ had to have ReadyNAS support "unlock" his drives because they somehow locked:
http://www.geekzone.co.nz/forums.asp?forumid=66&topicid=107084
In another case, the user had deleted the shares intentionally but started to receive the message:
http://www.readynas.com/forum/viewtopic.php?f=23&t=24846
Solution was to use ewok's add-on http://www.readynas.com/contributed/ewok/CreateMissingSharePaths_0.2.bin
In another case, the user's superblock copies were destroyed sometime after a single-disk upgrade:
http://www.readynas.com/forum/viewtopic.php?f=20&t=67688
And in another case, an attempt to change permissions caused the issue:
http://www.readynas.com/forum/viewtopic.php?f=23&t=48514
I don't fit into any of those categories (at least I don't think so-- using WD drives, not Seagate; didn't delete any shares; didn't upgrade any disks; didn't try to change permissions). And that CreateMissingSharePaths_0.2.bin seems to be for the SPARC based ReadyNAS devices, so I won't be able to use it.
The only Sharing that I'm using is CIFS. If I disable CIFS, the error does not appear on reboot. If I enable CIFS the error recurs.
I do not have anything showing in /c/lost+found
I do not see any obvious errors in dmesg.
I do not see any errors in /var/log/samba.
My backup and media shares seem fine-- I can see them and access them from other devices without issue.
Is there anything specific I should be looking / grepping for?
Is the log message intended to be tagged green (ie non-critical)?
Thanks in advance!
Running Radiator 4.2.22 since December 2012.
Sat Feb 9 received the following yellow alert: "The on-line filesystem consistency check detected problems with your data volume. Please reboot the system with the volume scan checkbox enabled to do a full filesystem consistency check and repair." I take yellow alert to mean a warning.
Sunday Feb 17, Performed a reboot with the "volume scan checkbox enabled" and started receiving the green alert: "The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. media backup" message. I take green alert to mean non-critical.
I used a search engine to see what others have done with this message.
In one case, a ReadyNAS user in NZ had to have ReadyNAS support "unlock" his drives because they somehow locked:
http://www.geekzone.co.nz/forums.asp?forumid=66&topicid=107084
In another case, the user had deleted the shares intentionally but started to receive the message:
http://www.readynas.com/forum/viewtopic.php?f=23&t=24846
Solution was to use ewok's add-on http://www.readynas.com/contributed/ewok/CreateMissingSharePaths_0.2.bin
In another case, the user's superblock copies were destroyed sometime after a single-disk upgrade:
http://www.readynas.com/forum/viewtopic.php?f=20&t=67688
And in another case, an attempt to change permissions caused the issue:
http://www.readynas.com/forum/viewtopic.php?f=23&t=48514
I don't fit into any of those categories (at least I don't think so-- using WD drives, not Seagate; didn't delete any shares; didn't upgrade any disks; didn't try to change permissions). And that CreateMissingSharePaths_0.2.bin seems to be for the SPARC based ReadyNAS devices, so I won't be able to use it.
The only Sharing that I'm using is CIFS. If I disable CIFS, the error does not appear on reboot. If I enable CIFS the error recurs.
I do not have anything showing in /c/lost+found
I do not see any obvious errors in dmesg.
I do not see any errors in /var/log/samba.
My backup and media shares seem fine-- I can see them and access them from other devices without issue.
Is there anything specific I should be looking / grepping for?
Is the log message intended to be tagged green (ie non-critical)?
Thanks in advance!
readynaspro6:/var/log/samba# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md2 : active raid5 sda3[0] sdf3[5] sde3[4] sdd3[3] sdc3[2] sdb3[1]
4860203520 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
md1 : active raid6 sda2[0] sdf2[5] sde2[4] sdd2[3] sdc2[2] sdb2[1]
2096896 blocks super 1.2 level 6, 64k chunk, algorithm 2 [6/6] [UUUUUU]
md0 : active raid1 sda1[0] sdf1[5] sde1[4] sdd1[3] sdc1[2] sdb1[1]
4193268 blocks super 1.2 [6/6] [UUUUUU]
unused devices: <none>
readynaspro6:/var/log/samba# cd /
readynaspro6:/# mdadm -E -s;
ARRAY /dev/md/0 metadata=1.2 UUID=a8fa1b4a:6a19b3e3:2158bd43:9985af81 name=001F33EAF8E1:0
ARRAY /dev/md/1 metadata=1.2 UUID=0ec930b1:8ed99020:3fa480d7:4708ca43 name=001F33EAF8E1:1
ARRAY /dev/md/2 metadata=1.2 UUID=367bcbd8:bdf93bf2:7b13c94f:169c9e08 name=001F33EAF8E1:2
echo DEVICE partitions > /etc/mdadm.conf
readynaspro6:/# ls /etc/mdadm.conf
/etc/mdadm.conf
readynaspro6:/# mdadm -E -s >> /etc/mdadm.conf
readynaspro6:/# cat /etc/mdadm.conf
DEVICE partitions
ARRAY /dev/md/0 metadata=1.2 UUID=a8fa1b4a:6a19b3e3:2158bd43:9985af81 name=001F33EAF8E1:0
ARRAY /dev/md/1 metadata=1.2 UUID=0ec930b1:8ed99020:3fa480d7:4708ca43 name=001F33EAF8E1:1
ARRAY /dev/md/2 metadata=1.2 UUID=367bcbd8:bdf93bf2:7b13c94f:169c9e08 name=001F33EAF8E1:2
readynaspro6:/# mdadm --assemble --scan
mdadm: No arrays found in config file or automatically
readynaspro6:/# mdadm -E -s
ARRAY /dev/md/0 metadata=1.2 UUID=a8fa1b4a:6a19b3e3:2158bd43:9985af81 name=001F33EAF8E1:0
ARRAY /dev/md/1 metadata=1.2 UUID=0ec930b1:8ed99020:3fa480d7:4708ca43 name=001F33EAF8E1:1
ARRAY /dev/md/2 metadata=1.2 UUID=367bcbd8:bdf93bf2:7b13c94f:169c9e08 name=001F33EAF8E1:2
readynaspro6:/# mdadm --assemble --scan
mdadm: No arrays found in config file or automatically
readynaspro6:/# mdadm -Q --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Fri Jun 8 19:21:22 2012
Raid Level : raid1
Array Size : 4193268 (4.00 GiB 4.29 GB)
Used Dev Size : 4193268 (4.00 GiB 4.29 GB)
Raid Devices : 6
Total Devices : 6
Persistence : Superblock is persistent
Update Time : Mon Feb 18 11:21:36 2013
State : clean
Active Devices : 6
Working Devices : 6
Failed Devices : 0
Spare Devices : 0
Name : 001F33EAF8E1:0
UUID : a8fa1b4a:6a19b3e3:2158bd43:9985af81
Events : 21
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
2 8 33 2 active sync /dev/sdc1
3 8 49 3 active sync /dev/sdd1
4 8 65 4 active sync /dev/sde1
5 8 81 5 active sync /dev/sdf1
readynaspro6:/# mdadm -Q --detail /dev/md1
/dev/md1:
Version : 1.2
Creation Time : Fri Jun 8 19:21:22 2012
Raid Level : raid6
Array Size : 2096896 (2048.09 MiB 2147.22 MB)
Used Dev Size : 524224 (512.02 MiB 536.81 MB)
Raid Devices : 6
Total Devices : 6
Persistence : Superblock is persistent
Update Time : Mon Feb 18 10:20:06 2013
State : clean
Active Devices : 6
Working Devices : 6
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
Name : 001F33EAF8E1:1
UUID : 0ec930b1:8ed99020:3fa480d7:4708ca43
Events : 19
Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 8 18 1 active sync /dev/sdb2
2 8 34 2 active sync /dev/sdc2
3 8 50 3 active sync /dev/sdd2
4 8 66 4 active sync /dev/sde2
5 8 82 5 active sync /dev/sdf2
readynaspro6:/# mdadm -Q --detail /dev/md2
/dev/md2:
Version : 1.2
Creation Time : Fri Jun 8 19:21:22 2012
Raid Level : raid5
Array Size : 4860203520 (4635.05 GiB 4976.85 GB)
Used Dev Size : 972040704 (927.01 GiB 995.37 GB)
Raid Devices : 6
Total Devices : 6
Persistence : Superblock is persistent
Update Time : Mon Feb 18 10:24:36 2013
State : clean
Active Devices : 6
Working Devices : 6
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
Name : 001F33EAF8E1:2
UUID : 367bcbd8:bdf93bf2:7b13c94f:169c9e08
Events : 180
Number Major Minor RaidDevice State
0 8 3 0 active sync /dev/sda3
1 8 19 1 active sync /dev/sdb3
2 8 35 2 active sync /dev/sdc3
3 8 51 3 active sync /dev/sdd3
4 8 67 4 active sync /dev/sde3
5 8 83 5 active sync /dev/sdf3
readynaspro6:/# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md2 : active raid5 sda3[0] sdf3[5] sde3[4] sdd3[3] sdc3[2] sdb3[1]
4860203520 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
md1 : active raid6 sda2[0] sdf2[5] sde2[4] sdd2[3] sdc2[2] sdb2[1]
2096896 blocks super 1.2 level 6, 64k chunk, algorithm 2 [6/6] [UUUUUU]
md0 : active raid1 sda1[0] sdf1[5] sde1[4] sdd1[3] sdc1[2] sdb1[1]
4193268 blocks super 1.2 [6/6] [UUUUUU]
unused devices: <none>
readynaspro6:/# pvscan
PV /dev/md2 VG c lvm2 [4.53 TB / 10.00 GB free]
Total: 1 [539.00 GB] / in use: 1 [539.00 GB] / in no VG: 0 [0 ]
vgscan
Reading all physical volumes. This may take a while...
Found volume group "c" using metadata type lvm2
readynaspro6:/#
readynaspro6:/#
readynaspro6:/# vgchange -ay c
1 logical volume(s) in volume group "c" now active
readynaspro6:/# e2fsck /dev/c/c -n
e2fsck 1.42.3 (14-May-2012)
Warning! /dev/c/c is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/c/c: clean, 135862/75776000 files, 153366765/1212416000 blocks
readynaspro6:/#
4 Replies
Replies have been turned off for this discussion
- StephenBGuru - Experienced User
What shares did it list? Can you access them? Does there appear to be any data loss?vaprasad wrote: ...Sunday Feb 17, Performed a reboot with the "volume scan checkbox enabled" and started receiving the green alert: "The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. media backup" message. I take green alert to mean non-critical... - vaprasadAspirantIt lists "media" and "backup".
My backup and media shares seem fine-- I can see them and access them from other devices without issue.
There does not appear to be any data loss as far as I can tell. Is there a log file I can use to verify for sure? - vaprasadAspirantJust observed the following and not sure what to make of it-- there seems to be a couple block devices with the date from the other day listed:
readynaspro6:/etc# mount
/dev/md0 on / type ext3 (rw,noatime,nodiratime)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw)
tmpfs on /ramfs type ramfs (rw)
tmpfs on /USB type tmpfs (rw,size=16k)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/mapper/c-c on /c type ext4 (rw,noatime,nodiratime,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1,data=journal)
no idea what this is or why it's mounted read-only-->/dev/mapper/c-c_2013_02_18_11_53 on /c_2013_02_18_11_53 type ext4 (ro,noatime,acl,user_xattr)
readynaspro6:/etc# cat /etc/fstab
#-----------------------------------------------------------------------------
# <device> <mount> <type> <options> <freq> <pass>
#-----------------------------------------------------------------------------
/dev/md0 / ext3 defaults,noatime,nodiratime 0 0
proc /proc proc defaults 0 0
/dev/md1 swap swap defaults 0 0
/dev/c/c /c ext4 defaults,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1,noatime,nodiratime,data=journal 0 2
same here--> /dev/c/c_2013_02_18_11_53 /c_2013_02_18_11_53 ext4 defaults,ro,acl,user_xattr,noatime 0 0
readynaspro6:/etc# ls -ali /dev/mapper
total 0
2152 drwxr-xr-x 2 root root 140 2013-02-18 11:53 .
1074 drwxr-xr-x 18 root root 5100 2013-02-18 11:53 ..
3676 brw-rw---- 1 root disk 253, 0 2013-02-18 11:31 c-c
12631 b--------- 1 root root 253, 3 2013-02-18 11:53 c-c_2013_02_18_11_53
12630 b--------- 1 root root 253, 2 2013-02-18 11:53 c-c_2013_02_18_11_53-cow
12629 b--------- 1 root root 253, 1 2013-02-18 11:53 c-c-real
2153 crw-rw---- 1 root root 10, 236 2013-02-18 11:31 control - vaprasadAspirantFound the following thread / case 18587457 which seems to indicate it's a snapshot:
http://www.readynas.com/forum/viewtopic.php?t=63292
I did indeed manually create that snapshot.
So back to the original issue, I'm still receiving the green alert "The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. media backup"-- and to correct my initial post, it still occurs even after stopping the sharing/streaming services and doing a reboot. This log item is coming from the RAIDiator service and showing up /var/log/syslog and /var/log/user.logvaprasad wrote: Just observed the following and not sure what to make of it-- there seems to be a couple block devices with the date from the other day listed: readynaspro6:/etc# mount
/dev/md0 on / type ext3 (rw,noatime,nodiratime)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw)
tmpfs on /ramfs type ramfs (rw)
tmpfs on /USB type tmpfs (rw,size=16k)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/mapper/c-c on /c type ext4 (rw,noatime,nodiratime,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1,data=journal)
no idea what this is or why it's mounted read-only-->/dev/mapper/c-c_2013_02_18_11_53 on /c_2013_02_18_11_53 type ext4 (ro,noatime,acl,user_xattr)
readynaspro6:/etc# cat /etc/fstab
#-----------------------------------------------------------------------------
# <device> <mount> <type> <options> <freq> <pass>
#-----------------------------------------------------------------------------
/dev/md0 / ext3 defaults,noatime,nodiratime 0 0
proc /proc proc defaults 0 0
/dev/md1 swap swap defaults 0 0
/dev/c/c /c ext4 defaults,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1,noatime,nodiratime,data=journal 0 2
same here--> /dev/c/c_2013_02_18_11_53 /c_2013_02_18_11_53 ext4 defaults,ro,acl,user_xattr,noatime 0 0
readynaspro6:/etc# ls -ali /dev/mapper
total 0
2152 drwxr-xr-x 2 root root 140 2013-02-18 11:53 .
1074 drwxr-xr-x 18 root root 5100 2013-02-18 11:53 ..
3676 brw-rw---- 1 root disk 253, 0 2013-02-18 11:31 c-c
12631 b--------- 1 root root 253, 3 2013-02-18 11:53 c-c_2013_02_18_11_53
12630 b--------- 1 root root 253, 2 2013-02-18 11:53 c-c_2013_02_18_11_53-cow
12629 b--------- 1 root root 253, 1 2013-02-18 11:53 c-c-real
2153 crw-rw---- 1 root root 10, 236 2013-02-18 11:31 control
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!