dannygreg

Members
  • Posts

    5
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

dannygreg's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Fair enough! Fwiw it turned out to be a negotiation issue on my switch rather than the NIC. Fixed it to 2.5G and have a solid link on the latest Unraid release.
  2. Hey folks - @ThatDude especially, I've blacklisted the r8169 driver as above, and looking at the logs appears to show the correct driver being loaded: r8125 2.5Gigabit Ethernet driver 9.005.01-NAPI loaded However, I'm only seeing a 1G link. Were there any other tweaks that were required?
  3. Perfect, thanks. Wiped and done the reformat dance. Back up and running!
  4. That would make sense. What's the best way to reformat in a way that Unraid will expect?
  5. Hey folks, I had a cache drive go bad a couple days ago, this resulted in the btrfs failure mode of a read-only filesystem. I had plenty of headroom in the pool so my initial thought was to just shrink the pool down from 4 to 3 disks. This didn't help and still resulted in the filesystem being mounted as readonly. I just put a fresh drive in (same size as before) and, after setting the pool back to 4 disks I was still seeing the same result. I ran `btrfs fi show` and was greeted with our friend `*** Some devices missing`, despite also seeing the new drive added to the pool. This made sense in retrospect, as the GUI had performed an addition, not a replace. I stopped the array and mounted the pool in degraded mode. Deleted the new drive and ran `btrfs replace start 6 /dev/sdp1 /mnt/cache` (/dev/sdp1 being the new drive). This didn't give an error, which I thought was great news… until I ran `btrfs replace status /mnt/cache` and saw the output `Never started`. No matter what I do - I can't convince btrfs to replace the dead drive. At this point, I'm more than happy to nuke the cache entirely and build a new filesytem. Everything is backed up and it wouldn't take long to copy it back over and rebuild the Docker image etc. etc., mostly just looking to get back up and running as quick as possible. Would love any suggestions, either for nuking the entire cache, or getting a replace operation to run. Here's the output of `btrfs fi show`: Label: none uuid: b0707364-0ca2-443d-a5cf-ca6cf64e5bbb Total devices 4 FS bytes used 101.96GiB devid 3 size 232.89GiB used 90.03GiB path /dev/sdm1 devid 4 size 232.89GiB used 60.00GiB path /dev/sdn1 devid 5 size 232.89GiB used 91.03GiB path /dev/sdo1 *** Some devices missing