andykm Now • 100%
One reason I thought of this was that it's taking forever to manually copy files from the corrupt volume to an external hard drive anyhow, and I trust the external drive less. It's honestly not even that much data -- I can't imagine internally copying from one drive to another would take longer.
andykm Now • 100%
I'm like 99% sure it's RAID1, but it might be SHR. I'm sure it's not RAID0.
I have a DS220+ with 2x 6TB drives in RAID. I used some bad RAM, and now the volume is read-only and won't restore. I was resigned to backup the data, create a new volume, and restore the data, but I had an idea -- will this work?: Basically, I use one of the two drives as its own backup. I pull out one drive and save it, I wipe the other drive and create a new volume, then pop in the drive with files from the old volume, and copy the files over, and then recreate the RAID. Should that work? Any obstacles I should watch for?
I have a DS220+ with 2 identical drives, configured as RAID, so just one volume. Everything was working great, but to access the new object-recognition in photos, I added RAM, which caused some corruption and now the volume is read-only and won't repair itself (even after removing the RAM). So now I'm preparing to do an external backup and rebuild the NAS. But now I'm wondering: If volume issues are more likely than drive issues, should I forget about RAID, create one volume on each drive, and use the second volume as a local backup? Or is RAID still the best first line of defence? (Or is there a way I can do both with two drives?
The population of Canada is expected to hit 40 million within the next day or two, according to StatCan's modelling.