mbc0 Posted February 7, 2023 Share Posted February 7, 2023 Woke this morning to find all my appadata & dockers gone. Rebooted still the same. I have backups so I decided to build a new cache pool with 2 new nvme drives, I can mount 1 and format ok but when I try to add a 2nd the pool is unmountable and will not format. Any ideas how I can resolve this please? Diags attached unraid1-diagnostics-20230207-1053.zip Quote Link to comment
mbc0 Posted February 7, 2023 Author Share Posted February 7, 2023 (edited) Also, how do I recover all my docker templates from the flash drive please? I have the docker img still Edited February 7, 2023 by mbc0 Quote Link to comment
JorgeB Posted February 7, 2023 Share Posted February 7, 2023 Feb 7 10:51:59 UNRAID1 emhttpd: shcmd (729): /sbin/wipefs -a /dev/nvme1n1 Feb 7 10:51:59 UNRAID1 root: wipefs: error: /dev/nvme1n1: probing initialization failed: Device or resource busy Device is reporting busy, reboot and try again. Quote Link to comment
mbc0 Posted February 7, 2023 Author Share Posted February 7, 2023 Hi, I am running on a single cache currently as I needed to get up and running, I rebooted 3 times and tried to mount/format with the same result before posting here so maybe it is something else? If I try again later do you think I could risk causing a problem with the data on the single cache drive? Many thanks! Quote Link to comment
JorgeB Posted February 7, 2023 Share Posted February 7, 2023 Something is using that device not allowing it to be partitioned, but if a reboot doesn't help don't know what it could be. Quote Link to comment
Solution mbc0 Posted February 7, 2023 Author Solution Share Posted February 7, 2023 OK, Resolved, Not sure why I lost the docker containers and appdata but it is what it is, if it happens again I will download diags and investigate. Unraid got hung up on one of the NVME drives that used to be a pool called cachetwo, I had removed the pool cachetwo made a new config and used that drive as cache instead as a single cache drive just to get up and running. I then created another pool called cachetwo using one of the drives that used to be in the cache pool. Even though I was writing to the path /mnt/cache Unraid was writing to the drive in the cachetwo pool! I removed cache pool & cachetwo pool, re-added cache using 2 drives and cachetwo using 1 drive and now all running as normal. Quote Link to comment
mbc0 Posted February 7, 2023 Author Share Posted February 7, 2023 Ever seen this before @JorgeB ? Quote Link to comment
JorgeB Posted February 7, 2023 Share Posted February 7, 2023 Yeah, didn't notice before, device was already part of a pool: Data Metadata System Id Path RAID1 RAID1 RAID1 Unallocated Total Slack -- -------------- --------- --------- -------- ----------- --------- ----- 1 /dev/nvme1n1p1 100.00GiB 1.00GiB 32.00MiB 852.84GiB 953.87GiB - 2 /dev/nvme0n1p1 100.00GiB 1.00GiB 32.00MiB 830.48GiB 931.51GiB - No wonder it was busy 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.