NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS 316 (6x4TB Enterprise) - No volumes after graceful shutdown and restart
I shutdown my RN316 while leaving for a few days. Upon restart, I was able to connect and access normally. However after about 15 minutes when I tried to save a file to the NAS I was not able to acce...
Hi StephenB
Thanks for pointing me to those logs and taking the time to review this. .
From Systemd-journal.log:
"Jan 26 10:14:12 NAS_IV kernel: md/raid:md1: raid level 6 active with 6 out of 6 devices, algorithm 2"
(It looks like on bootup all 6 drives started up ok. Then...)
" Jan 26 10:14:12 NAS_IV kernel: BTRFS: device label 7c6e3b76:root devid 1 transid 4240856 /dev/md0"
(I think this must have been a failure on Raid Disk 1, because next I see ...)
"Jan 26 10:14:12 NAS_IV kernel: md: kicking non-fresh sdf3 from array!"
(There is no matching BTRFS error for this Raid Drive 5, but next I see...)
"Jan 26 10:14:12 NAS_IV kernel: md/raid:md127: not enough operational devices (2/6 failed)"
(Followed by unbind and export_rdev for each drive.)
RT6507 wrote:
"Jan 26 10:14:12 NAS_IV kernel: md: kicking non-fresh sdf3 from array!"
(There is no matching BTRFS error for this Raid Drive 5, but next I see...)
"Jan 26 10:14:12 NAS_IV kernel: md/raid:md127: not enough operational devices (2/6 failed)"
(Followed by unbind and export_rdev for each drive.)
Any idea on what the second missing disk might be?
I think Disk 1 and Disk 5 must have been the problems:
"Jan 26 09:54:23 NAS_IV kernel: --- level:5 rd:6 wd:4
Jan 26 09:54:23 NAS_IV kernel: disk 0, o:1, dev:sda3
Jan 26 09:54:23 NAS_IV kernel: disk 2, o:1, dev:sdc3
Jan 26 09:54:23 NAS_IV kernel: disk 3, o:1, dev:sdd3
Jan 26 09:54:23 NAS_IV kernel: disk 4, o:1, dev:sde3"
RT6507 wrote:
I think Disk 1 and Disk 5 must have been the problems:
"Jan 26 09:54:23 NAS_IV kernel: --- level:5 rd:6 wd:4
Jan 26 09:54:23 NAS_IV kernel: disk 0, o:1, dev:sda3
Jan 26 09:54:23 NAS_IV kernel: disk 2, o:1, dev:sdc3
Jan 26 09:54:23 NAS_IV kernel: disk 3, o:1, dev:sdd3
Jan 26 09:54:23 NAS_IV kernel: disk 4, o:1, dev:sde3"Normally you'd see sda - sdf. sdb would be disk 2 (numbering from 1), sdf would disk 6. So 1 and 5 if numbering from 0.
Can you test them in a Windows PC with vendor tools (Dashboard for Western Digital, Seatools for Seagate)?
sdf can be forcibly added to the array with ssh,though it would be good to understand what is happening with sdb.
Your help is much appreciated! I can move the drives (one at a time) to a Windows chassis I have standing by, but it only has three available SATA connections. Can I pull and examine the drives (WD Red Pro 4.0 TB) from the RN316 individually without overwriting any needed RAID tables?
Also, I don't see any explicit drive failure BTRFS errors for drive 1 (SDB3). This is from Systemd-Journal.log. It implies Disk 1 (SDB3) is offline.
Jan 26 08:46:46 NAS_IV kernel: BTRFS: device label 7c6e3b76:root devid 1 transid 4240694 /dev/md0
Jan 26 08:46:46 NAS_IV systemd[1]: systemd 44 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP; debian)
Jan 26 08:46:46 NAS_IV systemd[1]: Set hostname to <NAS_IV>.
Jan 26 08:46:46 NAS_IV udevd[1342]: starting version 175
Jan 26 08:46:46 NAS_IV systemd-journal[1333]: Journal started
Jan 26 08:46:46 NAS_IV kernel: md: md127 stopped.
Jan 26 08:46:46 NAS_IV kernel: md: bind<sdb3>
Jan 26 08:46:46 NAS_IV kernel: md: bind<sdc3>
Jan 26 08:46:46 NAS_IV kernel: md: bind<sdd3>
Jan 26 08:46:46 NAS_IV kernel: md: bind<sde3>
Jan 26 08:46:46 NAS_IV kernel: md: bind<sdf3>
Jan 26 08:46:46 NAS_IV kernel: md: bind<sda3>
Jan 26 08:46:46 NAS_IV kernel: md: kicking non-fresh sdb3 from array!
Jan 26 08:46:46 NAS_IV kernel: md: unbind<sdb3>
Jan 26 08:46:46 NAS_IV kernel: md: export_rdev(sdb3)
Jan 26 08:46:46 NAS_IV kernel: md/raid:md127: device sda3 operational as raid disk 0
Jan 26 08:46:46 NAS_IV kernel: md/raid:md127: device sdf3 operational as raid disk 5
Jan 26 08:46:46 NAS_IV kernel: md/raid:md127: device sde3 operational as raid disk 4
Jan 26 08:46:46 NAS_IV kernel: md/raid:md127: device sdd3 operational as raid disk 3
Jan 26 08:46:46 NAS_IV kernel: md/raid:md127: device sdc3 operational as raid disk 2
Jan 26 08:46:46 NAS_IV kernel: md/raid:md127: allocated 0kB
Jan 26 08:46:46 NAS_IV kernel: md/raid:md127: raid level 5 active with 5 out of 6 devices, algorithm 2
Jan 26 08:46:46 NAS_IV kernel: RAID conf printout:
Jan 26 08:46:46 NAS_IV kernel: --- level:5 rd:6 wd:5
Jan 26 08:46:46 NAS_IV kernel: disk 0, o:1, dev:sda3
Jan 26 08:46:46 NAS_IV kernel: disk 2, o:1, dev:sdc3
Jan 26 08:46:46 NAS_IV kernel: disk 3, o:1, dev:sdd3
Jan 26 08:46:46 NAS_IV kernel: disk 4, o:1, dev:sde3
Jan 26 08:46:46 NAS_IV kernel: disk 5, o:1, dev:sdf3
Jan 26 08:46:46 NAS_IV kernel: created bitmap (30 pages) for device md127
Jan 26 08:46:46 NAS_IV kernel: md127: bitmap initialized from disk: read 2 pages, set 568 of 59543 bits
Jan 26 08:46:46 NAS_IV kernel: md127: detected capacity change from 0 to 19979093934080
Jan 26 08:46:46 NAS_IV start_raids[1325]: mdadm: /dev/md/data-0 has been started with 5 drives (out of 6).
Jan 26 08:46:46 NAS_IV kernel: Adding 2094844k swap on /dev/md1. Priority:-1 extents:1 across:2094844k
Jan 26 08:46:47 NAS_IV kernel: BTRFS: device label 7c6e3b76:data devid 1 transid 285232 /dev/md127
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
