× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Re: The paths for the shares listed not found - #25044991

Hibtek
Aspirant

The paths for the shares listed not found - #25044991

Hi,

Got the dreaded "The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume"

Was upgrading one of my 1.5TB disks to a 2TB disk, went to my webpage of what I though was my second NAS, same Make/Model, and restarted it due to an addon update pending, yep, you guessed it, the monkey had restarted the NAS which I just added the disk to.......

any hoo, from the downloaded logs I can now see this

From the logs I downloaded I can see this volume.txt

===== pvscan =====
Couldn't find device with uuid 'EzWjdT-RI2n-92LA-ZJzm-iPDO-Mble-ViYDxA'.
Couldn't find device with uuid 'EzWjdT-RI2n-92LA-ZJzm-iPDO-Mble-ViYDxA'.
PV /dev/md2 VG c lvm2 [5.44 TB / 0 free]
PV unknown device VG c lvm2 [1.36 TB / 0 free]
Total: 2 [2.80 TB] / in use: 2 [2.80 TB] / in no VG: 0 [0 ]
===== vgscan =====
Couldn't find device with uuid 'EzWjdT-RI2n-92LA-ZJzm-iPDO-Mble-ViYDxA'.
Couldn't find all physical volumes for volume group c.
Couldn't find device with uuid 'EzWjdT-RI2n-92LA-ZJzm-iPDO-Mble-ViYDxA'.
Couldn't find all physical volumes for volume group c.
Volume group "c" not found
Reading all physical volumes. This may take a while...
===== lvscan =====
Couldn't find device with uuid 'EzWjdT-RI2n-92LA-ZJzm-iPDO-Mble-ViYDxA'.
Couldn't find all physical volumes for volume group c.
Couldn't find device with uuid 'EzWjdT-RI2n-92LA-ZJzm-iPDO-Mble-ViYDxA'.
Couldn't find all physical volumes for volume group c.
Volume group "c" not found
===== vgdisplay =====
Couldn't find device with uuid 'EzWjdT-RI2n-92LA-ZJzm-iPDO-Mble-ViYDxA'.
Couldn't find all physical volumes for volume group c.
Couldn't find device with uuid 'EzWjdT-RI2n-92LA-ZJzm-iPDO-Mble-ViYDxA'.
Couldn't find all physical volumes for volume group c.
Volume group "c" not found


and this is from mounts.txt

/dev/md0 on / type ext2 (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)
nfsd on /proc/fs/nfsd type nfsd (rw

The disk continued to rebuild, and has now completed ok

A Netgear Support person has got back to me and said everything is ok, I did not word the question right so that my fault and he answered what I had put correctly :-), but it was a quick response so am not complaining 🙂

I had this before on a different Netgear 6 Bay NAS, and support were able to fix the issue in about 10 minutes 🙂 so Im hoping they can repeat the super performance 🙂

As I had to go to work I have left the NAS in Tech Support mode and added the code to my support case

Anyway, Though some of you might have a giggle at what I did.

But apart from learning to tell the difference between a ReadyNAS 6 Pro and a ReadyNAS 6 Pro (the two models in question) im going to continue to cry in the corner of the office until I go home to look at a poorly NAS 😞
Message 1 of 6
mdgm-ntgr
NETGEAR Employee Retired

Re: The paths for the shares listed not found - #25044991

I assume you have no backup?

Whilst reboots during resyncs are generally handled fine it's not something we would recommend. A contract purchase would be required to look into this issue.
Message 2 of 6
Hibtek
Aspirant

Re: The paths for the shares listed not found - #25044991

Hi,

No recent backups but Netgear fixed this issue when it happened before, from the Engineer getting connected to the fix was like 10 minutes last time 🙂

I'm more worried of it happening again as its not the first time this happened, last time it was a different NAS but the same thing, removed an old disk, waited for it to report a disk removal, then added the disk, this was a few weeks after I got it so I was still in test mode and had only copied test data to it,

My Other Netgear ReadyNAS Pro, I added a disk to, just after it started reshaping, the webpage died (error 500 bad request), so I ran a command which resets the http, and the webpage now loads, just after it completed the resync, or at 99.7% disk 1 is reporting as dead........ but if the webpage http thing still continues I will do an OS reinstall

so far its not going well 🙂 oh well
Message 3 of 6
Hibtek
Aspirant

Re: The paths for the shares listed not found - #25044991

Well, its an interesting day, my other NAS which held most of the copies of the first NAS has just had the same failure as the first!.

How bizzare is that!

volume.txt

===== pvscan =====
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'ovwebg-8GPr-0tky-ObYc-gkwV-mYLN-fDeL5B'.
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'ovwebg-8GPr-0tky-ObYc-gkwV-mYLN-fDeL5B'.
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'ovwebg-8GPr-0tky-ObYc-gkwV-mYLN-fDeL5B'.
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'ovwebg-8GPr-0tky-ObYc-gkwV-mYLN-fDeL5B'.
PV /dev/md2 VG c lvm2 [1.34 TB / 0 free]
PV unknown device VG c lvm2 [5.46 TB / 10.00 GB free]
PV /dev/md4 VG c lvm2 [1.82 TB / 0 free]
Total: 3 [4.62 TB] / in use: 3 [4.62 TB] / in no VG: 0 [0 ]
===== vgscan =====
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'ovwebg-8GPr-0tky-ObYc-gkwV-mYLN-fDeL5B'.
Couldn't find all physical volumes for volume group c.
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'ovwebg-8GPr-0tky-ObYc-gkwV-mYLN-fDeL5B'.
Couldn't find all physical volumes for volume group c.
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'ovwebg-8GPr-0tky-ObYc-gkwV-mYLN-fDeL5B'.
Couldn't find all physical volumes for volume group c.
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'ovwebg-8GPr-0tky-ObYc-gkwV-mYLN-fDeL5B'.
Couldn't find all physical volumes for volume group c.
Volume group "c" not found
Reading all physical volumes. This may take a while...
===== lvscan =====
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'ovwebg-8GPr-0tky-ObYc-gkwV-mYLN-fDeL5B'.
Couldn't find all physical volumes for volume group c.
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'ovwebg-8GPr-0tky-ObYc-gkwV-mYLN-fDeL5B'.
Couldn't find all physical volumes for volume group c.
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'ovwebg-8GPr-0tky-ObYc-gkwV-mYLN-fDeL5B'.
Couldn't find all physical volumes for volume group c.
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'ovwebg-8GPr-0tky-ObYc-gkwV-mYLN-fDeL5B'.
Couldn't find all physical volumes for volume group c.
Volume group "c" not found
===== vgdisplay =====
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'ovwebg-8GPr-0tky-ObYc-gkwV-mYLN-fDeL5B'.
Couldn't find all physical volumes for volume group c.
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'ovwebg-8GPr-0tky-ObYc-gkwV-mYLN-fDeL5B'.
Couldn't find all physical volumes for volume group c.
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'ovwebg-8GPr-0tky-ObYc-gkwV-mYLN-fDeL5B'.
Couldn't find all physical volumes for volume group c.
/dev/md3: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'ovwebg-8GPr-0tky-ObYc-gkwV-mYLN-fDeL5B'.
Couldn't find all physical volumes for volume group c.
Volume group "c" not found
===== fstab =====
#-----------------------------------------------------------------------------
# <device> <mount> <type> <options> <freq> <pass>
#-----------------------------------------------------------------------------
/dev/md0 / ext2 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 0 2

I'm trying to copy off what I can, but so far out of the 4TB its just copying folders, and can not read any files 😞

Oh well

Factory reset time me thinks
Message 4 of 6
mdgm-ntgr
NETGEAR Employee Retired

Re: The paths for the shares listed not found - #25044991

In my opinion your Ultra 6 Plus has the array in worse condition. I/O errors are always a bad sign.

One of the disks is marked as spare and another as failed. X-RAID single-redundancy can only handle a single disk failure.

You may wish to power down, remove your disks (label order) and test your SeaGate disks using SeaTools and your WD disks using the WD Data LifeGuard Diagnostic Tool.

I recommend X-RAID2 dual-redundancy or Flex-RAID RAID-6.

In both of your systems you have some disks outside the compatibility list.
Message 5 of 6
Hibtek
Aspirant

Re: The paths for the shares listed not found - #25044991

Thanks for the reply, yes they have always been disks outside, they have always worked ok, its still strange that 3 disk failures happen in two days on the same NAS, I have tested the disks on a USB caddy on my PC, the short and long test all pass ok, but I guess that's the down side of disks outside the compat list, if the NAS don't like em, then its a risk

Do you know of anyway I can try to recover the data, Netgear support have offered a Short Service contract, (forgot the wording) but its about £60 to look at it, which does not seem to bad, just trying to get a few more details from them first

The Ultra 6 Plus is over 3 years old!, wow! only just, but its over it

Given that the volume is corrupt, would Dual redundancy of helped this or are you just recommending Dual Redundancy in general?

Thanks Again

Chris
Message 6 of 6
Top Contributors
Discussion stats
  • 5 replies
  • 3065 views
  • 0 kudos
  • 2 in conversation
Announcements