Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "Carlos E.R." <robin_listas@es.invalid>
Newsgroups: alt.os.linux,alt.comp.os.windows-11
Subject: Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE)
Date: Fri, 4 Apr 2025 23:40:02 +0200
Lines: 87
Message-ID: <i606clxumo.ln2@Telcontar.valinor>
References: <7263clxr47.ln2@Telcontar.valinor> <m59ck7Fk3odU1@mid.individual.net> <vso35r$2utuc$1@dont-email.me> <9aq4clxn5a.ln2@Telcontar.valinor>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net rERmLDFvzulLyHjwUeADwwUdGfBNtEASQBGg+Ti5PlGnzjHvYj
X-Orig-Path: Telcontar.valinor!not-for-mail
Cancel-Lock: sha1:A89UkBTVc+nxssrihReCpFSiCKQ= sha256:eFuNsF0S6892Pt3++g/4nFZjOBiAG+Q9EDRbKJ5MPwk=
User-Agent: Mozilla Thunderbird
Content-Language: es-ES, en-CA
In-Reply-To: <9aq4clxn5a.ln2@Telcontar.valinor>
Xref: csiph.com alt.os.linux:81274 alt.comp.os.windows-11:18283

On 2025-04-04 12:53, Carlos E.R. wrote:
> On 2025-04-04 09:53, Paul wrote:


>>     https://ralimtek.com/posts/2021/jms578/
>>
>> The claim there, is the ROM inside the device has a boot loader,
>> so erasing the flash cannot brick it. You can keep trying to flash it.
> 
> «Additionally, you may have run into the stupid way these units power 
> down the drives after 10 minutes of inactivity forcefully. Completely 
> ignoring OS or HDD settings. This is infuriating if you want the drives 
> to do what you tell them.»
> 
> Argh. So I need a cronjob every five minutes? Or do they restart 
> automatically?
> 
> [...]
> 
> Seems to not be happening. I listed files in the terminal more than 10 
> minutes later, and it responded instantly.


Yes, it is happening.

Maybe having a terminal open at the mount point avoided the power off to happen.

I hibernated the machine, later woke it up, and access to the files was fast. But now I launched a smartctl long test, and it aborted (doesn't say the percent):

Telcontar:~ # smartctl -l selftest /dev/sde
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.4.0-150600.23.42-default] (SUSE RPM)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Interrupted (host reset)      00%       614         -
# 2  Short offline       Completed without error       00%       613         -
# 3  Short offline       Completed without error       00%       606         -


So I'm trying again leaving a terminal open at the mount point. If that fails, I need a while loop to do some activity periodically while running the smart test.

I don't know how sensitive is software raid to the disk dying on it.

[...]

Well, no, leaving the terminal open is not enough, the long test is aborted. Brilliant firmware, that. I'll have to create a script with the test and a loop.

Initial script:

+++···················
#!/bin/bash

THEDISK=/dev/sde

function busyloop()
{
    while true  ; do
         DATE=`date --rfc-3339=s`
         echo -en "$DATE \t"
         smartctl -l selftest $THEDISK | grep "# 1"
         sleep 1m
    done
}

echo smartctl --test=long $THEDISK
echo
busyloop
···················++-


It has survived for 15 minutes so far. I will let the script run, and change the loop to 5 minutes.

Mmm, dunno how to stop automatically the script... Of course, the text will say so, then ctrl-C. Maybe... knowing how long it should run, kill the script with a timer. Better parse the text somehow.


2025-04-04 23:35:18+02:00 	# 1  Extended offline    Completed without error       00%       618         -
^C
Telcontar:~/tmp/disk1 #


Ok, the procedure works. Now logging off, because I have a bug that crashes the machine a bit after midnight.
Improving the script has to wait.

-- 
Cheers, Carlos.