Jump to content

Darrel Dearth

Members
  • Posts

    5
  • Joined

  • Last visited

Darrel Dearth's Achievements

Noob

Noob (1/14)

0

Reputation

1

Community Answers

  1. Everything worked again after the rebuild finished. Must just be an issue with the version of unraid I was using. An array restart was needed after the rebuild like you said, and the dockers started working again. Also upgraded to v6.12.2
  2. Had the same problem once i updated windows. Online i found this... "If your unRAID folders are public, use 'guest' as username and '1234' as the password and tick the 'remember my credentials'" However, What i did that worked for me was just enter the name of my server (Tower) as the user, and my root user password as the password which worked. Then just click "remember my credentials" so you dont have to do it again every restart.
  3. Ok I will once the 2 servers finish their rebuilds of the swapped data drives. Hoping they just start working once the rebuild is complete 🤞
  4. I have 2 servers which have 2 parity drives and 1 data drive (zfs) in each. I stopped the arrays and swapped the single data drives for larger 18TB drives in both servers, and now both servers say "unmountable: unsupported or no filesystem" while the data sync process is still happening in the background. The "Replaced" drive are usually supposed to be emulated during the data rebuild (and if i put my mouse over the orange triangle it does say drive is emulated), but the emulation is not working and all the dockers are down. The dockers tab just shows "Docker Service failed to start.". Is this problem normal when only using 1 data drive even if it has parity? I was trying to get the servers running with small drives then switch to a bunch of 18tB drives now that i had everything working properly on both servers.
×
×
  • Create New...