
### Thermal design

Based on other users who have dissembled the D8U, the CPU cooler that’s been installed is a HP Probook compatible cooler, part no.s 905706-001, 912932, and L52034-001 – this was confirmed by a user on Discord dissembling their unit and viewing the QR codes on the cooler.

![thermal-1](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/thermal-1.png?raw=true))


This cooling solution is designed to be used with CPUs with 15–45W, whereas the Intel 125H can reach 60–80W.

The D8U by default shipped with the BIOS settings having the Power Limit 1 set to 45W and Power Limit 2 set to 93W – values that are completely incompatible with the CPU cooler.

The lack of appropriate CPU cooling is amplified by the fact that the D8U models are not getting enough fresh air into the CPU compartment, something that multiple users have proven is an issue by using laptop fans to push air into the CPU compartment, this results in an immediate drop in temperature and fan speed.

There is ample room within the D8U chassis for intake fans to be installed from the factory:

![thermal-2](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/thermal-2.png?raw=true)

![thermal-3](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/thermal-3.png?raw=true)


The fan module that Zettlab has chosen to implement also does not follow standard design practices. Most PWM fans follow 0-255 for their settings, the Zettlab module uses 0-183 and is not plug and play with third-party operating systems. If a user wants to install TrueNAS, Unraid, Ubuntu or anything else they need to compile the driver for the fan module and then use a script to convert the 0-183 range into a standard 0-225 range for fan control software to work as Zettlab have not provided a fan driver.

#### Zettlab claims vs real world testing

##### Zettlab data:
On the discord server Zettlab have shown this thermal data citing that the D8U units have no thermal throttling problems
![thermal-4](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/thermal-4.png?raw=true)

![thermal-5](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/thermal-5.png?raw=true)

##### Real world user data:

It should be noted in every single test, real world data shows the CPU is up to 30c higher than Zettlab's claimed thermal results and in most testing is causing the CPU to thermal throttle while the CPU fan is running significantly faster

![thermal-6](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/thermal-6.png?raw=true)

![thermal-7](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/thermal-7.png?raw=true)

![thermal-8](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/thermal-8.png?raw=true)

![thermal-9](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/thermal-9.png?raw=true)

![thermal-10](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/thermal-10.png?raw=true)

#### Conclusions:
From a hardware perspective; Zettlab have chosen a CPU cooler that is not appropriate for the Intel Ultra 5 125H. Additionally the CPU blower does not receive enough fresh air due to the lack of any active air intakes 

Additional concerns can be drawn, with multiple possible answers; 
Zettlab has inaccuracies with their testing methodology and the resulting data is not accurate to real word usage.
OR
Customers are receiving units that are not configured in the same way as Zettlab's internal testing units are.


### Hard Drive Backplane

The HDD backplane that Zettlab have implemented into the D8U is extremely flawed and has already caused irreparable damage to several users high capacity drives.

Zettlab have opted to put all 8 HDDs on a single PCIe 4x connector, without providing any auxiliary power to the hard drive backplane and are relying solely on the PCIe slot for power delivery.

![backplane-1](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/backplane-1.png?raw=true)

**Zettlab have claimed that they're using a custom design for the PCIe slot**

![backplane-2](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/backplane-2.png?raw=true)

![backplane-3](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/backplane-3.png?raw=true)

![backplane-4](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/backplane-4.png?raw=true)

It should be noted that the power limitation is not a protocol or interface restriction, it is a mechanical and electrical limitation of the PCIe connector itself, and Zettlab are using the PCIe connector for power delivery.

##### PCIe 4x Power 

A PCIe 4x slot, regardless of claims, is designed to to deliver a maximum of **25W**
Looking at an average Seagate enterprise drive power consumption and then multiplying by 8

|            | **Idle W** | **Max Load W** |
| ---------- | ---------- | -------------- |
| Single HDD | 5.3        | 9.4            |
| 8 HDDs     | 42.4       | 75.2           |

The idle power draw alone is nearly double what a PCIe 4x slot is rated for. This lack of appropriate power delivery causes all HDDs connected to the backplane to disconnect and reconnect as they're losing their electrical signal.
This can be seen here on all 8 drives:

**Disk A:**
![disk-a](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/disk-a.png?raw=true)

**Disk B:**
![disk-b](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/disk-b.png?raw=true)

**Disk C:**
![disk-c](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/disk-c.png?raw=true)

**Disk D:**
![disk-d](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/disk-d.png?raw=true)

**Disk E:**
![disk-e](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/disk-e.png?raw=true)

**Disk F:**
![disk-f](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/disk-f.png?raw=true)

**Disk G:**
![disk-g](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/disk-g.png?raw=true)

**Disk H:**
![disk-h](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/disk-h.png?raw=true)

The constant fluctuations in power causing to the HDDs to constantly disconnect and reconnect leads to irreparable data loss and file corruption and potentially HDD destruction:

**Capture of a RAIDZ1  pool running on Unraid. 278,600 checksum errors:**

![disk-error-1](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/disk-error-1.png?raw=true)


**This lack of consistent power delivery has already destroyed a customer hard drive:**

![disk-error-2](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/disk-error-2.png?raw=true)


##### SATA Speeds

Zettlab's backplane additionally does not provide the full SATA3 speeds to all 8 of the HDDs connected to it
Two HDDs are running at SATA2 speeds of 3.0Gbps

Here is the pertinent information from the previous screenshots:
```
Disk A - SATA controller: ASMedia ASM1166 - SATA link up 6.0 Gbps
Disk B - SATA controller: ASMedia ASM1166 - SATA link up 6.0 Gbps
Disk C - SATA controller: ASMedia ASM1166 - SATA link up 6.0 Gbps
Disk D - SATA controller: ASMedia ASM1166 - SATA link up 6.0 Gbps
Disk E - SATA controller: ASMedia ASM1166 - SATA link up 6.0 Gbps
Disk F - SATA controller: ASMedia ASM1166 - SATA link up 6.0 Gbps
Disk G - SATA controller: Intel 7e63      - SATA link up 3.0 Gbps
Disk H - SATA controller: Intel 7e63      - SATA link up 3.0 Gbps
```

The Intel 7e63 SATA controller does support SATA3 speeds, however due to the limitations of the PCIe 4x connector Zettlab are using these speeds are never reached as there is not enough bandwidth available.

This difference in SATA connection speeds limits any RAID operations to the SATA2 speeds of the drives connected to the Intel 7e63 - effectively halving what should be available to users.

#### Conclusions:
The Zettlab D8U is not safe to run with 8 HDDs installed into it. The inadequate power delivery system will cause data corruption, and eventually cause damage to any HDD that is constantly disconnecting and reconnecting. 

With how far out of specification the PCIe connector is being used, it's not unreasonable to conclude the device is a potential fire risk.

It is reasonable to assume these electrical concerns also apply to the D6U models based on Zettlab's comments:

![conclusion-1](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/conclusion-1.png?raw=true)

Running less than 3 HDDs should not exceed the limitations of the PCIe 4x slot and ideally prevent damage to user hardware and data.

### Final Thoughts

The Zettlab NAS range has hardware design choices that lead to a user experience that isn't close to what was originally pitched during the Kickstarter campaign.

The D8U in particular suffers the most from these hardware design choices and has already shown to be damaging user HDDs to the point of complete failure.

Unfortunately due the nature of these hardware concerns, an end user is not capable of rectifying them as they are all internal components that would require disassembly to access. and not something covered by the Kickstarter warranty

**Kickstarter Warranty**
![conclusion-2](https://github.com/doakyz/zettlab-d8u-hardware-concerns/blob/main/imgs/conclusion-2.png?raw=true)

My personal recommendation is that any D8U unit should be shut down for the time being to avoid any more potential damage to user HDDs and data.


## Community Credits & Guides

* @CheesyGiblets - Photos of system internals and extensive hardware testing.

* @Speedster (Haveacry / Dean Holland) -  DKMS‑compatible kernel driver exposing the Zettlab D6U/D8U fan controller via hwmon. https://github.com/Haveacry/zettlab-d8-fans
    * Comparative thermal benchmarks and data

* @Henry (Henry Wong) - Detailed documentation and tooling for installing and running Ubuntu on Zettlab D6U/D8U systems. https://github.com/henryxwong/zettlab-ubuntu
 
* @Alex (Ceveos) - Alternative TrueNAS fan control approach community contribution demonstrating fan control and TrueNAS operation on Zettlab D6U/D8U hardware. https://github.com/Ceveos/zettlab-d8-fans-truenas

* @Marshal (mvanas) - A  configuration guide for TrueNAS SCALE 26.  https://github.com/mvanas/zettlab-truenas
    * Insight on the configuration of the PCIe 4x slot

* @mike_whiskey - Logs of a HDD damaged within a D8U
