NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
8TB Drive drops out of JBOD volume on 6.4.0 on Ultra4
Hi I have 2x8TB Seagate Archive HDDs in JBOD array in a Ultra4 on 6.4.0 production. I started doing a rsync backup (this device was the destination) and after about 10min the second drive showed up...
It says JBOD on the status page. Each drive is 7.2 formatted I think so 14.4 in total.
Edit:
From volume.log
Pool backup: Device: /dev/md126 Node: 9:127 HostID: 5e26b038 (native) UUID: 635f4fc7-2874-40a5-965f-1d738131aaf7 Mount point: /backup Size: 15616260544KB (14892 GB) Available: 15615978408KB (14892 GB) RAID Level: JBOD State: unprotected Action: idle Flags 0x148 Type: btrfs RAIDs: md127 Size: 15618353664 Level: 0 Action: idle Members: 1 md126 Size: 15618353664 Level: 1 Action: idle Members: 1
It was also quick to set up and add second disk - few minutes - whereas I think (although I may be wrong) to set up RAID would take a few hours to initialise an array - especially with these disks.
Do you have two volumes or only one?
My guess is only one from the log.
If one, it is spanning RAID-0 no matter what volume.log says. And if either disk fails you lose the data on both.
Only 1 volume.
So a test would be to pull one and see what happens??
Thanks
A
powellandy1 wrote:
So a test would be to pull one and see what happens??
I wouldn't recommend that unless you want to lose your data.
StephenB wrote:
Do you have two volumes or only one?
My guess is only one from the log.
If one, it is spanning RAID-0 no matter what volume.log says. And if either disk fails you lose the data on both.
Not exactly true. It's not striping, so it's not RAID 0; but it is concatenated into the same volume "pool". Flex-RAID allows you to do this.
Thanks for the clarification. Whilst I know they are technically not supported they do seem to be causing a heap of problems - https://community.netgear.com/t5/Using-your-ReadyNAS/Seagate-8TB-Archive-drives-ST8000AS0002-do-work/m-p/989048 - that seem to be worse with 6.4.0, which might be related to the new linux kernel.
A
Right, and it certainly doesn't appear to be specific to ReadyNAS. There are many posts about the same issue online, with an official kernel bug report still open at https://bugzilla.kernel.org/show_bug.cgi?id=93581.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
