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

Re: RN104 failed disk exchange issue

tonyaa
Tutor

RN104 failed disk exchange issue

Hi all!

I have a RN104 equipped with 3 HDD: 1x2TB and two 4TB. 

Few days ago, just after moving to a new apartment, I've got a messagem that volume status on my RN104 is degraded.

After logs downloading I've got informed, that one of 4TB HDD is failed. I have one data volume in X-RAID confogurarion.

I Bought a new 4TB HDD, installed them in new slot, and nothing was happened!

I've installed a new drive in new (empty) slot - nothing!

I've moved them to failed disk slot - nothing!

I've formatted them - nothing!

Trying to set them as global spare = nothing!

When I've take a failed dis off NAS, and reinstalled them (even in new slot) there is a rebiulding provided,m but volume status is still DEGRADED!

Please, give me an information what should I do to exchange a failed 4TB to a new one, to keep all my data secured - that I've bought a NAS for!  Maybe is there some kind of manual how to do it, because, in my situation I've stucked!

Thank you very much for any help in advance,

Tony.

 

Model: RN104|ReadyNAS 100 Series 4- Bay
Message 1 of 11

Accepted Solutions
Sandshark
Sensei

Re: RN104 failed disk exchange issue

Drive 2 is reporting a temperature of 0 and no SMART data.  That could indicate the drive is simply spun down, but I don't know why it would do that.  So another possibility is the drive is bad.  It is missing from your data array, as you stated.

 

Connecting the drive to a PC and testing it with SeaTools is your best next step.  If it passes, then see if there is existing partitioning.  If there is, try removing that and re-insert the drive (with power on).

View solution in original post

Message 6 of 11

All Replies
StephenB
Guru

Re: RN104 failed disk exchange issue


@tonyaa wrote:

 

I've installed a new drive in new (empty) slot - nothing!

I've moved them to failed disk slot - nothing!

 


The right method is to remove the failed drive with the NAS running, and then hot-insert the replacement.

 

Can you download the log zip file, and cut/paste mdstat.log in a reply here?

 


@tonyaa wrote:

to keep all my data secured - that I've bought a NAS for! 

 


While RAID redundancy is good, it's not enough to keep your data safe.  You should have a backup plan in place for it.

 

You might want to get a USB drive and do a backup before proceeding further.

Message 2 of 11
tonyaa
Tutor

Re: RN104 failed disk exchange issue

@stephen  I've tried to provide procedure which you described.

On working system I've pulled out defected HDD, next I've inserted a new one drive and as in previous tries, resync was not started.

The disk is "inactive" = I can not do anything with them - as you can see on attached screenshot.

 

Is there any way to "force" rebuilding X-RAID? What else can I do to add new 4TB disk instead failed one?  I am stucked!

Can you give me a path what ele can I do in that situation?

 

Regards, 

Tony

 

Model: RN104|ReadyNAS 100 Series 4- Bay
Message 3 of 11
StephenB
Guru

Re: RN104 failed disk exchange issue

Did you try selecting the disk on the volume page, and then clicking on format?  If the new drive was formatted already, the NAS won't automatically add it.

 

Another thing you might want to do is test the new disk in a Windows PC - using Lifeguard (for western digital) or Seatools (for Seagate).

 


@tonyaa wrote:

 

Can you give me a path what ele can I do in that situation?

 


Please download the log zip file, and post mdstat.log (as I requested before).  Perhaps also post disk_info.log.

 

The best way to do this is to use the </> tool in the forum toolbar.  Copy/paste the info in those logs - don't try to attach the files themselves.

Message 4 of 11
tonyaa
Tutor

Re: RN104 failed disk exchange issue

@StephenB 

mdstat file:

Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md1 : active raid1 sdc2[1] sda2[0]
523264 blocks super 1.2 [2/2] [UU]

md126 : active raid5 sdc3[0] sda3[2]
3897325568 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/2] [U_U]

md127 : active raid1 sda4[1]
1953374912 blocks super 1.2 [2/1] [_U]

md0 : active raid1 sdc1[0] sda1[2]
4190208 blocks super 1.2 [2/2] [UU]

unused devices: <none>
/dev/md/0:
Version : 1.2
Creation Time : Sun Jan 25 23:01:04 2015
Raid Level : raid1
Array Size : 4190208 (4.00 GiB 4.29 GB)
Used Dev Size : 4190208 (4.00 GiB 4.29 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent

Update Time : Thu Sep 10 17:01:15 2020
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Consistency Policy : unknown

Name : 2fe4f88e:0 (local to host 2fe4f88e)
UUID : 6b44ae06:d158cb7d:fefa7dc5:f33f05c4
Events : 2332

Number Major Minor RaidDevice State
0 8 33 0 active sync /dev/sdc1
2 8 1 1 active sync /dev/sda1
/dev/md/data-0:
Version : 1.2
Creation Time : Sun Jan 25 23:01:04 2015
Raid Level : raid5
Array Size : 3897325568 (3716.78 GiB 3990.86 GB)
Used Dev Size : 1948662784 (1858.39 GiB 1995.43 GB)
Raid Devices : 3
Total Devices : 2
Persistence : Superblock is persistent

Update Time : Thu Sep 10 17:01:17 2020
State : clean, degraded
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 64K

Consistency Policy : unknown

Name : 2fe4f88e:data-0 (local to host 2fe4f88e)
UUID : d7bede82:a9b24fec:96e80c9e:31dc3cb1
Events : 41530

Number Major Minor RaidDevice State
0 8 35 0 active sync /dev/sdc3
- 0 0 1 removed
2 8 3 2 active sync /dev/sda3
/dev/md/data-1:
Version : 1.2
Creation Time : Fri Apr 24 23:01:37 2015
Raid Level : raid1
Array Size : 1953374912 (1862.88 GiB 2000.26 GB)
Used Dev Size : 1953374912 (1862.88 GiB 2000.26 GB)
Raid Devices : 2
Total Devices : 1
Persistence : Superblock is persistent

Update Time : Thu Sep 10 16:57:33 2020
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0

Consistency Policy : unknown

Name : 2fe4f88e:data-1 (local to host 2fe4f88e)
UUID : 2403653e:f948b946:6bba6481:7e4548bd
Events : 61355

Number Major Minor RaidDevice State
- 0 0 0 removed
1 8 4 1 active sync /dev/sda4

 

 

disk_info.log  file

 

Device: sdc
Controller: 0
Channel: 0
Model: WDC WD20EURS-63S48Y0
Serial: WD-WCAZAE943509
Firmware: 51.0AB51W
Class: SATA
Sectors: 3907029168
Pool: data
PoolType: RAID 5
PoolState: 3
PoolHostId: 2fe4f88e
Health data
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 41
Start/Stop Count: 236
Power-On Hours: 50557
Power Cycle Count: 197
Load Cycle Count: 51

Device: sdb
Controller: 0
Channel: 1
Model: ST4000VN008
Serial: ZDH8PKMD
Firmware: SC60
Class: SATA
RPM: 7200
Sectors: 7814037168
Health data
ATA Error Count: 0
Temperature: 0

Device: sda
Controller: 0
Channel: 2
Model: WDC WD40EFRX-68WT0N0
Serial: WD-WCC4E0HHFP7Z
Firmware: 82.00A82W
Class: SATA
RPM: 5400
Sectors: 7814037168
Pool: data
PoolType: RAID 5
PoolState: 3
PoolHostId: 2fe4f88e
Health data
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 38
Start/Stop Count: 55
Power-On Hours: 34911
Power Cycle Count: 55
Load Cycle Count: 408

 

 

Regards,

Tony.

 

 

Model: RN104|ReadyNAS 100 Series 4- Bay
Message 5 of 11
Sandshark
Sensei

Re: RN104 failed disk exchange issue

Drive 2 is reporting a temperature of 0 and no SMART data.  That could indicate the drive is simply spun down, but I don't know why it would do that.  So another possibility is the drive is bad.  It is missing from your data array, as you stated.

 

Connecting the drive to a PC and testing it with SeaTools is your best next step.  If it passes, then see if there is existing partitioning.  If there is, try removing that and re-insert the drive (with power on).

Message 6 of 11
tonyaa
Tutor

Re: RN104 failed disk exchange issue

@Sandshark I finally inserted the drive to my PC, and examination by SeaTools gives, that HDD is defective! 

I am pretty confused - this was brand new HDD, thiat situation happened for the first time to me and I am 50 y.o. and I am using PC's since 1990's! We are still learning and finally die stupid Smiley Happy ...

I made a RMA request in Seagate and send them HDD for warranty exchange.

When I will receive a new HDD I will make procedure to hot insert them in RN104 working and I will report, if X-RAID rebuilding will take place.

 

Thank you @Sandshark and @StephenB for attention and for your priceless help!

Regards,

Tony.

Model: RN104|ReadyNAS 100 Series 4- Bay
Message 7 of 11
StephenB
Guru

Re: RN104 failed disk exchange issue


@tonyaa wrote:

 

I made a RMA request in Seagate and send them HDD for warranty exchange.

Generally it's better to exchange new disks with the seller.  When you do an RMA you get a recertified replacement, and that only has a 1 year warranty.

Message 8 of 11
tonyaa
Tutor

Re: RN104 failed disk exchange issue

@StephenB Today I've received an exchanged disk. Looks like brand new, I've checked warranty status for its S/N - is 3 years - exactly as this one I've bought.

Rebuilding process has started and I think, it will take more than whole day - I'll give feedback about results.

Regards, 

Tony.

Model: RN104|ReadyNAS 100 Series 4- Bay
Message 9 of 11
tonyaa
Tutor

Re: RN104 failed disk exchange issue

Dear all,

Today 7:30 AM thr resynchronizing process was finished and all seems to me working perfectly Smiley Happy

Thanks for everyone for your help and knowledge!

 

Regards, 

Tony.

Model: RN104|ReadyNAS 100 Series 4- Bay
Message 10 of 11
StephenB
Guru

Re: RN104 failed disk exchange issue


@tonyaa wrote:

Today 7:30 AM thr resynchronizing process was finished and all seems to me working perfectly Smiley Happy

 


Great new, thx for sharing.

Message 11 of 11
Top Contributors
Discussion stats
  • 10 replies
  • 2016 views
  • 2 kudos
  • 3 in conversation
Announcements