NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Disk shows Dead. Volume shows fine.
I have X-Raid with dual redundancy configured. A disk failed on me and I went to pull out the bad drive. Stupid me for not checking, but I pulled out disk 6 when disk 4 was the dead drive. I was n...
There's no important data on the swap partition. That's just used for temporarily storing what's normally stored in RAM if the RAM doesn't have sufficient space.
So you can safely do what the error message suggested:
# mdadm --zero-superblock /dev/sdf2
then
# mdadm --manage /dev/md1 --add /dev/sdf2
If sdf2 is marked as a spare in md1 (you can tell this by checking the output of # cat /proc /mdstat ) you can force it to be used properly by doing e.g.
# mdadm --grow /dev/md1 -n6
Yes. I have tried different web browsers, computers, etc. Doesn't appear to be a cache issue.
I have restarted the system twice and still has the same status.
Do you have a backup of the data?
I have a backup of all the data that is critical. The rest can be re-imported, but it would be a pain.
Have you downloaded the logs and checked those?
I have poked around, but don't know exactly what I am looking at. Here are a couple things. Any suggestions as to what to look for?
enclosure.log
temp!!1!!status=ok::descr=50.0C/122.0F::expected=0-65C/32-149F temp!!2!!status=ok::descr=30.0C/86.0F::expected=0-60C/32-140F fan!!2!!status=ok::descr=924RPM::type=SYS1 ups!!1!!status=ok::descr=CPS CP1350PFCLCD Battery charge: 100%, 21 min volume!!1!!status=ok::descr=Volume C: RAID Level X2, Redundant; 9250 GB (83%) of 11110 GB used disk!!1!!status=ok::descr=Channel 1: Hitachi HDS5C3030ALA630 2794 GB, 35C/95F disk!!2!!status=ok::descr=Channel 2: Hitachi HDS5C3030ALA630 2794 GB, 38C/100F disk!!3!!status=ok::descr=Channel 3: WDC WD30EFRX-68AX9N0 2794 GB, 33C/91F disk!!4!!status=ok::descr=Channel 4: Hitachi HUA723030ALA640 2794 GB, 38C/100F disk!!5!!status=ok::descr=Channel 5: WDC WD30EFRX-68EUZN0 2794 GB, 34C/93F disk!!6!!status=ok::descr=Channel 6: WDC WD30EFRX-68EUZN0 2794 GB, 31C/87F model!!0!!mode=home::descr=ReadyNAS Ultra 6::arch=x86
a snipet of system.log
Mar 10 22:23:04 tesla6 RAIDiator: New disk detected. [Disk 6] (tesla6) : A new disk was added to the ReadyNAS. If multiple disks have been added, they will be processed one at a time. Please do not remove any added disk(s) during this time. Mar 10 22:25:12 tesla6 kernel: sdf: unknown partition table Mar 10 22:25:15 tesla6 kernel: sdf: sdf1 sdf2 sdf5 sdf6 Mar 10 22:25:16 tesla6 kernel: md: bind<sdf1> Mar 10 22:25:16 tesla6 kernel: RAID1 conf printout: Mar 10 22:25:16 tesla6 kernel: --- wd:5 rd:6 Mar 10 22:25:16 tesla6 kernel: disk 0, wo:0, o:1, dev:sda1 Mar 10 22:25:16 tesla6 kernel: disk 1, wo:0, o:1, dev:sdb1 Mar 10 22:25:16 tesla6 kernel: disk 2, wo:0, o:1, dev:sdc1 Mar 10 22:25:16 tesla6 kernel: disk 3, wo:1, o:1, dev:sdf1 Mar 10 22:25:16 tesla6 kernel: disk 4, wo:0, o:1, dev:sde1 Mar 10 22:25:16 tesla6 kernel: disk 5, wo:0, o:1, dev:sdd1 Mar 10 22:25:16 tesla6 kernel: md: recovery of RAID array md0 Mar 10 22:25:16 tesla6 kernel: md: minimum _guaranteed_ speed: 100000 KB/sec/disk. Mar 10 22:25:16 tesla6 kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery. Mar 10 22:25:16 tesla6 kernel: md: using 128k window, over a total of 4194292 blocks. Mar 10 22:25:54 tesla6 kernel: md: bind<sdf5> Mar 10 22:25:54 tesla6 kernel: RAID conf printout: Mar 10 22:25:54 tesla6 kernel: --- level:6 rd:6 wd:5 Mar 10 22:25:54 tesla6 kernel: disk 0, o:1, dev:sda5 Mar 10 22:25:54 tesla6 kernel: disk 1, o:1, dev:sdb5 Mar 10 22:25:54 tesla6 kernel: disk 2, o:1, dev:sdc5 Mar 10 22:25:54 tesla6 kernel: disk 3, o:1, dev:sdd5 Mar 10 22:25:54 tesla6 kernel: disk 4, o:1, dev:sde5 Mar 10 22:25:54 tesla6 kernel: disk 5, o:1, dev:sdf5 Mar 10 22:25:54 tesla6 kernel: md: delaying recovery of md2 until md0 has finished (they share one or more physical units) Mar 10 22:25:58 tesla6 kernel: md: bind<sdf6> Mar 10 22:25:58 tesla6 kernel: RAID conf printout: Mar 10 22:25:58 tesla6 kernel: --- level:6 rd:6 wd:5 Mar 10 22:25:58 tesla6 kernel: disk 0, o:1, dev:sdc6 Mar 10 22:25:58 tesla6 kernel: disk 1, o:1, dev:sdf6 Mar 10 22:25:58 tesla6 kernel: disk 2, o:1, dev:sda6 Mar 10 22:25:58 tesla6 kernel: disk 3, o:1, dev:sdb6 Mar 10 22:25:58 tesla6 kernel: disk 4, o:1, dev:sdd6 Mar 10 22:25:58 tesla6 kernel: disk 5, o:1, dev:sde6 Mar 10 22:25:58 tesla6 kernel: md: delaying recovery of md3 until md2 has finished (they share one or more physical units) Mar 10 22:26:00 tesla6 kernel: md: md0: recovery done. Mar 10 22:26:00 tesla6 kernel: md: delaying recovery of md3 until md2 has finished (they share one or more physical units) Mar 10 22:26:00 tesla6 kernel: md: delaying recovery of md2 until md3 has finished (they share one or more physical units) Mar 10 22:26:00 tesla6 kernel: md: recovery of RAID array md3 Mar 10 22:26:00 tesla6 kernel: md: minimum _guaranteed_ speed: 1000 KB/sec/disk. Mar 10 22:26:00 tesla6 kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery. Mar 10 22:26:00 tesla6 kernel: md: using 128k window, over a total of 976751296 blocks. Mar 10 22:26:01 tesla6 kernel: RAID1 conf printout: Mar 10 22:26:01 tesla6 kernel: --- wd:6 rd:6 Mar 10 22:26:01 tesla6 kernel: disk 0, wo:0, o:1, dev:sda1 Mar 10 22:26:01 tesla6 kernel: disk 1, wo:0, o:1, dev:sdb1 Mar 10 22:26:01 tesla6 kernel: disk 2, wo:0, o:1, dev:sdc1 Mar 10 22:26:01 tesla6 kernel: disk 3, wo:0, o:1, dev:sdf1 Mar 10 22:26:01 tesla6 kernel: disk 4, wo:0, o:1, dev:sde1 Mar 10 22:26:01 tesla6 kernel: disk 5, wo:0, o:1, dev:sdd1 Mar 10 22:53:14 tesla6 RAIDiator: RAID sync started on volume C. Mar 10 22:53:15 tesla6 RAIDiator: RAID event detected. (tesla6) : RAID sync started on volume C.\n\n[Sat Mar 10 22:53:14 EST 2018] Mar 10 23:41:30 tesla6 chronyd[3309]: Selected source 192.168.1.1 Mar 11 00:00:02 tesla6 RAIDiator: The on-line filesystem consistency check has started for Volume C. Mar 11 00:00:03 tesla6 RAIDiator: Volume consistency check started for Volume C. (tesla6) : The on-line filesystem consistency check has started for Volume C. Mar 11 00:00:05 tesla6 kernel: EXT4-fs (dm-3): INFO: recovery required on readonly filesystem Mar 11 00:00:05 tesla6 kernel: EXT4-fs (dm-3): write access will be enabled during recovery Mar 11 00:00:12 tesla6 kernel: EXT4-fs (dm-3): recovery complete Mar 11 00:00:12 tesla6 kernel: EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: acl,user_xattr Mar 11 00:12:26 tesla6 RAIDiator: The on-line filesystem consistency check completed without errors for Volume C. Mar 11 00:12:27 tesla6 RAIDiator: Volume consistency check completed for Volume C. (tesla6) : The on-line filesystem consistency check completed without errors for Volume C.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
