Jump to content

andyjayh

Members
  • Content Count

    173
  • Joined

  • Last visited

Community Reputation

0 Neutral

About andyjayh

  • Rank
    Advanced Member
  • Birthday 05/23/1970

Converted

  • Gender
    Male
  • Location
    Sussex, England

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks both, very much appreciated your help with this I think I am now back on the road to recovery, drives formated and data being moved back with no errors showing
  2. I think I have found the re-format answer; Stop the array. Main, Cache Device, Change the format type to what you want. If its already what you want and just want to reformat it, then: Change it to anything else. Start the array. Format the drive Stop the array Change the format type to what you want Start the array Format the drive However, when I stop the array and go to change the format I only have auto, btrfs, btrfs encrypted. Should I chose the auto or encrypted? Worried that encrypted will take ages or impossible to back out of?
  3. So not going particularly well, to be expected given the corruption I guess. I have set appdata and system to not use the cache drive and kicked off the mover, expecting it to then move the data off the cache drive. This doesn't work and I see warnings in the log so I am assuming moving the data off is a non starter and I'm going to rely on backups as I'm using CA backup for appdata. Therefore I think what I need to do now is; 1) Re-format the cache drives 2) Re-create the docker image 3) Restore the appdata via the CA backup 4) Reinstall the docker apps Is that the right process? I'm also failing to see how I format the cache drives, sorry, probably being dumb here again....
  4. Ah ok, thanks. Very much appreciate the help and apologies for my level of dumbness with this one..... 🙄
  5. Ok thanks. The reset was partly where i was getting confused, I was thinking that I needed to resolve the issues via the scrub and then I would reset. Obviously misunderstood, my bad. I was just looking into backup now so at least I'm doing something right... To be clear then, do I reset the drives before the backuo, format and restore? Many thanks
  6. I have a pair of Samsung SSD drives for my cache running on btrfs file system. These primarily run my Dockers, Plex, Sonarr, Radarr, nzbget & tautulli. THis setup has been running well for over a year with no problems. A month or so ago I installed UniFi Controller and Video dockers and not sure if this was the cuase but it is certainly where my troubles began. I have since removed the UniFi dockers and migrated over to a Cloud Key. The issue is some write issues in the past that have caused csum errors on the drives. I started a thread under apps/docker initially as I thought the problem was with the docker image; So with some help I ran the btrfs stats command and I could see the write errors; [/dev/sdl1].write_io_errs 7 [/dev/sdl1].read_io_errs 0 [/dev/sdl1].flush_io_errs 0 [/dev/sdl1].corruption_errs 0 [/dev/sdl1].generation_errs 0 [/dev/sdk1].write_io_errs 9 [/dev/sdk1].read_io_errs 0 [/dev/sdk1].flush_io_errs 0 [/dev/sdk1].corruption_errs 0 [/dev/sdk1].generation_errs 0 Advice was to look at the following thread and follow the suggestions; From here I could see the write errors and I replaced the cable for the SSD's. It's at this point I get a bit stuck as to how to fix the issue? Each time I run a Scrub command either via terminal or via the gui, it aborts immediately. I have actually now purchased a new pair of SSD's but I am assuming this is a btrfs issue as no reporting is given to errors on the f/s so I want to avoid in the future. I would really like to fix this though. Latest diag report attached. media-diagnostics-20190416-1446.zip
  7. I'll start a new thread for this as it's clearly an issue with my Cache drives and so far I can't resolve and got completely stuck with how to fix the issues on the drives.
  8. Ok thanks for this. I've created the following script as suggested in the linked post; #!/bin/bash btrfs dev stats -c /mnt/cache if [[ $? -ne 0 ]]; then /usr/local/emhttp/webGui/scripts/notify -i warning -s "ERRORS on cache pool"; fi Ran with the following output; [/dev/sdl1].write_io_errs 7 [/dev/sdl1].read_io_errs 0 [/dev/sdl1].flush_io_errs 0 [/dev/sdl1].corruption_errs 0 [/dev/sdl1].generation_errs 0 [/dev/sdk1].write_io_errs 9 [/dev/sdk1].read_io_errs 0 [/dev/sdk1].flush_io_errs 0 [/dev/sdk1].corruption_errs 0 [/dev/sdk1].generation_errs 0 /tmp/user.scripts/tmpScripts/btrfs check/script: line 4: syntax error: unexpected end of file Not quite sure about the syntax error? As expected, some write errors. As suggested in your linked post this is most likely a cable fault so until I can purchase another pair of cable I should try and reseat them? Once I do this the only thing to do is scrub the cache drive? I can do this via selecting the primary cache drive and running the scrub tool? I've done this and it's reporting no errors.
  9. Ok, thanks for looking. I've restarted the server and uploaded a new diagnostics file. Learning curve but I now understand that what I was seeing in the Dashboard was that my Docker Log was filling up and I suspect this is causing part of the issue, don't know if this was able to take one of the cache drives offline and therefore caused the corruption I am now experiencing? I need to understand why my log file is now filling up so quickly when my server has in the past been up for months at a time without issue. UniFi Controller and Video are the new Dockers so I suspect one of these is writing large amounts of log file entries? media-diagnostics-20190326-0944.zip
  10. Apologies for not doing this yesterday but here is my diagnostics report. I've also just noticed in my Dashboard that it is showing the 'Flash Log Docker' as 100% on the second of the three graphs! Not sure where this is located but none of my drives are full or near full including the flash drive. media-diagnostics-20190326-0843.zip
  11. Brilliant, I’ll do that as soon as I get back home [emoji106] Sent from my iPhone using Tapatalk Pro
  12. Thanks, I hope not [emoji106] Good idea and I’ll sort that when I get home. Sent from my iPhone using Tapatalk Pro
  13. Eek, sounds bad Thanks for your help though.
  14. Hmm, not great. Did the above and what I am seeing in the Sys Log now is; Mar 24 21:54:59 Media kernel: BTRFS warning (device sdl1): csum failed root 5 ino 17093788 off 4571136 csum 0x3235bd95 expected csum 0x00000000 mirror 2 Mar 24 21:54:59 Media kernel: BTRFS critical (device sdl1): corrupt node: root=7 block=93667393536 slot=86, bad key order, current (18446744073709551606 128 986823262208) next (18446744073707454454 128 986826604544) When I go to the WebUI it is cycling between a message about repairing the database and then server startup.
  15. Ah I see. So leave the appdata well alone in this case. Will give this a go, thanks.