VL4DST3R

The first one is indeed the one I lost, but I'm not sure it makes much difference, they all seem to be the same. I have used Photorec but it gives all files generic names and ruins any folder structure. I'm interested in only a few particular files i have not yet backed up, not necessarily the entire thing, so keeping the…

Update: Turns out the latest firmware update was INDEED the issue, and going back solved the issue. From what I understand update 13 will be pulled from the update servers so other people won't end up in the same situation as me and OP, but supposedly no other updates are planned to come. Sadly, in my scrambling last night…

Hey, sorry for taking a while to reply, I did as you suggested and got the following: Note: the setup I had was drives 1-3 in a JBOD and drive 4 by itself, so I assume that's why the first command failed. ~ # mdadm -A /dev/md0 /dev/sd[abcd]3 mdadm: superblock on /dev/sdd3 doesn't match others - assembly aborted ~ # mdadm…

Thanks, I will try what you suggested and report back.

To provide an update: I've been talking and debugging this with someone from support on the side and their theory so far is that one of the drives somehow kicked the bucket and is causing this (which yes, apparently can happen, more about this below). However I still find this very odd for a number of reasons, the main one…

Thanks for the reply. I don't even use WebPublisher, so unless I'm missing something, that shouldn't interfere with anything, I don't think. The LEDs do come on, indicating activity and however many drives are inserted into the bays, but you never hear the beep that indicates a successful bootup with them connected, at…

Hi, i have encountered the exact same issue after upgrading to the latest firmware V5.21(ABAG.13) on my Nas542. The device does not boot at all unless all drives are removed. All drives are otherwise working fine and did so up to the firmware update. If i connect them to the NAS after it booted they get recognized inside…