NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
LeeLogan
Jul 14, 2017Aspirant
ReadyNAS 3138 Drives not recognized
I am having an issue with my drives being recognized.
I recently received a replacemnet RN3138 due to my old chassis being deffective. The old chassis would boot up and work for a few days. (2-7 days)
I contacted Tech Support and gave them logs. They decided that I needed a new chassig so I was sent a new chassis (with RMA). In the RMA instrcutions I was told to keep the drives and just return the chassis. When the new chassis showed up I swapped the drives 1 for 1 into the new chassis. When I run the setup with Raidar it finds the new NAS and the first thing it tells me is that the drive are dirty and I will have to reformat them. I cannot do this since it has all of my data on those drives. Yes I did not back up the data first. My stupidity. Well I figured my alternative is put the drives back into the old chassis. I am getting the same issue.
My question is this. Can I using the new chassis or the old chassis find a way to get to my data?
Any advice would be great. I did not have a support contract and Netgear has closed my ticket and I have passed my 90 day complimentary support.
Thanks.
Lee Logan
Just wanted to follow up to let all who responded that my issue is fixed. Looks like I had a corrupted NAS OS. The technician successfully brought back my OS and in turn all of my data that was on the NAS is now accessible. Thanks for all that responded.
11 Replies
Replies have been turned off for this discussion
- jak0lantashMentor
LeeLogan wrote:Any advice would be great. I did not have a support contract and Netgear has closed my ticket and I have passed my 90 day complimentary support.
Imo, they should help you with that issue as you're facing it when booting up the replacement chassis.
LeeLogan wrote:I am having an issue with my drives being recognized.
I recently received a replacemnet RN3138 due to my old chassis being deffective. The old chassis would boot up and work for a few days. (2-7 days)
I contacted Tech Support and gave them logs. They decided that I needed a new chassig so I was sent a new chassis (with RMA).
Did they tell you what they identified as defective?
If you want me to take a look, download the logs from the GUI, look for md127 in dmesg.log and paste an extract here.
- LeeLoganAspirant
I did submit a request and am waiting for a response. I was going to give them until Monday and then call them up and talk to someone on the phone.
- Marty_MNETGEAR Employee Retired
Hello LeeLogan,
You may try to setup the replacement chassis using a spare drive after successfully doing so you may migrate the drives 1 for 1 and check if it will address the concern. If both NAS old and replacement chassis is detecting the drives as dirty drives, then there is a possibility that the problem might be on hard drives. Upon contacting support you might be ask to avail support contract and worst case scenario it may fail to data recovery.
Regards,
Marty_M
NETGEAR Community Team
- LeeLoganAspirant
Here is the output from dmesg that have md127 in them.
[Fri Jun 23 12:15:49 2017] md: md127 stopped.
[Fri Jun 23 12:15:49 2017] md: bind<sdb3>
[Fri Jun 23 12:15:49 2017] md: bind<sdc3>
[Fri Jun 23 12:15:49 2017] md: bind<sdd3>
[Fri Jun 23 12:15:49 2017] md: bind<sda3>
[Fri Jun 23 12:15:49 2017] md/raid:md127: device sda3 operational as raid disk 0
[Fri Jun 23 12:15:49 2017] md/raid:md127: device sdd3 operational as raid disk 3
[Fri Jun 23 12:15:49 2017] md/raid:md127: device sdc3 operational as raid disk 2
[Fri Jun 23 12:15:49 2017] md/raid:md127: device sdb3 operational as raid disk 1
[Fri Jun 23 12:15:49 2017] md/raid:md127: allocated 4362kB
[Fri Jun 23 12:15:49 2017] md/raid:md127: raid level 5 active with 4 out of 4 devices, algorithm 2
[Fri Jun 23 12:15:49 2017] RAID conf printout:
[Fri Jun 23 12:15:49 2017] --- level:5 rd:4 wd:4
[Fri Jun 23 12:15:49 2017] disk 0, o:1, dev:sda3
[Fri Jun 23 12:15:49 2017] disk 1, o:1, dev:sdb3
[Fri Jun 23 12:15:49 2017] disk 2, o:1, dev:sdc3
[Fri Jun 23 12:15:49 2017] disk 3, o:1, dev:sdd3
[Fri Jun 23 12:15:49 2017] md127: detected capacity change from 0 to 11987456360448Thanks.
- jak0lantashMentorAny mention of md126? BTRFS error?
Your extract looks OK.- LeeLoganAspirant
Here are the mention of BTRFS
[llogan04.PJSEN1WK2DJXQ22] ➤ grep BTRFS dmesgfromNAS.txt
[Fri Jun 23 12:15:48 2017] BTRFS: device label 2fe6ba82:root devid 1 transid 34659 /dev/md0
[Fri Jun 23 12:15:48 2017] BTRFS info (device md0): has skinny extents
[Fri Jun 23 12:15:49 2017] BTRFS: device label 2fe6ba82:data devid 1 transid 3169 /dev/md127
[Fri Jun 23 12:15:49 2017] BTRFS info (device md127): has skinny extents - Marty_MNETGEAR Employee Retired
Hello LeeLogan,
You just receive the replacement I believe you are entitled for support. It appears the issue you have described requires assistance from the engineers and/or higher tier who can remote in to the NAS and fix this from the backend. It shows on your records that you still have support warranty, I suggest contacting support center and can get one of the engineers take a look at it.
Regards,
Marty_M
NETGEAR Community Team- LeeLoganAspirant
OK, Thanks.
I guess I will have to call them. Tried through the web portal with not much success.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!