NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RAID 6 inaccessible after hdd upgrade
Hello,
I had 4 seagate 3TB drives on my ReadyNAS 104 firmware 6.7.4, using RAID 6. One of them went bad, so I exchanged it for a seagate 4TB drive. After a few days resyncing, it finished without errors. Later I had to buy an hdd for another purpose so I decided to buy another 4TB drive for the readynas and use one of the 3TB ones for this other purpose. This way I would have 2x1TB spare and could create another volume.
I did a hot swap: removed the 3TB drive, waited for the removal recognition, and then inserted the new 4TB drive. As in the last time, it started resyncing. When it was about 40%, my 1-year old son turned the readynas off. I turned it on again and it resumed resyncing, but all my shares became inaccessible and the admin page showed all the drives red.
The resyncing process just finished and the drives remain red. I'm attaching a picture, it shows my RAID-6 volume and another unknown volume that I don't know what is. When I put the mouse over my RAID 6 volume, a popup appears saying "Remove inactive volumes to use the disk. Disk #1,2,3,4". This is also shown as those yellow messages that appear in any screen.
How can I recover my data properly?
Thanks in advance.
sectoid wrote:I tried using SSH to create a dmesg log myself but I couldn't because I got the error "dmesg: write failed: No space left on device"!! My HDDs have plenty of space but of course it's referring to the internal space of the NAS.
It's not referring to the Flash card but to the OS volume created on the HDDs.
You see, there are three volumes created on the HDDs, the OS, the swap and the data (multiple pieces for data in certain cases).
If it tells you that there is no space left when trying to extract the logs, that would mean that the OS volume is full. Sometimes, this prevents the data volume from being mounted.
Can you check with df -h if md0 is full?
If it is, follow these steps: https://community.netgear.com/t5/Using-your-ReadyNAS/RN314-FW-6-7-1-root-partition-full-how-to-fix/m-p/1284659/highlight/true#M130056
13 Replies
Replies have been turned off for this discussion
I can't see the screenshot as it wasn't approved yet.
Download the logs from the GUI, search for md127 in dmesg.log and paste an extract here.
Maybe you want to upvote this "idea" as well: https://community.netgear.com/t5/Idea-Exchange-for-ReadyNAS/Change-the-incredibly-confusing-error-message-quot-remove/idi-p/1271658
Thanks for the reply! I can't download the logs, I get the following error:
<xs:nml xmlns:xs="http://www.netgear.com/protocol/transaction/NMLSchema-0.9" src="browser" dst="nas" locale="en-us"></xs:nml>I've upvoted the idea, of course! I suspected right off the bat that I shouldn't do what it was suggesting and that's why I came here...The NAS is generating a lot of logs, I'm attaching an screenshot of it.
I tried using SSH to create a dmesg log myself but I couldn't because I got the error "dmesg: write failed: No space left on device"!! My HDDs have plenty of space but of course it's referring to the internal space of the NAS. How could this happen? I have only one app in use, Transmission, but my use of it is very light, occasional. I also use the amazon drive synchronization.
So here's the output of dmesg which I got by hand using SSH:
https://www.dropbox.com/s/6r0swgcexehunok/readynas104-dmesg.log?dl=0
Thank you very much for your help!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
