Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Carlos E.R." 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 12:53:29 +0200 Lines: 201 Message-ID: <9aq4clxn5a.ln2@Telcontar.valinor> References: <7263clxr47.ln2@Telcontar.valinor> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: individual.net nlFWaM6XFuAHISdLZGTXBg84ErwSyxfjcDjqIFz1fFf1zsVnw6 X-Orig-Path: Telcontar.valinor!not-for-mail Cancel-Lock: sha1:KyIBBlVJ09GrcytNDYI9dR04n3A= sha256:gsZ2/Iayt9qVaJ9Y3+cuZYcrVX01ZpU0At0drVeKOKM= User-Agent: Mozilla Thunderbird Content-Language: es-ES, en-CA In-Reply-To: Xref: csiph.com alt.os.linux:81265 alt.comp.os.windows-11:18266 On 2025-04-04 09:53, Paul wrote: > On Fri, 4/4/2025 2:30 AM, vallor wrote: >> On Thu, 3 Apr 2025 22:01:43 +0200, "Carlos E.R." >> wrote in <7263clxr47.ln2@Telcontar.valinor>: >> >>> Hi, >>> >>> I just bought a hard disk enclosure, a Yottamaster 5Bay USB3.0 Model F55 >>> (non raid). My plan is to build a software raid 6 later. >>> >>> Bought here >>> >>> I think it is this one: >>> >>> > type-c-external-hard-drive-enclosure-for-3-5-2-5-inch-sata-hdd-ssd- >> support-5-x-16tb-mac-style-direct-attached-storage-das-ps500c3> >>> >>> >>> I don't have yet the hard disks that will populate it, but I have 2 >>> disks to test it. >>> >>> This is what I get on the log - there is an error >>> >>> <0.6> 2025-04-03T20:16:00.529454+02:00 Telcontar kernel - - - [ T884] >>> usb 2-1: new SuperSpeed USB device number 7 using xhci_hcd <0.6> >>> 2025-04-03T20:16:00.553462+02:00 Telcontar kernel - - - [ T884] usb >>> 2-1: New USB device found, idVendor=152d, idProduct=0578, bcdDevice= >>> 3.01 <0.6> 2025-04-03T20:16:00.553473+02:00 Telcontar kernel - - - [ >>> T884] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 >>> <0.6> 2025-04-03T20:16:00.553474+02:00 Telcontar kernel - - - [ T884] >>> usb 2-1: Product: External HDD <0.6> 2025-04-03T20:16:00.553475+02:00 >>> Telcontar kernel - - - [ T884] usb 2-1: Manufacturer: External USB3.0 >>> <0.6> 2025-04-03T20:16:00.553476+02:00 Telcontar kernel - - - [ T884] >>> usb 2-1: SerialNumber: 0000007788FC <0.6> >>> 2025-04-03T20:16:00.561457+02:00 Telcontar kernel - - - [ T884] >>> usb-storage 2-1:1.0: USB Mass Storage device detected <0.6> >>> 2025-04-03T20:16:00.561466+02:00 Telcontar kernel - - - [ T884] >>> usb-storage 2-1:1.0: Quirks match for vid 152d pid 0578: 1000000 <0.6> >>> 2025-04-03T20:16:00.561467+02:00 Telcontar kernel - - - [ T884] scsi >>> host10: usb-storage 2-1:1.0 <1.6> 2025-04-03T20:16:00.567201+02:00 >>> Telcontar mtp-probe - - - checking bus 2, device 7: >>> "/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb2/2-1" >>> <1.6> 2025-04-03T20:16:00.567579+02:00 Telcontar mtp-probe - - - bus: >>> 2, device: 7 was not an MTP device <1.6> >>> 2025-04-03T20:16:00.602928+02:00 Telcontar mtp-probe - - - checking bus >>> 2, device 7: >>> "/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb2/2-1" >>> <1.6> 2025-04-03T20:16:00.603037+02:00 Telcontar mtp-probe - - - bus: >>> 2, device: 7 was not an MTP device <0.5> >>> 2025-04-03T20:16:01.577474+02:00 Telcontar kernel - - - [T28281] scsi >>> 10:0:0:0: Direct-Access External USB3.0 0301 PQ: 0 ANSI: 6 >>> <0.5> 2025-04-03T20:16:01.577488+02:00 Telcontar kernel - - - [T28281] >>> scsi 10:0:0:1: Direct-Access External USB3.0 0301 PQ: 0 >>> ANSI: 6 <0.5> 2025-04-03T20:16:01.577489+02:00 Telcontar kernel - - - >>> [T28281] sd 10:0:0:0: Attached scsi generic sg5 type 0 <0.5> >>> 2025-04-03T20:16:01.577490+02:00 Telcontar kernel - - - [T28281] sd >>> 10:0:0:1: Attached scsi generic sg6 type 0 <0.5> >>> 2025-04-03T20:16:01.577491+02:00 Telcontar kernel - - - [T31396] sd >>> 10:0:0:0: [sde] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) >>> <0.5> 2025-04-03T20:16:01.577492+02:00 Telcontar kernel - - - [T31392] >>> sd 10:0:0:1: [sdf] 3907029168 512-byte logical blocks: (2.00 TB/1.82 >>> TiB) >>> <0.5> 2025-04-03T20:16:01.577492+02:00 Telcontar kernel - - - [T31396] >>> sd 10:0:0:0: [sde] Write Protect is off <0.7> >>> 2025-04-03T20:16:01.577493+02:00 Telcontar kernel - - - [T31396] sd >>> 10:0:0:0: [sde] Mode Sense: 47 00 00 08 <0.5> >>> 2025-04-03T20:16:01.577494+02:00 Telcontar kernel - - - [T31392] sd >>> 10:0:0:1: [sdf] Write Protect is off <0.7> >>> 2025-04-03T20:16:01.577495+02:00 Telcontar kernel - - - [T31392] sd >>> 10:0:0:1: [sdf] Mode Sense: 47 00 00 08 <0.5> >>> 2025-04-03T20:16:01.581468+02:00 Telcontar kernel - - - [T31396] sd >>> 10:0:0:0: [sde] Disabling FUA <0.5> 2025-04-03T20:16:01.581482+02:00 >>> Telcontar kernel - - - [T31396] sd 10:0:0:0: [sde] Write cache: enabled, >>> read cache: enabled, doesn't support DPO or FUA <0.5> >>> 2025-04-03T20:16:01.581484+02:00 Telcontar kernel - - - [T31392] sd >>> 10:0:0:1: [sdf] Disabling FUA <0.5> 2025-04-03T20:16:01.581486+02:00 >>> Telcontar kernel - - - [T31392] sd 10:0:0:1: [sdf] Write cache: enabled, >>> read cache: enabled, doesn't support DPO or FUA <0.6> >>> 2025-04-03T20:16:01.677458+02:00 Telcontar kernel - - - [T31392] sdf: >>> sdf1 sdf2 sdf3 sdf4 <0.6> 2025-04-03T20:16:01.677470+02:00 Telcontar >>> kernel - - - [T31396] sde: sde1 sde2 sde3 sde4 <0.5> >>> 2025-04-03T20:16:01.677471+02:00 Telcontar kernel - - - [T31392] sd >>> 10:0:0:1: [sdf] Attached SCSI disk <0.5> >>> 2025-04-03T20:16:01.677472+02:00 Telcontar kernel - - - [T31396] sd >>> 10:0:0:0: [sde] Attached SCSI disk <1.4> >>> 2025-04-03T20:16:01.859892+02:00 Telcontar udisksd 2769 - - Error >>> probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sde': >>> Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 >>> 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 >>> 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) >>> <1.4> 2025-04-03T20:16:01.959722+02:00 Telcontar udisksd 2769 - - Error >>> probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdf': >>> Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 >>> 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 >>> 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) >>> >>> >>> hdparm fails: >>> >>> Telcontar:~ # hdparm -i /dev/sdf >>> >>> /dev/sdf: >>> HDIO_GET_IDENTITY failed: Invalid argument >>> Telcontar:~ # hdparm -i /dev/sde >>> >>> /dev/sde: >>> HDIO_GET_IDENTITY failed: Invalid argument >>> Telcontar:~ # >>> >>> smartctl appears to work: >>> >>> Telcontar:~ # smartctl -i /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 INFORMATION SECTION === >>> Model Family: Seagate Barracuda 7200.14 (AF) >>> Device Model: ST1000DM003-1CH162 Serial Number: ... >>> LU WWN Device Id: 5 000c50 05b57c31a Firmware Version: CC44 User >>> Capacity: 1,000,204,886,016 bytes [1.00 TB] >>> Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: >>> 7200 rpm Form Factor: 3.5 inches Device is: In smartctl >>> database 7.3/5528 ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA >>> Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) >>> Local Time is: Thu Apr 3 20:20:14 2025 CEST SMART support is: >>> Available - device has SMART capability. >>> SMART support is: Enabled >>> >>> Telcontar:~ # >>> >>> fdisk -l works. >>> >>> >>> If I run smart short test on one disk, it refuses to start on another, >>> which is funny because tests are supposed to happen internally to the >>> hard disk. >>> >>> >>> What do you think about the error? >>> >>> <1.4> 2025-04-03T20:16:01.859892+02:00 Telcontar udisksd 2769 - - Error >>> probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sde': >>> Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 >>> 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 >>> 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) >>> >>> >>> Bug report? >>> >>> (openSUSE Leap 15.6) >> >> Well, Linux seems to see the partitions... >> >> Maybe the drives will work anyway? Have you tested them? > > It might depend on what firmware is in the box. > > 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. «It appears that most JMicron based USB enclosures use a “feature” in the enclosure to override the model/serial number of the drive inside to instead match the outside of the case. This is popular for pre-assembled units but is an absolute pain for user-replaceable drives.» What? :-O [...] Wow, it is true. :-/ How on earth can I know what RAID disk I have to replace? [...] Mmm... activity makes the blue led to blink slightly, very fast. He says it is easy to flash, but it is a different enclosure. -- Cheers, Carlos.