-
BTRS switched to "read only"
So the event did actually occur on the 8th. I hesitate because I know I will be left with non running containers and even worse Downtime lol. I'm just trying to be as careful as I can since if I stop them, I have no functionality with the server. Is it possible that the diag file shows what could have occurred since nothing has changed since?
-
BTRS switched to "read only"
My apologies. Should have thought of that. Here's the file and I hope I at least got that right. bigbertha-diagnostics-20230312-1220.zip
-
GullwingV77 started following Parity drive in error again - New drive, two fails. and BTRS switched to "read only"
-
BTRS switched to "read only"
Hello all, I’ve recently run into this apparently well-known issue with btrfs where it has hit 100% filled and has changed itself to read only. I already took these steps: https://forums.unraid.net/topic/61497-solved-cache-disk-full-shows-plenty-of-free-space/ and these... https://www.reddit.com/r/unRAID/comments/j99brd/docker_failing_with_readonly_file_system_error/ https://www.reddit.com/r/btrfs/comments/hwpcaj/full_filesystem_btrfs_read_only/ Unfortunately the (btrfs balance start -usage=75 /mnt/cache) 10 through 80 incrementing by 10 did not fix anything. Currently my dockers are still working except one. I turned a non-critical one off and tried turning it on and as expected just like in another forum that i cannot find now i get "error code 403". Then I tried deleting a docker and got "Image cannot be deleted, in use by other container(s)". Opened the terminal for unraid and gave the command "docker rm (docker container) which then told me that the filesystem is read only and how i found these articles to read. These forums are saying stop all dockers, turn docker off and remove the docker.img to have it reinstall a fresh image. https://forums.unraid.net/topic/103534-solved-docker-read-only-file-system/ https://forums.unraid.net/topic/54533-624-cache-drive-reporting-quotno-space-left-on-diskquot/#comment-532931 But they also say that I need to reformat my ssd. So before i stopped my critical containers like plex, I thought I'd ask for some direction as to what i really should do since there appears to be confusion in these posts. I’m wondering why btrfs is the default file system if it’s so fragile and as Jorge B says :"Yep, btrfs is kind of high maintenance, hopefully this specific issue should be fixed once we go to kernel 4.14." Since we are way past that kernal and this problem persists, if I need to reformat the ssd, 1) what’s the best way to do that and 2) how do I choose a better file system that’s not so high maintenance?
-
Parity drive in error again - New drive, two fails.
We have been running the server for a month now, including a successful schedule parity check. Something so simple that I didn't even think of. Have just finished configuring the backup server using the same disks and, of course, setting the parity drive to not spin down. About to start the data transfer for the first backup. Many, many thanks for the solution.
-
Parity drive in error again - New drive, two fails.
Thanks so much. We'll try that.
-
Parity drive in error again - New drive, two fails.
I don't know what is going on after two failures. The drive I'm using for parity might not be the correct one or something else. This server has taken me nearly 2 years to get built, all new Supermicro 24 bay hardware, and I still haven't been able to use it consistently. Any suggestions would be very helpful. My first server has been running for several years straight without a single problem and it was all used hardware, but using Windows Server Essentials. I'm using a brand new 18tb drive from Seagate for the parity, Seagate 18TB 7200RPM Exos SATA 3.5" Enterprise Hard Drive ST18000NM000J. I went through the "normal" and suggested installation prep for the drive each time. Pre clear was successful and so was parity sync. 1 week after both times the parity showed up as disabled. Been told about the third power pin on these newer drives which sorta makes sense for how they act, but then again it starts out good and runs fine for a week. These ones will actually spin down per the schedule I set but the older drives that don't have this extra pin in my other server have never spun down. I do have the diagnostic zip file, and have attached the .zip file below. Intend to add a second parity drive as well, once we can get the first one up, running and staying happy. Begging for help, suggestions, anything but calling me an idiot for getting in over my head. I love the functionality of unRaid - would just like to get the parity(s) working so my data is secure. bigbertha-diagnostics-20221214-1843.zip
GullwingV77
Members
-
Joined
-
Last visited