Device 'WDC WD20EZRZ-00Z5HB0 2TB'
|
Submit your devices info by creating a probe.Status (878)
The device is a part of the following computers:| HWid | Type | Vendor / Model | Probes | System | Last Status | |
|---|---|---|---|---|---|---|
| D0161 » | desktop | ASUSTek / M4A78-E |
2 |  Ubuntu MATE... |
malfunc | |
| B1E93 » | desktop | ASRock / A320M-HDV |
1 |  Ubuntu 20.10 |
malfunc | |
| 6F304 » | desktop | ASRock / B450M Steel ... |
1 |  OpenMandriv... |
malfunc | |
| A4EC4 » | desktop | ASRock / X570 Steel L... |
1 | Ubuntu 24.04 |
malfunc | |
| ED7A4 » | desktop | ASUSTek / B150M-A |
1 |  Mint 22 |
malfunc | |
| A50BE » | desktop | ASUSTek / B150M-A/M.2 |
1 |  Siduction 11 |
malfunc | |
| A50BE » | desktop | ASUSTek / B150M-A/M.2 |
3 | Siduction U... |
malfunc | |
| 084E4 » | desktop | ASUSTek / M5A78L-M LE |
1 | OpenMandriv... |
malfunc | |
| EE6D7 » | desktop | ASUSTek / Maximus VI E... |
1 | Ubuntu 22.04 |
malfunc | |
| B6E30 » | desktop | ASUSTek / P8H77-V |
1 |  ROSA 12.2 |
malfunc | |
| 9AE77 » | desktop | ASUSTek / PRIME B560-PLUS |
1 |  MX 23 |
malfunc | |
| AC6FC » | desktop | ASUSTek / PRIME H510M-E |
1 |  Gentoo 2.14 |
malfunc | |
| D6266 » | desktop | ASUSTek / PRIME H510M-E |
2 | Gentoo 2.14 |
malfunc | |
| BF4D2 » | desktop | ASUSTek / PRIME Z270M-... |
2 |  Arch |
malfunc | |
| CE863 » | desktop | ASUSTek / ROG STRIX B5... |
1 |  Pop!_OS 22.04 |
malfunc | |
| 9891E » | desktop | ASUSTek / ROG STRIX B6... |
1 |  Debian |
malfunc | |
| 9891E » | desktop | ASUSTek / ROG STRIX B6... |
1 | Debian 12 |
malfunc | |
| 75A3C » | desktop | ASUSTek / STRIX Z270E ... |
1 | Arch Rolling |
malfunc | |
| 12270 » | desktop | ASUSTek / TUF B360-PRO... |
1 | OpenMandriv... |
malfunc | |
| 3ECE4 » | desktop | ASUSTek / TUF B450-PLU... |
1 | Mint 20.3 |
malfunc | |
| A7726 » | desktop | ASUSTek / Z170-A |
1 | ROSA R9-R11 |
malfunc | |
| E7832 » | desktop | ASUSTek / Z170-K |
2 | Arch Rolling |
malfunc | |
| 2C707 » | desktop | ASUSTek / Z170M-PLUS |
1 | OpenMandriv... |
malfunc | |
| 62655 » | desktop | Dell / 018D1Y A00 |
1 | OpenMandriv... |
malfunc | |
| 0430F » | mini tower |
Dell / 0KRC95 A00 |
1 | OpenMandriv... |
malfunc | |
| 35FC6 » | tower | Dell / 0TP412 |
1 | Ubuntu MATE... |
malfunc | |
| 0AC5D » | desktop | Dell / 0XHGV1 A00 |
1 |  CentOS 8 |
malfunc | |
| 6B625 » | desktop | EVGA / 151-IB-E699 |
1 | OpenMandriv... |
malfunc | |
| 1DEE2 » | desktop | Gigabyte / 970A-D3P |
1 | OpenMandriv... |
malfunc | |
| 8B6ED » | desktop | Gigabyte / B150M-HD3-CF |
1 | Gentoo 2.7 |
malfunc | |
| 1A51D » | desktop | Gigabyte / B450M S2H |
1 |  Kubuntu 20.10 |
malfunc | |
| FA8EB » | desktop | Gigabyte / B760 GAMING ... |
1 |  NixOS 22.11 |
malfunc | |
| 32D69 » | desktop | Gigabyte / H97-D3H-CF |
1 | Arch |
malfunc | |
| 367B4 » | desktop | Gigabyte / P55-USB3 |
3 |  BlackPanthe... |
malfunc | |
| 60908 » | desktop | Gigabyte / Z590M GAMING X |
1 | OpenMandriv... |
malfunc | |
| D0917 » | low profile |
HP / 1998 |
1 |  Fedora 32 |
malfunc | |
| A756B » | desktop | Intel / DQ965GF AAD4... |
2 | Ubuntu 20.04 |
malfunc | |
| 64E34 » | desktop | Intel / DZ77SL-50K A... |
2 | Debian 12 |
malfunc | |
| 6FFD2 » | desktop | Intel / H61/B75 |
1 | Ubuntu 22.04 |
malfunc | |
| 5016C » | desktop | MSI / A68HM-E33 V2 |
1 | Arch Rolling |
malfunc | |
| 91156 » | desktop | MSI / B150M PRO-VDH |
2 | Mint 20.2 |
malfunc | |
| 48F3B » | desktop | MSI / B350M GAMING... |
1 | Mint 22.2 |
malfunc | |
| B04C7 » | desktop | MSI / B450 TOMAHAW... |
1 | Ubuntu 22.04 |
malfunc | |
| C55D1 » | desktop | MSI / B650 GAMING ... |
1 | OpenMandriv... |
malfunc | |
| 93875 » | desktop | MSI / Z170A GAMING M5 |
1 |  Nobara 39 |
malfunc | |
| 5C1AE » | desktop | MSI / Z370 PC PRO |
1 |  Garuda Linu... |
malfunc | |
| 5C1AE » | desktop | MSI / Z370 PC PRO |
1 |  Manjaro 23.1.3 |
malfunc | |
| 315F6 » | desktop | MSI / Z370-A PRO |
1 | Ubuntu 20.04 |
malfunc | |
| 7DC41 » | desktop | MSI / Z77A-GD55 |
1 |  KDE neon 20.04 |
malfunc |
I don't know why this keeps getting flagged. I have downgraded the filesystem to ext2 to bypass the journalling, done full badblocks check with read+write, and I still get a flag about one sector not writing. Shouldn't that have been taken out of the loop by the disk badblocks list and be bypassed?