dpatterson
Cadet
- Joined
- Nov 10, 2023
- Messages
- 4
Environment:
- MacOS 10.14.6 (Mojave)
- Dual 6-core Intel Xeon
- 64GB RAM
- VMware Fusion 8.5.8
- TrueNAS 13.0-U5.3
I am trying to determine if I can accomplish all of the things that I would like to with a TrueNAS server. To that end I am trying to get up to speed by installing TrueNAS on a VMware Fusion VM under MacOS strictly as a prototyping and learning exercise. If something goes sideways, data loss will be annoying, not a real problem.
That being said, I've run into a problem early on.
I created the VM:
- 2 cores
- 8GB RAM
- Unique IP address via DHCP
- 3 40GB virtual drives, one for boot, two for data
TrueNAS installed without issue. However, when I went to create the pool, I get an error about non-unique drive serial numbers:
Editing the
.
A bit of searching resulted in a parameter that can be added to the
This is apparently only valid for ESXi, not Fusion. Adding that to my Fusion
So the questions:
- Is there a way to set the drive serial numbers in Fusion?
- Is there a way around this in TrueNAS?
- If not, can I do reasonable evaluation/prototyping with a single-disk pool?
TIA
- MacOS 10.14.6 (Mojave)
- Dual 6-core Intel Xeon
- 64GB RAM
- VMware Fusion 8.5.8
- TrueNAS 13.0-U5.3
I am trying to determine if I can accomplish all of the things that I would like to with a TrueNAS server. To that end I am trying to get up to speed by installing TrueNAS on a VMware Fusion VM under MacOS strictly as a prototyping and learning exercise. If something goes sideways, data loss will be annoying, not a real problem.
That being said, I've run into a problem early on.
I created the VM:
- 2 cores
- 8GB RAM
- Unique IP address via DHCP
- 3 40GB virtual drives, one for boot, two for data
TrueNAS installed without issue. However, when I went to create the pool, I get an error about non-unique drive serial numbers:
Code:
Warning: There are 2 disks available that have non-unique serial numbers. Non-unique serial numbers can be caused by a cabling issue and adding such disks to a pool can result in lost data.
Editing the
ddb.uuid
parameter in the .vmdk
file resulted in, essentially, a boot failure (the .vmdk
file is technically a binary file)..
A bit of searching resulted in a parameter that can be added to the
.vmx
file: disk.EnableUUID = “TRUE”
This is apparently only valid for ESXi, not Fusion. Adding that to my Fusion
.vmx
file resulted in an error from Fusion when I booted the VM (TRUE is not a valid value; defaulted to FALSE).So the questions:
- Is there a way to set the drive serial numbers in Fusion?
- Is there a way around this in TrueNAS?
- If not, can I do reasonable evaluation/prototyping with a single-disk pool?
TIA