HELP!! - logged in to admin page today and got "No volumes exist" !
I had my NAS set up to shut down and restart every night. When it started up today I logged into the admin page and when I went to Shares it came up with "No volumes exist" and has the message "Remove inactive volumes to use the disk. Disk #1,2,3,4."
There's no info in the logs within the admin page indicating a problem.
I logged in via ssh and had a look in the logs there but again nothing I can find shows an error.
I hope this is what you are after, a bit before and a bit after 'md127'. Problem is it appears the disk had disappeared long before this time. Funny enough though, my mapping from my windows computer to the server still displays all the shares I had on the NAS but I can't get into them. If I click on a share I get "Network Error" "Windows cannot access..." :
[Sat May 6 20:23:11 2017] md1: detected capacity change from 0 to 1071644672 [Sat May 6 20:23:11 2017] BTRFS: device label 43f62a62:root devid 1 transid 1492722 /dev/md0 [Sat May 6 20:23:12 2017] systemd[1]: Failed to insert module 'kdbus': Function not implemented [Sat May 6 20:23:12 2017] systemd[1]: systemd 230 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN) [Sat May 6 20:23:12 2017] systemd[1]: Detected architecture x86-64. [Sat May 6 20:23:12 2017] systemd[1]: Set hostname to <biggun>. [Sat May 6 20:23:12 2017] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [Sat May 6 20:23:12 2017] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [Sat May 6 20:23:12 2017] systemd[1]: Reached target Paths. [Sat May 6 20:23:12 2017] systemd[1]: Listening on Journal Socket (/dev/log). [Sat May 6 20:23:12 2017] systemd[1]: Listening on udev Control Socket. [Sat May 6 20:23:12 2017] systemd[1]: Reached target Encrypted Volumes. [Sat May 6 20:23:12 2017] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [Sat May 6 20:23:12 2017] systemd[1]: Listening on Journal Socket. [Sat May 6 20:23:12 2017] systemd[1]: Listening on udev Kernel Socket. [Sat May 6 20:23:12 2017] systemd[1]: Created slice User and Session Slice. [Sat May 6 20:23:12 2017] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [Sat May 6 20:23:12 2017] systemd[1]: Created slice System Slice. [Sat May 6 20:23:12 2017] systemd[1]: Created slice system-serial\x2dgetty.slice. [Sat May 6 20:23:12 2017] systemd[1]: Mounting RPC Pipe File System... [Sat May 6 20:23:12 2017] systemd[1]: Starting hwclock.service... [Sat May 6 20:23:12 2017] systemd[1]: Mounting POSIX Message Queue File System... [Sat May 6 20:23:12 2017] systemd[1]: Created slice system-getty.slice. [Sat May 6 20:23:12 2017] systemd[1]: Created slice system-openvpn.slice. [Sat May 6 20:23:12 2017] systemd[1]: Starting Journal Service... [Sat May 6 20:23:12 2017] systemd[1]: Mounting Debug File System... [Sat May 6 20:23:12 2017] systemd[1]: Reached target Slices. [Sat May 6 20:23:12 2017] systemd[1]: Started ReadyNAS LCD splasher. [Sat May 6 20:23:12 2017] systemd[1]: Starting ReadyNASOS system prep... [Sat May 6 20:23:12 2017] systemd[1]: Starting Create list of required static device nodes for the current kernel... [Sat May 6 20:23:12 2017] systemd[1]: Mounting RPC Pipe File System... [Sat May 6 20:23:12 2017] systemd[1]: Starting Load Kernel Modules... [Sat May 6 20:23:12 2017] systemd[1]: Starting MD arrays... [Sat May 6 20:23:12 2017] systemd[1]: Started Create list of required static device nodes for the current kernel. [Sat May 6 20:23:12 2017] systemd[1]: Starting Create Static Device Nodes in /dev... [Sat May 6 20:23:12 2017] systemd[1]: Started Load Kernel Modules. [Sat May 6 20:23:12 2017] systemd[1]: Mounted RPC Pipe File System. [Sat May 6 20:23:12 2017] systemd[1]: Mounted POSIX Message Queue File System. [Sat May 6 20:23:12 2017] systemd[1]: Mounted Debug File System. [Sat May 6 20:23:12 2017] systemd[1]: Mounted RPC Pipe File System. [Sat May 6 20:23:12 2017] systemd[1]: Mounting FUSE Control File System... [Sat May 6 20:23:12 2017] systemd[1]: Mounting Configuration File System... [Sat May 6 20:23:12 2017] systemd[1]: Starting Apply Kernel Variables... [Sat May 6 20:23:12 2017] systemd[1]: Mounted Configuration File System. [Sat May 6 20:23:12 2017] systemd[1]: Mounted FUSE Control File System. [Sat May 6 20:23:12 2017] systemd[1]: Started Create Static Device Nodes in /dev. [Sat May 6 20:23:12 2017] systemd[1]: Started hwclock.service. [Sat May 6 20:23:12 2017] systemd[1]: Started Apply Kernel Variables. [Sat May 6 20:23:12 2017] systemd[1]: Starting Remount Root and Kernel File Systems... [Sat May 6 20:23:12 2017] systemd[1]: Reached target System Time Synchronized. [Sat May 6 20:23:12 2017] systemd[1]: Starting udev Kernel Device Manager... [Sat May 6 20:23:12 2017] systemd[1]: Started ReadyNASOS system prep. [Sat May 6 20:23:12 2017] systemd[1]: Started Remount Root and Kernel File Systems. [Sat May 6 20:23:12 2017] systemd[1]: Starting Load/Save Random Seed... [Sat May 6 20:23:12 2017] systemd[1]: Starting Rebuild Hardware Database... [Sat May 6 20:23:12 2017] systemd[1]: Started Load/Save Random Seed. [Sat May 6 20:23:13 2017] systemd[1]: Started udev Kernel Device Manager. [Sat May 6 20:23:13 2017] systemd[1]: Started Journal Service. [Sat May 6 20:23:13 2017] systemd-journald[1335]: Received request to flush runtime journal from PID 1 [Sat May 6 20:23:14 2017] md: md127 stopped. [Sat May 6 20:23:14 2017] md: bind<sdb3> [Sat May 6 20:23:14 2017] md: bind<sdc3> [Sat May 6 20:23:14 2017] md: bind<sdd3> [Sat May 6 20:23:14 2017] md: bind<sda3> [Sat May 6 20:23:14 2017] md/raid:md127: device sda3 operational as raid disk 0 [Sat May 6 20:23:14 2017] md/raid:md127: device sdd3 operational as raid disk 3 [Sat May 6 20:23:14 2017] md/raid:md127: device sdc3 operational as raid disk 2 [Sat May 6 20:23:14 2017] md/raid:md127: device sdb3 operational as raid disk 1 [Sat May 6 20:23:14 2017] md/raid:md127: allocated 4354kB [Sat May 6 20:23:14 2017] md/raid:md127: raid level 5 active with 4 out of 4 devices, algorithm 2 [Sat May 6 20:23:14 2017] RAID conf printout: [Sat May 6 20:23:14 2017] --- level:5 rd:4 wd:4 [Sat May 6 20:23:14 2017] disk 0, o:1, dev:sda3 [Sat May 6 20:23:14 2017] disk 1, o:1, dev:sdb3 [Sat May 6 20:23:14 2017] disk 2, o:1, dev:sdc3 [Sat May 6 20:23:14 2017] disk 3, o:1, dev:sdd3 [Sat May 6 20:23:14 2017] created bitmap (15 pages) for device md127 [Sat May 6 20:23:14 2017] md127: bitmap initialized from disk: read 1 pages, set 0 of 29735 bits [Sat May 6 20:23:14 2017] md127: detected capacity change from 0 to 5986292072448 [Sat May 6 20:23:15 2017] Adding 1046524k swap on /dev/md1. Priority:-1 extents:1 across:1046524k [Sat May 6 20:23:15 2017] BTRFS: device label 43f62a62:data devid 1 transid 1170744 /dev/md127 [Sat May 6 20:23:15 2017] md: md126 stopped. [Sat May 6 20:23:15 2017] md: bind<sdd4> [Sat May 6 20:23:15 2017] md: bind<sdc4> [Sat May 6 20:23:15 2017] md/raid1:md126: active with 2 out of 2 mirrors [Sat May 6 20:23:15 2017] md126: detected capacity change from 0 to 1000061861888 [Sat May 6 20:23:15 2017] BTRFS: device label 43f62a62:data devid 2 transid 1170744 /dev/md126 [Sat May 6 20:23:15 2017] BTRFS (device md126): bad fsid on block 771250716672 [Sat May 6 20:23:15 2017] BTRFS (device md126): bad fsid on block 771250716672 [Sat May 6 20:23:15 2017] BTRFS: failed to read tree root on md126 [Sat May 6 20:23:15 2017] BTRFS: open_ctree failed [Sat May 6 20:23:17 2017] bonding: bond0 is being created... [Sat May 6 20:23:18 2017] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready [Sat May 6 20:23:18 2017] 8021q: adding VLAN 0 to HW filter on device bond0 [Sat May 6 20:23:18 2017] bond0: Setting MII monitoring interval to 100 [Sat May 6 20:23:18 2017] bond0: Setting xmit hash policy to layer3+4 (1) [Sat May 6 20:23:18 2017] e1000e: eth0 NIC Link is Down [Sat May 6 20:23:18 2017] bond0: Adding slave eth0 [Sat May 6 20:23:18 2017] 8021q: adding VLAN 0 to HW filter on device eth0 [Sat May 6 20:23:18 2017] bond0: Enslaving eth0 as an active interface with a down link [Sat May 6 20:23:18 2017] e1000e: eth1 NIC Link is Down [Sat May 6 20:23:18 2017] bond0: Adding slave eth1 [Sat May 6 20:23:18 2017] 8021q: adding VLAN 0 to HW filter on device eth1 [Sat May 6 20:23:18 2017] bond0: Enslaving eth1 as an active interface with a down link [Sat May 6 20:23:18 2017] bond0: Setting eth0 as primary slave [Sat May 6 20:23:18 2017] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready [Sat May 6 20:23:18 2017] 8021q: adding VLAN 0 to HW filter on device bond0 [Sat May 6 20:23:18 2017] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready [Sat May 6 20:23:18 2017] 8021q: adding VLAN 0 to HW filter on device bond0 [Sat May 6 20:23:19 2017] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None [Sat May 6 20:23:19 2017] e1000e 0000:01:00.0 eth0: 10/100 speed: disabling TSO [Sat May 6 20:23:20 2017] bond0: link status definitely up for interface eth0, 100 Mbps full duplex [Sat May 6 20:23:20 2017] bond0: making interface eth0 the new active one [Sat May 6 20:23:20 2017] bond0: first active interface up! [Sat May 6 20:23:20 2017] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready [Sat May 6 20:23:20 2017] e1000e: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None [Sat May 6 20:23:20 2017] e1000e 0000:03:00.0 eth1: 10/100 speed: disabling TSO [Sat May 6 20:23:20 2017] bond0: link status definitely up for interface eth1, 100 Mbps full duplex [Sat May 6 20:23:22 2017] BTRFS: could not find root 8 [Sat May 6 20:23:26 2017] wsdd2[2910]: segfault at 0 ip 0000000000401ee0 sp 00007ffc1262fd80 error 4 in wsdd2[400000+a000] [Sat May 6 20:23:27 2017] wsdd2[3774]: segfault at 0 ip 0000000000401ee0 sp 00007ffedc20ae20 error 4 in wsdd2[400000+a000] [Sat May 6 20:23:27 2017] wsdd2[3776]: segfault at 0 ip 0000000000401ee0 sp 00007fffc0b4f8a0 error 4 in wsdd2[400000+a000] [Sat May 6 20:23:27 2017] wsdd2[3785]: segfault at 0 ip 0000000000401ee0 sp 00007fff8cc3ffc0 error 4 in wsdd2[400000+a000] [Sat May 6 20:23:27 2017] wsdd2[3788]: segfault at 0 ip 0000000000401ee0 sp 00007ffd81661c40 error 4 in wsdd2[400000+a000] [Sat May 6 20:23:28 2017] wsdd2[3790]: segfault at 0 ip 0000000000401ee0 sp 00007ffe5fae6430 error 4 in wsdd2[400000+a000] [Sat May 6 20:23:28 2017] wsdd2[3792]: segfault at 0 ip 0000000000401ee0 sp 00007fffb0eba520 error 4 in wsdd2[400000+a000] [Sat May 6 20:23:28 2017] wsdd2[3811]: segfault at 0 ip 0000000000401ee0 sp 00007ffe31774d00 error 4 in wsdd2[400000+a000] [Sat May 6 20:23:28 2017] wsdd2[3813]: segfault at 0 ip 0000000000401ee0 sp 00007ffcaf190e30 error 4 in wsdd2[400000+a000] [Sat May 6 20:23:29 2017] wsdd2[3815]: segfault at 0 ip 0000000000401ee0 sp 00007ffebb1386f0 error 4 in wsdd2[400000+a000]
[Sat May 6 20:23:15 2017] BTRFS (device md126): bad fsid on block 771250716672 [Sat May 6 20:23:15 2017] BTRFS (device md126): bad fsid on block 771250716672 [Sat May 6 20:23:15 2017] BTRFS: failed to read tree root on md126 [Sat May 6 20:23:15 2017] BTRFS: open_ctree failed
A part of your BTRFS volume is corrupted. You have four hard drives, with different sizes, don't you?
If you feel confident with it, you should research "BTRFS restore" to attempt dumping the data to an external storage. If may or may not work.
If not, you need to contact a data recovery specialist. NETGEAR provides this kind of services as a contact. They have the required knowledge and experience to do much more than the above.
Do you see any SMART error on any drive? (There are other possible reasons for this to occur.)
Re: HELP!! - logged in to admin page today and got "No volumes exist" !
Thanks for your help and yes, I have two 2TB and two 4TB HDDs.
I haven't noticed any SMART errors on the disks. They all seem to light in green and there doesn't appear to be any errors on the disks when I look in volumes in the NAS Admin page but I'll check again asap.
I guess it's as you say, go looking at BTRFS for now...
Re: HELP!! - logged in to admin page today and got "No volumes exist" !
FYI, I worked out how to look at the SMART settings on the disks last night and besides one marginal (temperature) there are no errors on the disks themselves.
Re: HELP!! - logged in to admin page today and got "No volumes exist" !
I too am having the same issue after a reboot. No Volumes and it tells me to create a new one. No errors on drives. I have bee having alot of issues ever since the update to 6.6.1 with frequent no response.
I too am having the same issue after a reboot. No Volumes and it tells me to create a new one. No errors on drives. I have bee having alot of issues ever since the update to 6.6.1 with frequent no response.
If you have a good backup, then I suggest doing a factory reset, reconfiguring the NAS and restoring the data from the backup.
If you need to get data off the NAS, then I suggest that you contact Netgear paid support.
Re: HELP!! - logged in to admin page today and got "No volumes exist" !
Hi,
Your mileage may vary but this helped me:
I shutdown and restart my (legacy) nas every day too. Sometimes it comes up with the same message as you report. In that case I shutdown the readynas by pressing the power button a number of times (7?) until the display asks if it should power down the nas. AFTER full shutdown I pull the power cable out of the wall socket for a few minutes. Once I put it back and restart the NAS the disks are found again.
I have not heard of anyone having succes with this approach but it always worked in my case.
At a certain moment, and I do not know if this is related to the "no disks found" issue, I ran into critical HD failures that destroyed my complete raid array and thus I lost all data. Eventually I found recovery software that pieced back the raid array and with that I could copy everything to new disks: I posted detailed instructions earlier, it was not too difficult either.
And for the future, unless you have files larger than your HDD's or you have very slow HDD's, stay away from RAID configurations: you have a higher risk of losing all your data, and it makes recovery much more complicated. In a nutshell: you need a backup regardless and without Raid you only lose the disk that faults. See my other posts for a more extensive explanation.
As a last note: since I renewed my HDD's, I have not had the boot problems anymore, but then I have also upgraded the firmware in the mean time.
Hopefully you'll recover everything too, good luck.
And for the future, unless you have files larger than your HDD's or you have very slow HDD's, stay away from RAID configurations: you have a higher risk of losing all your data, and it makes recovery much more complicated. In a nutshell: you need a backup regardless and without Raid you only lose the disk that faults. See my other posts for a more extensive explanation.
This is terrible advise. While a complete colapse of the volume, which is an atypical event, can cause complete loss of data in a RAID, loss of a single drive in a non-RAID configuration is more typical and will certainly result in loss of some of your data.
Here is the proper advise: Stick with a RAID appropriate to your use and keep a separate backup. There is an old IT saying "if you only have one copy of something, you must not think it's important". It is as true today as it was 30ish years ago when I first heard it. RAID is not two copies of something, it is one copy with a protective layer. It helps prevent the need for a total recovery from backup when the typical event occurs (failure of a hard drive), but does not protect against all loss cases. It's also provides a large, contiguous storage space where one does not have to juggle data between individual drives. With drives getting bigger and bigger, that's becoming less important; but data is also getting bigger and bigger (like 4K videos).
Re: HELP!! - logged in to admin page today and got "No volumes exist" !
Hi Sandshark,
I don't agree with what you qualify as your "proper advice", I really see no significant benefits in using raid: it costs performance, it costs diskspace, and it makes it more difficult to recover if it goes wrong, in exchange for what benefit exactly?
Your key argument seems to be that raid is good in case you have very large files. I mentioned that already, and I think that that is a non issue with todays multi terabyte disks. Your example points it out itself: 4k Movies won't take up more than 100 GB.... so that means I can store 60 movies on one 6 TB disk. Even if I am off by 100 percent you can still store 30 movies on one disk. And on top of that, a RN316 takes 10TB disks.. The only advantage is that a volume can span multiple disks, wholly or partially, but than can also be accomplished without Raid, thus avoiding the risk of losing all data.
I have experienced the "atypical" event. I described in a post some time ago how one atypical event led to another which resulted in a total loss of data. As a result I realised that the risk that you lose all data is much higher with a raid array than with individual disks: with X-Raid or Raid 5 for example, if two disks fail all your data is gone. With individual disks you lose only the data on the two disks. Or in other words: suppose you have 4 disks: the chance that all 4 fail is obviously much smaller. What's more, individual disks are much easier to restore. And in case backups failed, data is much easier to recover from individual disk/volumes, than from disks that were part of a RAID array. Ask a recovery company. Dynamic RAID configurations (X-Raid and the like) make it even harder, as the parameters that define the array are "dynamic": thus unknown.
I have since my atypical event experience recovered (see my posts) and as a result reconfigured my Readynas boxes without any form or raid, thus with every disk as an individual volume. I have not met one occasion that would want me to introduce a raid array again.
My point is that I think the tradeoff is pretty clear: with out RAID I gain: more performance, more diskspace, less complexity and less risk, while I lose nothing.
I am still looking for that compelling argument for a RAID configuration, but I believe your post has not brought that.
Re: HELP!! - logged in to admin page today and got "No volumes exist" !
How many single drives have you lost? I have lost several, as I have been using the ReadyNASes for some time. I made sure my backup was in order, then put in a replacement drive, the volume re-synced, and all was well. That is the typical case. I lost no data and I lost no time restoring data. Those are benefits to me, and the primary use for RAID. I did do a preventative backup, but that did not make my data unavailable, it just delayed the point at which is was once again redundent. If those don't matter to you, then by all means don't use RAID. But I believe your useage to be atypical and following your example is not appropriate for most users.
Yes, you can store large files on individual large drives. But you have to work out where each one will go and remember where it is when you go to get it. With one large RAID, there is no decision to make. I went from several USB drives to one NAS because I tired of doing that. Individually addressed drives in a NAS are not that much different from that. This is a secondary use of RAID. If you don't see it as a benefit like I do, then do it your way. But advising others to do the same as you is telling them to ignore one of the reasons they probably bought a NAS.
I went and looked at your post for the data loss. You had one atypical event, not two. The loss of the first drive is not atypical. One hopes they don't happen often, but when a failure does occur, that's the typical one. I'm not sure that you did not mis-identify the bad drive, You started a scrub with a degraded volume -- one of the worst things you could have done because it, too, is hard on the drives and relies on an intact volume. You may have contributed to the data loss -- it's impossible to tell. Re-sync is hard on your existing drives and making sure your data was backed up before replacing the drive should have been in your course of action.
Re: HELP!! - logged in to admin page today and got "No volumes exist" !
Hi Sandshark,
Resyncing a replaced disk in a raid array can take a while..... Restoring a single disk is most of the time much faster. And after one click ("copy") it all goes automatic. You can't convince me that automatic resync is that important that you accept the increased risk, lost capacity, lost performance and increased complexity. But opinions differ of course...
But what's more, I think (automatic) resync is actually a bad thing: it puts a big strain on your disks, as you point out, at the moment that your array is not redundant anymore. Why on earth do you want to do that at the moment you try to recover from having lost one disk already? This should be the period that you treat all disks with the greatest care until the array is redundant again!
On the ease of storing files. Unless people use the whole array as one folder I don't see any difference. And if they do use the array as one folder then I hope they don't have too many files... But regardless, as I stated before, you don't need RAID for that: for example https://romanrm.net/mhddfs, or http://www.windowscentral.com/how-create-one-large-volume-using-multiple-hard-drives-windows-10. The first one even describes exactly your use case, but these solutions have the advantage that they don't introduce dependencies between disks as Raid does.
So once more, RAID, including resync, does nothing over individual disks to protect your data, nothing to access it easier and very little to reduce maintenance. At the same time it significantly increases risk, and complexity, while it reduces capacity and performance. So I don't think it is a good idea, in fact I think it is a bad idea..
You may like Raid for a reason I don't understand, and you may call my advice terrible and your own advice proper, I'll leave it at this and let everyone decide for themselves.
Re: HELP!! - logged in to admin page today and got "No volumes exist" !
Decided to factory default and rebuild the volume and data. It wasn't important data so it was not a big deal. Ran extensive tests on the drives to make sure there were no errors. Upgraded to 6.7.1 and restoring data. Still get occasional lockup of the nas like I was getting on 6.6.1 but so far I do not see any corruption to the btrfs filesystem. Hopefully don't have anymore issues.
Re: HELP!! - logged in to admin page today and got "No volumes exist" !
I guess you didn't read the entire article: "In addition, both Spanned and Striped volumes do not use parity, which means they the don't provide fault tolerance — if one drive fails you will lose the data on all hard drives —so make sure to create regular backups of your computer." So, each drive does depend on the others (as is always the case with spanned drives) and losing but one drive in this configuration causes you to lose everything every time. Losing a single drive in a RAID5 rarely does. And what of those of use who access the data with systems other than Windows or don't have enough drive slots in our computers for all the drives? And where are you oing to keep that oh so important backup the earticle recommends? Probably on a NAS with RAID.
I just re-sync'ed a 2TB drive in 8 hours. I don't think you can restore 2TB of data in any significantly shorter time. During that time, I had full access to my data. More complex? I inserted the drive and it did everying for me. Couldn't be more simple. Not even one button to push. You left out partitioning and formatting in your "one click" solution, BTW. Dangerous? There is risk, as there typically is with any gain. But it's low, especially when properly managed (like checking SMART stats regularly).
Yes, having uninterrupted access to my data, as happens during a resync, is that important to me, as it is for many. On a low end NAS like a 100 series, the performance hit during resync may be a lot. I don't use those..But the data is still available.
Plain and simple, you are searching high and low for reasons that don't exist to say RAID is not useful or is somehow complicated and should be avoided. Maybe once it was complicated, but Netgear has made it not so with XRAID. You are condemning a good system because of your unusual case, which you agravated yourself. You would do other users a service by discontinuing your snake oil sales.
I think your comment is misdirected. I was just replying to my sitatuon. I have no problem with using Raid.
Unfortunately, one cannot "direct" a reply to just one message; it goes to the bottom. My reply is obviously intended for Hombibi, who has chosen this topic to proselytize against the use of RAID. Sorry for the confusion.
