Custom Query (1560 matches)
Results (457 - 459 of 1560)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1575 | fixed | Add new drives to database: TOSHIBA HDWU120 | ||
| Description |
The following drive is not in the database. TOSHIBA HDWU120The HDWU120 is part of the Toshiba V300 series which is not in the database at all. Other capacity members are the TOSHIBA HDWU105, TOSHIBA HDWU110 and TOSHIBA HDWU120. See attachment for the smartctl printout. |
|||
| #1578 | fixed | improve Supported_RAID-Controllers (-d cciss) | ||
| Description |
Hey. On https://www.smartmontools.org/wiki/Supported_RAID-Controllers it says:
and
for CCISS (HP/Compaq Smart Array Controller). However, it seems that /dev/cciss/ is no longer present with current drivers. But... it seems that one can simply use *any* device that is exported from that controller, e.g. /dev/sda (if that is). Perhaps just add a note to the wiki (and other documentation) that this works just as well, which may not be immediately obvious. Thanks, Chris. |
|||
| #1581 | invalid | smartctl never completes when all information is requested from a 4K Native WD drive over USB | ||
| Description |
When the drive is configured 512e, there is no problem. When the drive is configured 4K Native, running "smartctl --xall pd1" results in an infinite loading condition and the only way to stop it is to unplug the drive. This only happens over USB and works fine over a direct SATA connection. It's worth noting I have tested a lot of drives over USB and this is the only time I have seen this issue. The drive was originally 512e, but was changed to 4K Native using this tool: https://github.com/pig1800/WD4kConverter Disk model: WDC WD4005FZBX-00K5WB0 (WD Black 4 TB 3.5") USB docking station: Sabrent DS-UTC1 I believe the chipset on the docking station is the ASMedia ASM235CM. When the drive is unplugged, smartctl immediately returns the attached information (there are many errors). The LED activity light on the docking station blinks the whole time and never stops until it's powered off. My theory is that the the USB chip can't handle one of the commands you are sending. It's a bit odd it took a sector size change to expose the issue, though. |
|||
