Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 4873

General discussion • Re: Move Synology NAS Drives to Pi 5

$
0
0
There isn't enough info on the https://global.synologydownload.com/dow ... et_enu.pdf datasheet to tell, so assume you'll have to copy everything. It's possible (as pdf mentions ext4 internal) that it'll be using software raid but you'll risk losing all the data in order to find out.

I haven't used OMV so can't advise. I prefer to set up my NAS manually. Here's two enclosure problems to consider:

a) My IcyBox two bay usb enclosure had a failing drive so I replaced both with larger HDD last week. The replacement drives are slimmer and physically(*) aren't secure. Advantage of this enclosure is it presents both drives as though they were each attached individually.

b) My Yottamaster five bay enclosure was purchased as somewhere to put all the "odd" HDD's (like the good one from above). I specifically purchased it because it will spin down each drive bay. Contrast with (a) which always keeps them running.

Both the above are attached to an rpi4.

Thus (a) is more reliable and (b) saves power but (b) is only really useful for archiving - which is what I purchased it for. From the outset (b) revealed a problem. One of two identical (hitachi) disks would not spin back up again unless (b) was power-cycled. This turned out to be due to a difference in firmware on one of the two hitachi disks: nothing to do with (b). It wasn't critical at the time and (b) has been turned off for months as a project to come back to.

I'd set (b) up to use four disks as part of a LVM volume group (VG), leaving the buggy hitachi hdd (effectively) span down as a simple ext4 volume: if ever used you'd have to run a script to touch a file on it periodically to stop it spinning down. With (a) having a dead disk and new disks not arrived, I fired up (b) to discover not enough space left on the VG to get all of (a) onto it. I'd forgotten the buggy hitachi and added it to the VG as another disk. My bad. Now the yottamaster starts doing its thing spinning up/down disks but as the buggy hitachi is now part of a VG I can't "touch it" to keep it spinning. Naturally I never noticed while backing up (a) because it was writing to the buggy hitachi keeping it awake. Trying to read the data back was a different matter: the VG kept going offline and new disks kept getting created rather than the old ones waking up: for the life of me I can't remember if this was a thing originally or not.

Requirements change. I now want (b) to not spin down disks. There's no way to change it, except perhaps, after a google, some utility which only runs under windoze. I've created a win10 virtual machine (VM) on my PC and am hoping to attach (b) to it as a pass-through device in order to run this (undocumented, no help, dubious generic jmicron) "utility".

Summary:
The IcyBox approach looks to be your best solution. It has raid/jbod options (I never used). Just make darned sure whatever you purchase can run your HDD's 24/7 (much more reliable) and obviously get a suitable cradle(*) for your disks.

(*) Each new HDD came with a useless multi-language safety booklet. If you fold the booklet enough times, and cram them in the gaps, you can stop the slimmer disks sideward wobbling. Obviously this was a temporary measure because it's more important to get the data copied than wait for proper cradles. Do not then think to yourself, "hmm, I wonder if it's still possible to open the "push click to shut/open" door once shut?" Answer is, it isn't. Once I've verified all the normal backups occur over the weekend I'm going to have to shut it all down, extricate the enclosure and figure out how to get the door open without breaking it.

Statistics: Posted by swampdog — Fri Dec 06, 2024 9:32 pm



Viewing all articles
Browse latest Browse all 4873

Trending Articles