Hello,

I have months/years of problems with my server that I am slowly trying to diagnose. My lastest efforts have been to replace an older sata SSD with a new NVME one for my dockers and eventually VM's (dont have any VM's yet).

 

I told mover to move everything off the SSD onto the array. Mover bugged out and stayed "working" forever. I used MC and manually moved over the data. Something is up though, the dockers are all funky. I may have lost everything. Not the end of the world.

 

I am now in process of removing the SSD from the Pool and adding a new NVME to the pool but I keep getting other problems. The Pool is zfs with compression and autotrim set to on. 

Every time I start my array I get: "Unmountable: Unsupported or no file system"

I have cleared and formatted the drive, and cleared the Pool. I even deleted the pool and made a new one with the same name. I added back the old drive plus the new one, and it auto mirrored (it should have zero bytes on it, but w/e) and appeared to work. I then remove the old drive from the array and it goes back to 'Unmountable'.

 

Running "zpool import" gives: 

I dont really care about the data. I just want the drive to work, so I can put the data back on it. I have many backups using 'ZFS Master'. The reason for running a zfs cache drive is to do daily/weekly/monthly backups onto the single zfs hard disk in my array.

The only thing I can think of is I still see the new NVME drive under "Historical Devices" where I had it unmounted since installation a while ago (never used, never put data, never mounted).

 

Any ideas?

 

I will eventually open another topic to discuss the myriad of troubleshooting steps taken over the past few months to try and get my server to stop randomly crashing every few days. I am hoping a bad drive running my dockers is the culprit.

Diagnostics included. gigavault-diagnostics-20240403-1051.zip

 

Thank you!

Not clear to me if it new pool is one or two devices, but if the pool can be formatted try this, unassing all pool devices, start array, stop array, assign one or both pool devices, click on the pool, then click "Erase", select the filesystem you want, start array, format the pool, any issues post new diags.

I would like the new pool to be 1 device.
Snips showing each step below:

Current config, array started.

 

Crazy, I don't think I missed this before, but found this as I was stopping the array for the 20th time today lol. 

 

I formatted, and its now apparently working. I knew it should be this easy, it has been this easy in the past. I don't know why the option wasnt there before, or why I missed it (more likely). I did format a few times while it was unassigned, just havent been able to do it when it was in the pool and assigned.

 

Transferring appdata and system back to array from other SSD using mover. Took about 15 minutes vs the 18 hours (before I gave up) on the old SSD. Hung up transferring back just now, so I let mover run overnight. Server crashed again during the night's auto-restart but recovered and Parity was going again I guess. Cancelled that, used MC to transfer over the system share that mover missed. Turned off the array for docker shares, and all seems to be working, except for 1 of my dockers. No biggie, just restore from a backup.

 

Sorry for the false alarm, dont know why it wasnt there or I didnt see it.