philliphs
Members
-
Joined
-
Last visited
-
Docker RAM Allocation is stuck at 9.29GB even though total RAM usage is 4.93GB. Confirmed with htop on console around 4.9GB RAM is used. Even though after restart, no docker is turned on, RAM allocation shown in dashboard remains the same
-
Hi, I read that Unraid 6.12 ZFS support converting single ZFS disk in a pool into mirrored pool up to 3 devices. When I tried to convert my single ZFS to mirror pool with 2 devices, it produces "Wrong pool state. invalid expansion" error. What I did was: 1. Stop the array 2. Increase the slots of the cache pool from 1 to 2 3. Assign the second device to the second slot. 4. Start the array I wonder if that's how you are supposed to do the ZFS conversion from single disk to mirror vdev in unraid? FYI, the pool only consist of 1 vdev of 1 single disk
-
Yes. Emulation was supposed to happen, but it didn't for that specific docker. I suppose it had something to do with the cache system. I will dig a bit more when I'm replacing another of my ironwolf soon. Funny I have mixed disks of WD red and Ironwolf, I had bad sectors on 3 Ironwolfs (RMA was easy) but none on WD red.
-
I have a weird case last week. My unraid pool is set up with 1 parity + 3 disks. There is extra one cache disk Share "CCTV" is set up in the pool, with cache set to "YES". I am running docker ShinobiCCTV with recording set to /mnt/user/CCTV So the recording will be saved in cache disk, with mover run every night. Disk 2 on pool is having bad sector, and I decided to RMA the disk. I removed Disk 2, and run the pool from parity drive with missing Disk 2. The ShinobiCCTV Docker decided that it cannot find the CCTV share path, resulting in crash. When I changed the recording location map to /mnt/user0/CCTV thus bypassing the cache it worked fine. The new replacement disk came, restored the content, and set back to /mnt/user/CCTV and everything runs normal again. Did I do something wrong, or with missing disk, dockers cannot access the cache drive?
