Custom Query (1327 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (16 - 18 of 1327)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Ticket Resolution Summary Owner Reporter
#1760 wontfix NVMe support for qnx Navaneeth N
Description

Smartmontools does not support NVMe devices on QNX as per the NVMe wiki page. Is there any enhancement planned to extend existing support to NMVe SSDs?

#1757 invalid HP EX950 Nvme Drive not in database Alan Knepper
Description

Submitting output of smartctl -x /dev/nvme0n1

#1751 fixed SMART Test never ending and cannot be stopped Felix
Description

Hi, I have accumulated some 30 or more HGST HUC101212CSS600 disks over the years which have served in different environments. Most of them have been replaced by larger SSDs by now.

How ever, as I was somewhat lazy in documenting the disks health before decommissioning them in their prior environment, I have to do this now to see, which of them can be still used as spares, where needed.

The test-server is a HP DL380 Gen8 with a SmartArray in HBA-Mode. I have had already tested over 20 disks. The test scenario was always the same:

Insert the disks, enumerate them and check if they are available to the system (dmesg, ssacli) and then start using

smartctl -t long -d cciss,N /dev/sdX

All went well and I was able to identify about 6 disks, which did not pass the long self test.

The last 5 disks give me a headache:

So i did my usual routine and launched on every disk the smartctl -t long -d cciss,N /dev/sdX

When issuing the command to the last of those 5 disks, the server became unresponsible, I was not even able to use SysReq to restart it and really had to hard-shutdown via Power-Off button.

So I rebooted the host, removing all but the boot disk and repeated the whole procedure. Same result, the last disk killed the server. So, "One down, 4 to go" I thought.

So I rebooted again, removed the obviously damaged disk completely, the others I re-plugged once the server was up again. So I checked the smart status:

All of those 4 remaining disks have now one or two long tests pending, which I cannot stop: for x in 0 1 2 3 4; do smartctl -a -d cciss,$x /dev/sda|grep -e "Product\|Vendor\|Serial\|Self test in progress"; done|less Vendor: HGST Product: HUC101212CSS600 Serial number: L0G9PVTG Vendor (Seagate Cache) information # 1 Background long Self test in progress ... 7 NOW - [- - -] Vendor: HGST Product: HUC101212CSS600 Serial number: L0GXKNLH Vendor (Seagate Cache) information # 2 Background long Self test in progress ... 7 NOW - [- - -] Vendor: HGST Product: HUC101212CSS600 Serial number: L0G9KZPG Vendor (Seagate Cache) information # 2 Background long Self test in progress ... 7 NOW - [- - -] Vendor: HGST Product: HUC101212CSS600 Serial number: L0G2E74H Vendor (Seagate Cache) information # 1 Background long Self test in progress ... 7 NOW - [- - -] # 2 Background long Self test in progress ... 7 NOW - [- - -]

Issuing smartctl -X -d cciss,2 /dev/sdd

smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.2.16-12-pve] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

Self Test returned without error

Re-checking with -a still shows those one or two self-tests in progress.

BTW: in /etc/smartd.conf no scheduled tests are defined, that could mess up. BTW2: I left the server do it's things over night in the hope, that maybe the disks would finish up their tests themselves, but no luck either!

My questions are: 1) is there any other way to abort those self-tests that pretend to be in progress 2) if not, is this a sign, that all of those disks are ready for disposal? Or can they still be saved?

many thanks for any help on this!

Felix

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.