Missing volume, dead disk.

[ipb_uk]

Hello,

Disk 6 on my RNDP6000 has been detecting increasing pending sector counts. I’ve ordered and received a new disk.

Now for some reason it reported disk 4 dead. I’ve shut it down and pulled the disks out and checked and they are OK. I’ve put them back in and turned the box back on and it reported a new disk in bay 4 (it isn’t, it’s the same disk!), which it checked and started a resync, this seems to have failed with disk 6 being reported dead. And now it says there are no volumes.

RNDP6000 - 4.2.30

What to do next?

Thanks very much.

Ipb

[vandermerwe]

I assume you were set up with xraid single redundancy or raid 5, and it also sounds like you have no backup?

If you have no backup and you need to try to retrieve the data, your best option would be to contact Netgear support and ask for data recovery, this will cost money.

It does not look good though.

[JennC]

Hello ipb_uk,

You have mentioned that you have shut down and pulled the disks out, you need to be careful when doing this as it will break the RAID causing data loss when you improperly inserted the disks and booting up the NAS. It is best to label them so you are sure you are inserting the disks back to their respective bays before starting up the NAS.

There is a possibility that there are more than one disk that had problems.

Have you checked if you were able to get to the files after you removed disk 6 and before replacing it? It does not look good like what vandermerwe said. You may need to avail data recovery service.

Welcome to the community!

Regards,

[ipb_uk]

Hello,

I’ve been here before mdgm help me out that time. I couldn’t find my login details, requested a password on my email account.

The disk are labelled 1 to 6, been there and got the t-shirt.

Yes it’s xraid single. It’s ALL backed-up on dvd’s.

I took the disks out when the system was off, tested them, then put ‘em back in and turned it on. Then a resync failed, but I could get to my files and after a reboot, no volumes.

I think I got unlucky somewhere.

If I’ve got to bite the bullet here, then I’ll have too.

Regards

Ian

[JennC]

Hello ipb_uk,

This issue you have has something to do with recovery the data already.

I don't think mgdm does data recovery.

Let's see if he has something else to suggest.

Regards,

[ipb_uk]

Helle JennC,

I was giving mgdm a name check only. As I hadn't done so here in this new forum.

The sixth disc isn't good any more. I've got a new red 6TB disk and I've tested that disc in the box on it's own and all is well with it.

If the remaining 5 discs have lost thier volume I can see I have no choice but to start again. And if so I have some more options to consider.

Many thanks & regards

Ian.

[JennC]

Hello ipb_uk,

Do you still remember what RAID level you had when all were working?

Even if the disk 6 has gone bad, you should still be able to see your files with the 5 disks inserted provided that they were not removed from the bays and moved to another bay and that you had XRAID configuration.

Regards,

[ipb_uk]

Hello JennC,

It was the default for six disks. They are all numbered so I know they have never been in the wrong bay.

I have the logs. Will they be able to confirm which raid level. If so which log?

Thanks

Ian.

[JennC]

Hello ipb_uk,

Check the reallocated sector count, see this article and ATA errors.

Regards,

[ipb_uk]

Hello JennC

Coulldn't find anything to confirm the RAID level from what those links siad to look at.

But in mdstat.log.....

Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md2 : active raid5 sda3[0] sdf3[5] sde3[4] sdd3[3] sdc3[2] sdb3[1]
9743963520 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]

md1 : active raid6 sda2[0] sdf2[5] sde2[4] sdd2[3] sdc2[2] sdb2[1]
2096896 blocks super 1.2 level 6, 64k chunk, algorithm 2 [6/6] [UUUUUU]

md0 : active raid1 sda1[0] sdf1[5] sde1[4] sdd1[3] sdc1[2] sdb1[1]
4193268 blocks super 1.2 [6/6] [UUUUUU]

unused devices: <none>

expansion.log.

Only mentions "RAID MODE: 1, sn="

Thanks

Ian

[JennC]

Hello ipb_uk,

When did you grab this logs? It seems RAID5 has been used which is not a 2 disk fault tolerance RAID. Can you check please boot_info.log's XRAIDif it has 1 or 0?

Regards,

[ipb_uk]

Hi JennC,

I have logs from 20th Oct, 15th & 16 Nov.

Boot_info.log has "xraid: 1".

Regards

Ian.

[JennC]

Hello ipb_uk,

Okay then that was configured XRAID RAID5 which has 1-disk fault tolerance only.

How's the reallocated sectors and ATA errors of the disks from the smart logs that has no date?

Regards,

[ipb_uk]

Hi JennC,

Would it be better for me to post the contents of that log from two versions of that log?

Thanks

Ian

[JennC]

Hello ipb_uk,

Just indicate which log is the latest and which one isn't.

Regards,

[ipb_uk]

Hello JennC,

Ok, I can't post the contents. It's more 20,000 characters. I didn't know about that limit.

Thanks

Ian.

[ipb_uk]

*****20161020-150540****
SMART Error Log Version: 1
ATA Error Count: 6 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 6 occurred at disk power-on lifetime: 33590 hours (1399 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 ff ff ff 4f 00 12:08:02.019 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 12:08:02.019 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 12:08:02.018 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 12:08:02.018 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 12:08:02.018 READ NATIVE MAX ADDRESS EXT
Error 5 occurred at disk power-on lifetime: 33590 hours (1399 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 ff ff ff 4f 00 12:07:58.219 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 12:07:58.219 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 12:07:58.218 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 12:07:58.218 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 12:07:58.218 READ NATIVE MAX ADDRESS EXT
Error 4 occurred at disk power-on lifetime: 33590 hours (1399 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 ff ff ff 4f 00 12:07:54.492 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 12:07:54.492 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 12:07:54.491 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 12:07:54.491 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 12:07:54.491 READ NATIVE MAX ADDRESS EXT
Error 3 occurred at disk power-on lifetime: 33590 hours (1399 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 ff ff ff 4f 00 12:07:50.691 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 12:07:50.691 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 12:07:50.690 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 12:07:50.690 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 12:07:50.690 READ NATIVE MAX ADDRESS EXT
Error 2 occurred at disk power-on lifetime: 33590 hours (1399 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 ff ff ff 4f 00 12:07:46.994 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 12:07:46.994 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 12:07:46.993 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 12:07:46.993 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 12:07:46.993 READ NATIVE MAX ADDRESS EXT

[ipb_uk]

Hi JennC

The  Reallocated_Sector_Ct on the remaining disks are in disk order....

5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0

5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0

5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0

5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0

5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0

This is from the newest logs.

Regards

Ian

[JennC]

Hello ipb_uk,

I'm sorry, send logs, please.

Regards,

[ipb_uk]

Hello JennC

That's OK. But I've sent them in via the instructions on THIS page.

Regards

Ian

[JennC]

Hello ipb_uk,

They're the same 🙂

Regards,

[ipb_uk]

Hello JennC,

Erm, what are the same?

I will try to keep up with you!

Regards

Ian

[JennC]

Hello ipb_uk,

I was referring to the link that has the instructions. However, I do not have access to it so we'll have to wait for someone here in the community that has the access.

Regards,

[ipb_uk]

Hi JennC,

Your link goes to a page that instructs me to send logs via a Support Case number, which I don't have, therefore no case reference number for me to click on.

Anyway I've had a read receipt from Hyacinthe .......for my email.

Anything else I can do to help?

Regards

Ian

[JennC]

Hello ipb_uk,

I hope you have included the link for this forum or a short description of the problem.

Regards,