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

Can't find path for shares

kristianherlufs
Aspirant

Can't find path for shares

Hi Everyone

I've had my ReadyNAS Duo v2 for four months now, and everything has worked perfectly until now. But after I disconnected and connected the power to my NAS yesterday I can no longer gain acces to the shares.

The log gives following information:

Sat Jan 5 19:12:47 PST 2013System is up.
Sat Jan 5 19:12:46 PST 2013The 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
Sat Jan 5 19:11:57 PST 2013Volume scan failed to run properly

I've tried to upgrade the firmware, but that did not work.

I can see the NAS on the network and have no problem connecting to the NAS using https://192.168.1.109/admin/index.html

I've not changed any settings from during the time the NAS worked and until now.

What to do next?

/Kristian
Message 1 of 4
evan2
NETGEAR Expert

Re: Can't find path for shares

Maybe the partition's table lost when you disconnected power directly.
Could you send logs follow below steps?
http://www.readynas.com/kb/faq/misc/how ... d_all_logs
Message 2 of 4
kristianherlufs
Aspirant

Re: Can't find path for shares

Done!
Message 3 of 4
evan2
NETGEAR Expert

Re: Can't find path for shares

I see your logs, the device's partition table lost, please contact technical support, let them remote control your device to recover the partition table.

Disk /dev/sda doesn't contain a valid partition table

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1 doesn't contain a valid partition table

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
256 heads, 63 sectors/track, 121126 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdb1 1 1953525167 976762583+ ee GPT

Disk /dev/md0: 4293 MB, 4293906432 bytes
2 heads, 4 sectors/track, 1048317 cylinders, total 8386536 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/md1: 536 MB, 536858624 bytes
2 heads, 4 sectors/track, 131069 cylinders, total 1048552 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Message 4 of 4
Top Contributors
Discussion stats
  • 3 replies
  • 1269 views
  • 0 kudos
  • 2 in conversation
Announcements