cinereus

Members
  • Content Count

    261
  • Joined

  • Last visited

Community Reputation

10 Good

About cinereus

  • Rank
    Member

Recent Profile Visitors

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

  1. I strongly recommend moving to henryw3's docker.
  2. I think I got it working again. Although does anyone have any idea why my cache randomly corrupted itself in the first place?
  3. Okay it came up after 25 mins. I still don't have an appdata or a system share so unsure how to restore my appdata backup before re-installing dockers....
  4. And under "Reformatting a cache drive" I have no idea what step 4 is asking me to do: "Set all shares that have files on the cache and are currently not have a Use Cache:Yes to BE Cache:Yes. Make a note of which shares you changed and what setting they had before the change" I have two shares that are "Cache: Yes" but obviously no shares have files on cache as there is no working cache at the moment.
  5. Thanks all. It's worth noting that my appdata and system shares have completely disappeared. Will these steps automatically re-create them? And obviously I've lost all data that was on cache? So the precise order of steps I need to follow is as follows? 1. Reformat cache? 2. Recreate docker.img? 3. Copy appdata 4. Reinstall dockers?
  6. What's the correct order? Reinstall before copying appdata or after?
  7. Thanks, so what's the process exactly? Reformat cache and then just copy paste appdata folder over? Then work out which dockers I was actually using and reinstall them one by one?
  8. Yes but not fussed if I lose them. Mainly just want to get the system up and running asap. It was just that the Docker screen said the docker.img was lost too.
  9. Not sure. How do I tell? From my screenshot above it seems I might have had system on there too? What's best practise for restoring?
  10. @Squid @itimpi "Sorry, could not find valid secondary superblock Exiting now." What now? No idea what it had an issue in the first place...
  11. It's called "sdi". Does that mean a working command is xfs_repair -v /dev/sdi ?
  12. Thanks. Just noticed cache is "Unmountable: No file system" There's a lot of chat about "If the file system is XFS or ReiserFS (but NOT BTRFS), then you must start the array in Maintenance mode, by clicking the Maintenance mode check box before clicking the Start button. " But I assume the cache is not part of the array so I can just go ahead? It seems the general command is "xfs_repair -v /dev/md1" but how on earth do I find what /dev/??? is my cache drive?
  13. Now getting "Docker Service failed to start." And under Settings>Docker:
  14. Sorry took me a while to work out how to access the zip file. SMB wasn't up. fs-diagnostics-20210407-2220.zip