• Posts

  • Joined

  • Last visited

Everything posted by sonofdbn

  1. I don't use mover at all (so not really using cache disk as a cache). I move files manually. But the cache-prefer share idea is excellent. I only "discovered" cache preferences a short time ago and didn't have a good idea of how they could be used. I didn't even know there was a Cache Minimum Free setting - but what happens when you hit the minimum free (ignoring for this discussion any cache-prefer shares)? Does this trigger a warning (and continue writing into the "buffer") or does it just act like a hard limit to the cache drive size?
  2. Can you give more details on btrfs restore? If the pool is unmounted, how do I access the drives? Or do I unmount the drives and then mount them individually as - I don't know - unassigned devices?
  3. Cache-only shares are a bit messed up because I set some shares up before I understood how the cache could be used. In reality, I have /appdata, /domains and /isos there, as well as torrents. And, yes, torrents are also seeded from cache (didn't want to keep an array drive spinning). So that's probably the cause? I thought I left myself a reasonable margin (50GB) but perhaps I wasn't paying attention. I also left too many seeding on the cache because the latest versions of unRAID unfortunately slowed down file transfers from cache to array, so I didn't do transfers out as often as I used to. Bottom line, though, is that a full BTRFS cache drive pool can be a pretty bad problem.? Is there any notification that I could have enabled? My experience is Windows, and there I usually get a disk is low on space message.
  4. So it sounds like I've pretty much lost the data on the cache drive, although I might be lucky with some files (and it would take forever to work out which files are OK). That being the case, I think I should just try to recreate the cache drive from scratch. A real pain, but doable. That being the case, is there anything wrong with the drives themselves? And do you think it was the corruption that led to the cache drive being full or the other way round? Because if it was the other way round, I need to monitor what goes on in the cache drive more carefully in future. If the corruption was the issue, any idea what caused it?
  5. Here's /var/log/syslog. There's an earlier syslog.1 as well, but it's 15MB. Let me kno w if you need that as well. syslog
  6. Just to add: the cache seems to be mounted as read-only, so I can't delete anything. Is there a way to set it back to "normal" and allow me to clear some space?
  7. I can access the cache, but copying files usually produces errors. For example, this is what I get when I try to copy \appdata\MKVToolnix to a local drive: Trying to copy the same folder to /mnt/disk4 on the server via mc on console produces an error in the same place (?): The other weirdness is that some files seem to go offline and then online again very rapidly, and there's no visible copying progress. Unfortunately I can't seem to capture the Teracopy log as text, but here's a screencap: Some files do copy OK, but backing up what I can would be almost like trying to copy each file individually and seeing which ones work. So I'm a bit stuck at the moment.
  8. Thanks for looking into this. Here are the diagnostics. (It's getting late here; I'll be back in the morning.)
  9. Unfortunately no joy. I went to the link you provided, and tried the first two approaches. My cache drives (btrfs pool) are sdd and sdb. 1) Mount filesystem read only (non-destructive) I created mount point x and then tried mount -o usebackuproot,ro /dev/sdd1 /x This gave me an error mount: /x: can't read superblock on /dev/sdd1. (Same result if I tried sdb1.) Then I tried mount -o ro,notreelog,nologreplay /dev/sdd1 /x This produced the same error. So I moved to 2) BTRFS restore (non-destructive) I created the directory /mnt/disk4/restore. Then entered btrfs restore -v /dev/sdd1 /mnt/disk4/restore After a few seconds I got this error message: /dev/sdd1 is currently mounted. Aborting. This looks odd (in that the disk is mounted and therefore presumably accessible), so I thought I should check whether I've missed anything so far.
  10. I'm using ECC RAM, so I didn't run memtest. My problem is how to backup the files on the cache drive(s). I've tried various things to copy files off the drives, but everything I've tried throws up errors. (I've tried mc via SSH and Teracopy from my Windows PC, WinSCP and a few others.) I've also tried the CA Appdata Backup plugin, but it just flashes briefly that it's working and there's no error message, but the output folders are empty.
  11. My Win10 VM suddenly got disconnected, and when I checked the server dashboard, the log was at 100%. I downloaded a diagnostics file at that point. Then I rebooted and as expected, log was cleared, but now Fix Common Problems reports "Unable to write to cache" and "Unable to write to Docker Image". (I took a quick look at rTorrentVPN and while it starts, the rTorrentVPN GUI shows no activity, not even a list of torrents.) I have attached the post-reboot diagnostics file as well. What should I do next? Second - First -
  12. And now this endpoint has stopped completely for me.
  13. You can always add the variable manually. The option to add variables, ports, etc. is at the bottom of the settings screen.
  14. For me it's working, but speeds fluctuate a lot - sometimes stops altogether, then back up to normal. I'm using Sweden.
  15. Should I let the parity check finish? (The crash came roughly 50% of the way into the previous parity check.) Is there a possibility that the flash drive is corrupted? I did install a docker recently, about the time of the first crash. I haven't started it this time round. Don't want to name it and give it a bad rep when it might have nothing to do with the crashes.
  16. Fortunately I ran the syslog server tool as suggested - the server crashed again. This time I could ping, but no SSH. Also I couldn't see any of the shares, but my Win10 VM was still running. Weird? The GUI timed out with a 500 Internal Server Error. So I shut down the VM and then rebooted. I've attached the syslog, removing entries at the end which came after the reboot. My UPS is down, so those messages are not surprising. 192.168.134 is an Asus router. I have two Asus routers, one is the main one and one is configured as an access point (and also serves as a switch). I believe that internal IP address is the access point. The single Ethernet cable from the server is connected to the access point. unRAID came up again at 00:45 extract-syslog-
  17. Unfortunately the server crashed again. I noticed it when my Win10 VM disconnected (wasn't using the VM, but it was running in an RDP window on my PC). Couldn't SSH in to the server and couldn't ping it. So I've rebooted and parity check started automatically. I've attached the latest diagnostics (after rebooting) and the previous one for easy reference. From what I can tell, on Disk 3 the UDMA CRC Error Count hasn't changed. I'm wondering whether there's anything that can tell what cause the crash. So far, 4.8% into the parity check, there are no errors.
  18. Thanks for all the help. All done and seems to be OK. The disk was connected via a forward breakout cable to a SAS HBA and I was a little worried, having no spare breakout cable. Fortunately I found the last remaining SATA port on the MB and managed to use that with a new SATA cable. I'll watch out for more CRC errors, though.
  19. So should I do another parity check first? Then if that turns out OK, do a rebuild?
  20. Thanks for the quick response. OK, I cancelled the parity check and checked the cables, which seemed to be OK. I restarted but the disk still has an "x" next to it. (Weirdly I get a notification saying the array has turned good, array has 0 disks with read errors. While I get that if the disk is disabled but the array still works, doesn't seem like the state of the array should be termed "good".) If I need to restart the parity check, should I be writing corrections to parity? Diagnostics are attached.
  21. This morning I found my server unresponsive - seemed to be on, but couldn't SSH in and no response from pings. So I switched it off and restarted and it automatically went into a parity check. A few minutes later I got a messages for Disk 3: udma crc error count, then a message saying it was in error state, and warning that the array had errors, 1 disk with read errors. I'm assuming I should replace the disk. Is that correct? (Diagnostics attached.) Also, should I stop the parity check? Finally, if I replace this 4TB disk, can I replace it with an 8TB disk (which is the size of my parity disks)? For the replace, do I just put in the new one in place of the old one and rebuild?
  22. Couldn't get work units from F@Home, so went with RDP-Boinc. It's nice to see so many cores maxed out for once.
  23. Did you also do the last part? I missed that part initially, but after doing that AND clearing cookies, the Web UI worked.
  24. Thanks for the help. All done. Recreating the image was so much easier than I expected. I was worried because I had two instances of some dockers (named them differently of course), and was pleasantly surprised to see both listed in the previously installed apps list. Also took the opportunity to turn on log rotation.
  25. Thanks for looking at this. I'm trying to understand how docker.img works in the cache pool. In my case, docker.img sits inside /mnt/cache and is set to 20GB. So if I free up space by deleting some files in /mnt/cache, and also delete some containers to free up space in the docker image, would I then still have to recreate the docker image?