I just received a machine (Dell Precision 5820) today and moved my drives on it ( I don't have much: 1x4TB and 1x1TB). I also added a new drive at the same time (1x12TB) but I don't think this should affect anything  (correct me if I'm wrong).  So, after opening the PC I mistakenly added the 12TB drive to the array and started it. I guess since it wasn't formatted, it was unmountable. So I stopped the array, removed the drive, and started Unassigned Devices Preclear on it. Because I removed the drive, I was getting errors starting the array since the config had changed (from my understanding -- I could've gotten this wrong). So I went into Settings -> New Config and applied. The array is now starting, but I'm not seeing any shares and Docker is showing as Docker Service failed to start.

 

I'm sure I screwed up somewhere but here's some commands I ran from looking at other posts with similar issues:
 

1) running   fdisk -l /dev/sdb  and   fdisk -l /dev/sdc:

root@Tower:~# fdisk -l /dev/sdb
fdisk: cannot open /dev/sdb: No medium found
root@Tower:~# fdisk -l /dev/sdc
Disk /dev/sdc: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: ST4000DM004-2CV1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 2F55BC1F-5623-4C3F-B71A-48541D75C766

Device     Start        End    Sectors  Size Type
/dev/sdc1     64 7814037134 7814037071  3.6T Linux filesystem

 

 

2) zpool import

root@Tower:~# zpool import
no pools available to import

 

Hopefully this is enough information for someone more knowledgeable to help me out!

 

tower-diagnostics-20240924-2053.zip

Edited September 25, 20241 yr by BoneAppleTea

Sep 24 16:29:59 Tower root: sh: line 1: /usr/local/bin/shfs: No such file or directory

 

The disks are mounting, but this is a new one, try booting with a stock install, then just assign both disks and post new diags after array start.