NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Cloneing failed drive Readynas Pro OS6
I have a readynas Pro business edition with 6x 3tb drives in single redundancy. It's running the latest 0s6 firmware. A drive failed last week, I'm still waiting for the replacement to arrive and ...
It seems that it is not accepting sdc3
I had a look and the events aren't that far out.
Examining sdd3
Is the next step to force assemble ? mdadm --assemble --force
Thanks again for the help
RAID conf printout:
--- level:6 rd:5 wd:5
disk 0, o:1, dev:sda2
disk 1, o:1, dev:sdb2
disk 2, o:1, dev:sdc2
disk 3, o:1, dev:sdd2
disk 4, o:1, dev:sde2
md1: detected capacity change from 0 to 1608843264
md1: unknown partition table
btrfs: device label 33ea2359:root devid 1 transid 927169 /dev/md0
systemd[1]: systemd 44 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP; debian)
systemd[1]: Set hostname to <Media-nas>.
udevd[1190]: starting version 175
systemd-journald[1178]: Fixed max_use=32.0M max_size=8.0M min_size=64.0K keep_free=204.6M
systemd-journald[1178]: Vacuuming...
systemd-journald[1178]: Flushing /proc/kmsg...
md: md127 stopped.
md: bind<sdb3>
md: bind<sdc3>
md: bind<sdd3>
md: bind<sde3>
md: bind<sda3>
md: kicking non-fresh sdc3 from array!
md: unbind<sdc3>
md: export_rdev(sdc3)
md/raid:md127: device sda3 operational as raid disk 0
md/raid:md127: device sde3 operational as raid disk 5
md/raid:md127: device sdd3 operational as raid disk 4
md/raid:md127: device sdb3 operational as raid disk 1
md/raid:md127: allocated 6372kB
md/raid:md127: not enough operational devices (2/6 failed)
RAID conf printout:
--- level:5 rd:6 wd:4
disk 0, o:1, dev:sda3
disk 1, o:1, dev:sdb3
disk 4, o:1, dev:sdd3
disk 5, o:1, dev:sde3
md/raid:md127: failed to run raid set.
md: pers->run() failed ...
md: md127 stopped.
md: unbind<sda3>
md: export_rdev(sda3)
md: unbind<sde3>
md: export_rdev(sde3)
md: unbind<sdd3>
md: export_rdev(sdd3)
md: unbind<sdb3>
md: export_rdev(sdb3)
I had a look and the events aren't that far out.
mdadm --examine /dev/sd[a-z][1-6] | egrep 'Event|/dev/sd'
/dev/sda1:
Events : 281660
/dev/sda2:
Events : 21
/dev/sda3:
Events : 244566
/dev/sdb1:
Events : 281660
/dev/sdb2:
Events : 21
/dev/sdb3:
Events : 244566
/dev/sdc1:
Events : 281660
/dev/sdc2:
Events : 21
/dev/sdc3:
Events : 244481
/dev/sdd1:
Events : 281660
/dev/sdd2:
Events : 21
/dev/sdd3:
Events : 244566
/dev/sde1:
Events : 281660
/dev/sde2:
Events : 21
/dev/sde3:
Events : 244566
Examining sdd3
root@Media-nas:~# mdadm --examine /dev/sdc3
/dev/sdc3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 318fc18f:8d9a07c9:696c3a7f:195c8a72
Name : 33ea2359:data-0 (local to host 33ea2359)
Creation Time : Tue Apr 8 18:14:25 2014
Raid Level : raid5
Raid Devices : 6
Avail Dev Size : 5850829681 (2789.89 GiB 2995.62 GB)
Array Size : 14627073920 (13949.47 GiB 14978.12 GB)
Used Dev Size : 5850829568 (2789.89 GiB 2995.62 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262064 sectors, after=113 sectors
State : clean
Device UUID : 5e40c5f2:52184be2:b19f418c:20f3afae
Internal Bitmap : 8 sectors from superblock
Update Time : Mon Jun 8 23:27:14 2015
Checksum : 74ef4c53 - correct
Events : 244481
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 3
Array State : AA.AAA ('A' == active, '.' == missing, 'R' == replacing)
root@Media-nas:~# mdadm --examine /dev/sdc3
/dev/sdc3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 318fc18f:8d9a07c9:696c3a7f:195c8a72
Name : 33ea2359:data-0 (local to host 33ea2359)
Creation Time : Tue Apr 8 18:14:25 2014
Raid Level : raid5
Raid Devices : 6
Avail Dev Size : 5850829681 (2789.89 GiB 2995.62 GB)
Array Size : 14627073920 (13949.47 GiB 14978.12 GB)
Used Dev Size : 5850829568 (2789.89 GiB 2995.62 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262064 sectors, after=113 sectors
State : clean
Device UUID : 5e40c5f2:52184be2:b19f418c:20f3afae
Internal Bitmap : 8 sectors from superblock
Update Time : Mon Jun 8 23:27:14 2015
Checksum : 74ef4c53 - correct
Events : 244481
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 3
Array State : AA.AAA ('A' == active, '.' == missing, 'R' == replacing)
Is the next step to force assemble ? mdadm --assemble --force
Thanks again for the help
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
