Hi.  Not sure this is the right form and if not,  I will move. 

 

I have UnRaid, which I love, and I recently upgraded my system to handle VMs, and I bought a Samsung 850 EVO 250GB SSD drive to host the VM files, and created a Win7  VM.  It runs great for maybe 1-5 days and then the hard drive seems to go into a read only mode.  I can browse stuff on the drive, but cannot change anything.  of course the VM crashes because its read only.  I have to reboot UnRaid (I reboot within Unraid GUI), and when it comes up everything is fine, and then a few days later it happens again.  Any ides on what I should check?

In general, when a file system is changed to read-only, it's almost always because corruption was found in the file system.  So I would run the appropriate section of Check Disk File systems on the drive.

Thanks!  It is btrfs, so I ran scrub, with the default -r, and it found no errors:  total bytes scrubbed: 68.25GiB with 0 errors.  Anything else to try?  It's a smaller drive, so I can move th data off and rebuild the drive.

 

You can try a btfrs check, array has to be started in maintenance mode:

 

btrfs check /dev/sdX1

 

X=your cache letter

 

If it needs repairing, then:

 

btrfs check --repair /dev/sdX1

Thanks.  I tried that, and it didn't find any problems either.

I copied off the data, reformatted in xfs, and put the data back on.  Hopefully it will behave better now.

That would have been my suggestion as well. Not sure why but I recall seeing many issues like this.

 

In my opinion BTRFS should be for the docker.img only and the actual drive(s) formatted as XFS as it is more mature.

Thanks.  So I switch it over to XFS it ran fine for a few days, and then it went into read-only mode again.  Any other ideas?  Could it be a bad drive? 

I'd check to see if there is a newer firmware for your drive.

When I was looking at purchasing an SSD ~1 year ago, there was discussion about the Evo getting or needing updates for some issues.

I cannot say that this is related, but certainly worth checking.

I'd assume that there is something wrong with your drive or controller.

Is it set to AHCI in the BIOS?

 

I have a 512 Pro Samsung drive and do not any of these issues, and it is formatted to BTRFS.

I have the 850 EVO, and don't see new firmware for that, but I will check.  I will also check on the AHCI, but I am at work and can't check until I get home.

Post your diagnostics file, it should shed some light on why it's going into read-only at this point. It could be a bad cable, controller, port, etc.

Here is the diagnostic file. Thanks so much for your help!

tiki-diagnostics-20160404-1244.zip

Was that diagnostics taken from the system AFTER the SSD was marked read-only but before you rebooted? I dont anything in the log related to a read-only file system.

 

On another note, what are your hardware specs? I see only a handful (4 or 5) devices installed (HDD/SSD) but it's all the way up to ata14... im thinking the SSD is on an SATA add-in card and you should move it to a motherboard port.

it was run after the reboot when everything is running fine.  I can wait until after it happens again and re-run it.  I have replaced drives over the years, so maybe that accounts for why its up to 14.  I only have 5 drives in there now including the parity and cache drives.  I will check if its on the sata card or motherboard and if its not on the motherboard, I will move it there.

 

Its running in  PowerEdge T20 with with a Xeon E3-1225

So I put the SSD on the motherboard SATA port and one of the hard drives on the add-in cards sata port, and the hard drive then went down a while later.  So it appears to be the card.  I have ordered a new Sata card.