Extra Drive?

TrueNAS General
1

Hello. I’m running TrueNAS 25.04.2.4. I just moved everything from a smaller case to a larger case for more ventilation. I only have 8 drives in my NAS, sda thru sdh. When I checked the drives after booting, I noticed that I have an sdi drive; a 9th drive. It looks like the following:

extraDrive
extraDrive1348×244 23.4 KB

I don’t remember this drive being there when I first built my TrueNAS, or could it be the result of updating my TrueNAS version a few times? I don’t know. Any ideas why I might have an extra drive/letter?

Thanks.

2

Model is Virtual_HDisk0. Does that give you any clue as to what it could be?

3

That model doesn’t give me a clue at all at to what it could be. I have no idea. Maybe I’m not seeing something. My TrueNAS drive is an NVMe M.2 and my Apps drive is an NVMe M.2. The remaining 8 drives are spinning 6TB drives. That’s all the drives I have in my build.

I restarted to see what would happen, it’s now labeled: sde. This is odd.

sde
sde1351×249 23.5 KB

Any ideas on what may be occurring?

4

As already noted, the model is stated as “Virtual_HDisk0.” That suggests it’s, well, a virtual disk. Since you’ve given no information about the environment you’re running TrueNAS in, all we can do is guess. But a few of those guesses would include:

  • You’re running TrueNAS virtualized, and you’ve attached a (or another) virtual drive to the system
  • You’ve connected remote storage via IPMI
  • You’re using an IP-KVM that also provides remote storage
1 Like
5
  • My TrueNAS is sitting on the iron in a standalone full tower case. I have nothing virtualized and I’ve not connected a virtual drive to it.
  • 1 NVMe M.2 for TrueNAS; 1 NVMe M.2 for Apps; 8 spinning 6TB drives. No other drives.
  • I only have 1 App installed; ClamAV.
  • I’ve not connected any type of remote storage to it.
  • The motherboard’s onboard video DP is directly connected to the DP connection on my monitor. I do have a KVM, not an IP-KVM; the KVM has no storage (Avocent SV240DPH). I only have the KVM’s USB and audio cable connected to the motherboard - the USB is so I can use my keyboard through the KVM and that’s it. The Ethernet on the motherboard is connected to my layer 2 switch.
  • Seemingly a pretty simple build.
6

Guessing your screenshot is showing it not associated with a pool and a size of 0 B. You clipped a lot of info off.
Wild guess is you can just try removing it. Not sure how or why it was created.

7

@SmallBarky That screenshot is actually all of the info from that drive’s dropdown; I didn’t leave anything out. Before I try to remove this drive, if there is other information that you would like to see, I will screenshot and post. Just tell me where I need to go to get the screenshots.

8

You were missing the titles for the columns. I had to guess where you were in the menus on the TrueNAS GUI. On some, you can select and unselect what data shows. As long as my guesses were correct, you should be fine.

The only other thing I can think of is the BIOS or UEFI is where the virtual drive is from. I know it wasn’t from VirtualBox because I use that for menu references on all the different OS versions and the drives show the Model as that. I don’t know what software may show up as Virtual_HDisk

9

When I first built this computer and installed TrueNAS, I don’t remember this ghost drive being there. The only thing I’ve done is add the ClamAV app and set that up and it runs once a week. I believe I began with TrueNAS version 25.04.1 and the only other thing I’ve done is do incremental updates as they came out to version 25.04.2.4; of course I never checked for this ghost drive after the updates. That’s truly it. I’ve done nothing else. When I moved all of the parts to the new case, they are all the same parts in the same configuration, nothing new at all. Completely odd.