sauvagii

Thanks, I'll do that. It's strange since it went through a full preclear and rebuild and no issues prior to this.

Diagnostics attached. dl-net-diagnostics-20171216-1119.zip

Hi, I've recently (~2 weeks ago) replaced a drive in my array. Over the last couple of days, after a few days away (where I had the server powered down) - on reboot, it's showing the new drive as disabled. I did a smart test, and it showed no errors. When I first discovered this I googled the error (afraid I don't recall what it was at the time, stupid I know) but the suggestion was there was a loose or faulty cable - I've replaced this and still get the errors in the log attached. I've started in maintenance mode and checking the filesystem just in case. Just to be clear, the new drive was rebuilt successfully and running fine for about a week or so until power down (clean) and only developed this issue on boot after my return from a work trip. It's connected to the same motherboard port as always. unraid_log.txt

Great, thanks!

So once I have let this scan with the new selections, is it safe to delete the ones marked as missing ones?

Yes, from CP Home. I did the adoption process, it said 'adoption successful' at the time, but still says all of my folders are missing. I assumed when the message about successful adoption came up all was OK, so I logged out and didn't check again as I was away from home for a few days so struggling to remember if I missed a bit!

I'm having problems where the Crashplan app cannot locate my existing backup sources, they all show as Missing. I've tried adding paths to each but they don't seem to have any effect - have I missed something completely? (it's highly likely)

Thanks, did that this morning - looks like it's running OK now.

Been getting a lot of errors lately of mixed types but seem to be all pointing to my cache drive (SSD) but the SMART tests are apparently completing without error. I'm working away from home at the moment so not getting much opportunity to look at it unfortunately. This is the current log after a reboot this morning: After a while, the log just fills up with shfs_write/BTRFS Read Only filesystem errors continuously. It appears to be the cache SSD based on:

Worked perfectly, thank you!

Thanks! I thought that was what I should do but was just a bit wary... Fingers crossed it goes smoothly!

Hi, I currently have a system with 1x3TB parity drive, and several data drives, the largest of which (3TB) is starting to report regular errors so I'm looking to change this out before it fails. However, I have only 2x 4TB drives to go in the system, so obviously I can't just add one as a data drive as it would be larger than the parity. I wanted to check that I had this correct as I've not had to swap anything out previously except a failed cache SSD. Is the only option to me: 1 - add new drives into the system 2 - first assign as new parity drive to the new 4TB 3 - allow parity to rebuild 4 - when complete, unassign the failing 3TB drive and assign the second new 4TB in it's place The reason I'm a little cautious is that I wonder if the increased load generated as a new parity drive is created could accelerate the failure of the dying 3TB, and that I could be left with only a partially built new parity drive, and a dead data drive. I get regular error notifications if the drive is under load. I could be totally wrong about this, but I've really had no issues in the two years my Unraid box has been set up so I may be misunderstanding the process. Is the above the best way to go about the replacement? Reading through some of the guides I'd found it does look like it?