SageEdwards
Cadet
- Joined
- Aug 17, 2022
- Messages
- 9
I am a first time user of both TrueNAS and enterprise server hardware so, I am sure I have probably made a stupid mistake somewhere in the install/build process.
To start I purchased the following build from ServerMonkey (I'm very happy with this company btw):
System Hardware:
HPE ProLiant DL380 Gen9
x2 Intel Xeon E5-2697 v3
128Gb (8x16GB) 2RX4 PC4-17000R
HP Smart Array P440ar 2GB FBWC Lvl 0-60 INT RAID
On-Board Quad Port 1GbE LOM
HPE Ethernet 546FLR-SFP+ Dual Port DA/SFP+ 10Gb FlexibleLOM Adapter
x2 HP G9 800 Watt PSU
x12 WD RED Pro NAS 16TB HDD
x1 Supermicro SATADOM 64GB
where I installed that HDDs and the SATADOM. However, to get the 5V power to the SATADOM, I made a cable to come off of the internal USB 3 port. Everything boots up fine with no errors. From here I created the boot drive using Balena and then successfully installed the most recent stable version of TrueNAS Core, 13.0-U1.1 in UEFI mode on the SATADOM, with SWAP storage and root password set. I rebooted the system but realized the system was set for legacy boot, so I changed it to UEFI in the BIOS and rebooted again. Once I booted it again and went through the POSTing process, and TrueNAS starts up, I eventually get the following error messages:
This then repeats for a very long time, but it does eventually work through it and enters the console setup, but with the following lines after the option menu:
I suspect that the latter error is simply due to the fact that I don't have the system plugged into any network at the moment (correct me if I am wrong), but it is the former error that concerns me. I suspect that this is due to my janky rigging I did for powering the SATADOM, but I really do not know.
I have attached three images showing the two error screen and the SATADOM powering method.
Any help and/or advice will be greatly appreciated!
-Sage
To start I purchased the following build from ServerMonkey (I'm very happy with this company btw):
System Hardware:
HPE ProLiant DL380 Gen9
x2 Intel Xeon E5-2697 v3
128Gb (8x16GB) 2RX4 PC4-17000R
HP Smart Array P440ar 2GB FBWC Lvl 0-60 INT RAID
On-Board Quad Port 1GbE LOM
HPE Ethernet 546FLR-SFP+ Dual Port DA/SFP+ 10Gb FlexibleLOM Adapter
x2 HP G9 800 Watt PSU
x12 WD RED Pro NAS 16TB HDD
x1 Supermicro SATADOM 64GB
where I installed that HDDs and the SATADOM. However, to get the 5V power to the SATADOM, I made a cable to come off of the internal USB 3 port. Everything boots up fine with no errors. From here I created the boot drive using Balena and then successfully installed the most recent stable version of TrueNAS Core, 13.0-U1.1 in UEFI mode on the SATADOM, with SWAP storage and root password set. I rebooted the system but realized the system was set for legacy boot, so I changed it to UEFI in the BIOS and rebooted again. Once I booted it again and went through the POSTing process, and TrueNAS starts up, I eventually get the following error messages:
READ(16). cdb: 88 00 00 00 00 07 46 BF FF FE 00 00 00 01 00 00
CAM status: CCB request completed with an error
Retrying command, 3 more tries remain
READ(16). cdb: 88 00 00 00 00 07 46 BF FF FE 00 00 00 01 00 00
CAM status: SCSI Status Error
SCSI status: Check Condition
SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
...
...
...
This then repeats for a very long time, but it does eventually work through it and enters the console setup, but with the following lines after the option menu:
The web interface could not be accessed.
Please check network configuration.
Enter an option from 1-11: ciss0: ADAPTER HEARTBEAT FAILED
I suspect that the latter error is simply due to the fact that I don't have the system plugged into any network at the moment (correct me if I am wrong), but it is the former error that concerns me. I suspect that this is due to my janky rigging I did for powering the SATADOM, but I really do not know.
I have attached three images showing the two error screen and the SATADOM powering method.
Any help and/or advice will be greatly appreciated!
-Sage