Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-11 > #18245 > unrolled thread
| Started by | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| First post | 2025-04-03 22:01 +0200 |
| Last post | 2025-04-05 22:03 +0200 |
| Articles | 20 on this page of 35 — 6 participants |
Back to article view | Back to alt.comp.os.windows-11
Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-03 22:01 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-03 17:47 -0400
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 02:39 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-03 23:33 -0400
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 11:36 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 12:16 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-04 14:51 -0400
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 21:52 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Java Jive <java@evij.com.invalid> - 2025-04-04 11:28 +0100
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 12:47 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Java Jive <java@evij.com.invalid> - 2025-04-04 17:06 +0100
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 19:09 +0200
Re: Amazon (Was: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "J.O. Aho" <user@example.net> - 2025-04-04 21:26 +0200
Re: Amazon (Was: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Mark Lloyd <not.email@all.invalid> - 2025-04-05 16:22 +0000
Re: Amazon (Was: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-05 21:01 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-06 14:44 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) vallor <vallor@cultnix.org> - 2025-04-04 06:30 +0000
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-04 03:53 -0400
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 12:53 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 13:44 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 23:40 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-05 13:33 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-05 18:23 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-05 21:04 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 12:15 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-04 16:30 -0400
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 22:52 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-04 18:46 -0400
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Java Jive <java@evij.com.invalid> - 2025-04-05 00:20 +0100
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-04 23:05 -0400
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-05 12:47 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Java Jive <java@evij.com.invalid> - 2025-04-05 14:14 +0100
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-05 18:23 +0200
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-06 00:13 -0400
Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-05 22:03 +0200
Page 1 of 2 [1] 2 Next page →
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-04-03 22:01 +0200 |
| Subject | Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) |
| Message-ID | <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 <https://www.amazon.es/dp/B083Q8Z2KM> I think it is this one: <https://yottamaster.com/products/yottamaster-aluminum-5-bay-usb3-1-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) -- Cheers, Carlos.
[toc] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-04-03 17:47 -0400 |
| Message-ID | <vsmvmc$1n9gc$1@dont-email.me> |
| In reply to | #18245 |
On Thu, 4/3/2025 4:01 PM, Carlos E.R. wrote:
>
> 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 <https://www.amazon.es/dp/B083Q8Z2KM>
>
> I think it is this one:
>
> <https://yottamaster.com/products/yottamaster-aluminum-5-bay-usb3-1-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)
The first thing you check with "materials" like this, is what
driver support and firmware support does it have. There is a button
to click, which claims to expose user manuals for download.
https://support.yottamaster.com/download
A bad sign, is when you can't even hire someone to make a web site.
The web site behaves like it's on someones night table and
running over a $39.95 ADSL package or something.
Fortunately, you have a PNP of idVendor=152d, idProduct=0578
and it is a JMicron 578.
https://forums.linuxmint.com/viewtopic.php?t=230562
Product Teaser PDF. UhOh! This sentence hints how an attempt to make
a cheap enclosure could go.
https://web.archive.org/web/20171215115739if_/http://www.jmicron.com:80/PDF/brief/jms578.pdf
"Moreover, the JMS578 can combine with JMicron's SATA port multipliers to construct a data storage
device with multiple bays of HDDs to meet the requirement for large capacity data storage applications."
The datasheet shows an SPI port, which might be for a 2KB device to change the VendorID.
The device has a <cough> "ROM" -- they don't even make it clear whether
that is EEPROM or what. In the year 2025, it's risky to make first-layer
mask programmed ROM chips. If you foul up the firmware in such a device,
you need a mechanism to support patching. Good devices use EEPROM, you
flash them up and blow the bugs out of it.
I'm not at all sure, whether frame-based SATA switching is supported over
USB. It probably is, but your results are not encouraging so far.
"Great science experiment you've got there, sir!" :-)
If the enclosure only had one hard drive bay and no 1port-to-5port
expansion chip bolted to it, this would not have played out the same way.
USB3 --- JMB578 ---- Single drive # likely to work
USB3 --- JMB578 ---- SATA Mux ----- Drive1 # Expansion chip has a fanout of 5.
(Frame ----- Drive2 # This is the defacto way the industry makes those.
Based ----- Drive3
Switching) ----- Drive4
----- Drive5
Paul
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-04-04 02:39 +0200 |
| Message-ID | <4bm3clx6pp.ln2@Telcontar.valinor> |
| In reply to | #18251 |
On 2025-04-03 23:47, Paul wrote: > On Thu, 4/3/2025 4:01 PM, Carlos E.R. wrote: > > The first thing you check with "materials" like this, is what > driver support and firmware support does it have. You can not know before buying :-( > There is a button > to click, which claims to expose user manuals for download. What I noticed, is that both the paper "manual" and the web talk of raid modes and a switch to control them, while this box is raidless. Raid is on another box, more expensive. The metalwork and hardware give a good impression, though. The fan is actually silent. > > https://support.yottamaster.com/download > > A bad sign, is when you can't even hire someone to make a web site. > The web site behaves like it's on someones night table and > running over a $39.95 ADSL package or something. > > Fortunately, you have a PNP of idVendor=152d, idProduct=0578 > and it is a JMicron 578. > > https://forums.linuxmint.com/viewtopic.php?t=230562 > > Product Teaser PDF. UhOh! This sentence hints how an attempt to make > a cheap enclosure could go. > > https://web.archive.org/web/20171215115739if_/http://www.jmicron.com:80/PDF/brief/jms578.pdf > > "Moreover, the JMS578 can combine with JMicron's SATA port multipliers to construct a data storage > device with multiple bays of HDDs to meet the requirement for large capacity data storage applications." Ha! So, probably several vendors build the same thing. > The datasheet shows an SPI port, which might be for a 2KB device to change the VendorID. > > The device has a <cough> "ROM" -- they don't even make it clear whether > that is EEPROM or what. In the year 2025, it's risky to make first-layer > mask programmed ROM chips. If you foul up the firmware in such a device, > you need a mechanism to support patching. Good devices use EEPROM, you > flash them up and blow the bugs out of it. > > I'm not at all sure, whether frame-based SATA switching is supported over > USB. It probably is, but your results are not encouraging so far. > > "Great science experiment you've got there, sir!" :-) > > If the enclosure only had one hard drive bay and no 1port-to-5port > expansion chip bolted to it, this would not have played out the same way. > > USB3 --- JMB578 ---- Single drive # likely to work > > USB3 --- JMB578 ---- SATA Mux ----- Drive1 # Expansion chip has a fanout of 5. > (Frame ----- Drive2 # This is the defacto way the industry makes those. > Based ----- Drive3 > Switching) ----- Drive4 > ----- Drive5 Sigh. So you think this is a firmware issue, and nothing can be done on the Linux side? -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-04-03 23:33 -0400 |
| Message-ID | <vsnjul$2fgla$1@dont-email.me> |
| In reply to | #18253 |
On Thu, 4/3/2025 8:39 PM, Carlos E.R. wrote:
> On 2025-04-03 23:47, Paul wrote:
>> On Thu, 4/3/2025 4:01 PM, Carlos E.R. wrote:
>
>
>>
>> The first thing you check with "materials" like this, is what
>> driver support and firmware support does it have.
>
> You can not know before buying :-(
>
>> There is a button
>> to click, which claims to expose user manuals for download.
>
> What I noticed, is that both the paper "manual" and the web talk of raid modes and a switch to control them, while this box is raidless. Raid is on another box, more expensive.
>
> The metalwork and hardware give a good impression, though. The fan is actually silent.
>
>>
>> https://support.yottamaster.com/download
>>
>> A bad sign, is when you can't even hire someone to make a web site.
>> The web site behaves like it's on someones night table and
>> running over a $39.95 ADSL package or something.
>>
>> Fortunately, you have a PNP of idVendor=152d, idProduct=0578
>> and it is a JMicron 578.
>>
>> https://forums.linuxmint.com/viewtopic.php?t=230562
>>
>> Product Teaser PDF. UhOh! This sentence hints how an attempt to make
>> a cheap enclosure could go.
>>
>> https://web.archive.org/web/20171215115739if_/http://www.jmicron.com:80/PDF/brief/jms578.pdf
>>
>> "Moreover, the JMS578 can combine with JMicron's SATA port multipliers to construct a data storage
>> device with multiple bays of HDDs to meet the requirement for large capacity data storage applications."
>
> Ha! So, probably several vendors build the same thing.
>
>
>> The datasheet shows an SPI port, which might be for a 2KB device to change the VendorID.
>>
>> The device has a <cough> "ROM" -- they don't even make it clear whether
>> that is EEPROM or what. In the year 2025, it's risky to make first-layer
>> mask programmed ROM chips. If you foul up the firmware in such a device,
>> you need a mechanism to support patching. Good devices use EEPROM, you
>> flash them up and blow the bugs out of it.
>>
>> I'm not at all sure, whether frame-based SATA switching is supported over
>> USB. It probably is, but your results are not encouraging so far.
>>
>> "Great science experiment you've got there, sir!" :-)
>>
>> If the enclosure only had one hard drive bay and no 1port-to-5port
>> expansion chip bolted to it, this would not have played out the same way.
>>
>> USB3 --- JMB578 ---- Single drive # likely to work
>>
>> USB3 --- JMB578 ---- SATA Mux ----- Drive1 # Expansion chip has a fanout of 5.
>> (Frame ----- Drive2 # This is the defacto way the industry makes those.
>> Based ----- Drive3
>> Switching) ----- Drive4
>> ----- Drive5
>
> Sigh.
>
>
> So you think this is a firmware issue, and nothing can be done on the Linux side?
>
It would seem "the underground" is distributing various firmwares for
this thing. Maybe the SPI bus really does have a firmware capability
to "fix" the stupid thing ? The architecture document isn't exactly honest
about this.
jms578fwupdater.tgz 2,089,194 bytes
JMS578FwUpdate 4,130,828 bytes
I guess that means some of the devices, have a 4MB SPI flash chip.
and that's where the firmware is stored or something. THis could be
a small 8 pin DIP near the JMB578 on the circuit board.
I don't like to quote "sources" for things like this, unless
there is some sort of traceability for them.
The firmware may have been written by JMicron, but JMicron are
not likely to be serving the file like a RealTek might.
And since it's a flasher-firmware thing, the OS firmware support
is not of the same delivery type (some devices accept dynamic
firmware which is stored in device RAM). This would be a firmware
that is stored in an outboard chip from the JMS578. It fixes issue
such as TRIM, UASP diaablement, proper support of power saving,
and so on.
The work you are doing, is similar to the work an enclosure
engineer might do, before shipping this project. Each user
apparently expected to "sweep the web", "look for bootleg firmware",
"install" and "hope for the best". A science project.
Paul
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-04-04 11:36 +0200 |
| Message-ID | <nql4clxn8s.ln2@Telcontar.valinor> |
| In reply to | #18258 |
On 2025-04-04 05:33, Paul wrote: > On Thu, 4/3/2025 8:39 PM, Carlos E.R. wrote: >> On 2025-04-03 23:47, Paul wrote: >>> On Thu, 4/3/2025 4:01 PM, Carlos E.R. wrote: ... >> Sigh. >> >> >> So you think this is a firmware issue, and nothing can be done on the Linux side? >> > > It would seem "the underground" is distributing various firmwares for > this thing. Maybe the SPI bus really does have a firmware capability > to "fix" the stupid thing ? The architecture document isn't exactly honest > about this. > > jms578fwupdater.tgz 2,089,194 bytes > > JMS578FwUpdate 4,130,828 bytes > > I guess that means some of the devices, have a 4MB SPI flash chip. > and that's where the firmware is stored or something. THis could be > a small 8 pin DIP near the JMB578 on the circuit board. > > I don't like to quote "sources" for things like this, unless > there is some sort of traceability for them. > > The firmware may have been written by JMicron, but JMicron are > not likely to be serving the file like a RealTek might. > > And since it's a flasher-firmware thing, the OS firmware support > is not of the same delivery type (some devices accept dynamic > firmware which is stored in device RAM). This would be a firmware > that is stored in an outboard chip from the JMS578. It fixes issue > such as TRIM, UASP diaablement, proper support of power saving, > and so on. > > The work you are doing, is similar to the work an enclosure > engineer might do, before shipping this project. Each user > apparently expected to "sweep the web", "look for bootleg firmware", > "install" and "hope for the best". A science project. That's out of my league :-( -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-04-04 12:16 +0200 |
| Message-ID | <g5o4clxl55.ln2@Telcontar.valinor> |
| In reply to | #18261 |
On 2025-04-04 11:36, Carlos E.R. wrote: > On 2025-04-04 05:33, Paul wrote: >> On Thu, 4/3/2025 8:39 PM, Carlos E.R. wrote: >>> On 2025-04-03 23:47, Paul wrote: >>>> On Thu, 4/3/2025 4:01 PM, Carlos E.R. wrote: > > ... > >>> Sigh. >>> >>> >>> So you think this is a firmware issue, and nothing can be done on the >>> Linux side? >>> >> >> It would seem "the underground" is distributing various firmwares for >> this thing. Maybe the SPI bus really does have a firmware capability >> to "fix" the stupid thing ? The architecture document isn't exactly >> honest >> about this. >> >> jms578fwupdater.tgz 2,089,194 bytes >> >> JMS578FwUpdate 4,130,828 bytes >> >> I guess that means some of the devices, have a 4MB SPI flash chip. >> and that's where the firmware is stored or something. THis could be >> a small 8 pin DIP near the JMB578 on the circuit board. >> >> I don't like to quote "sources" for things like this, unless >> there is some sort of traceability for them. >> >> The firmware may have been written by JMicron, but JMicron are >> not likely to be serving the file like a RealTek might. >> >> And since it's a flasher-firmware thing, the OS firmware support >> is not of the same delivery type (some devices accept dynamic >> firmware which is stored in device RAM). This would be a firmware >> that is stored in an outboard chip from the JMS578. It fixes issue >> such as TRIM, UASP diaablement, proper support of power saving, >> and so on. >> >> The work you are doing, is similar to the work an enclosure >> engineer might do, before shipping this project. Each user >> apparently expected to "sweep the web", "look for bootleg firmware", >> "install" and "hope for the best". A science project. > > That's out of my league :-( I also asked on the openSUSE mail list, and a chap named Bengt said: +++····················· I have no experience with this device but it seems like others are having problems as well with idVendor=152d, idProduct=0578 (JMicron Technology JMS578 SATA 6Gb/s) https://linux-hardware.org/?id=usb:152d-0578 ·····················++- > -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-04-04 14:51 -0400 |
| Message-ID | <vsp9na$6off$1@dont-email.me> |
| In reply to | #18262 |
On Fri, 4/4/2025 6:16 AM, Carlos E.R. wrote: > On 2025-04-04 11:36, Carlos E.R. wrote: >> On 2025-04-04 05:33, Paul wrote: >>> On Thu, 4/3/2025 8:39 PM, Carlos E.R. wrote: >>>> On 2025-04-03 23:47, Paul wrote: >>>>> On Thu, 4/3/2025 4:01 PM, Carlos E.R. wrote: >> >> ... >> >>>> Sigh. >>>> >>>> >>>> So you think this is a firmware issue, and nothing can be done on the Linux side? >>>> >>> >>> It would seem "the underground" is distributing various firmwares for >>> this thing. Maybe the SPI bus really does have a firmware capability >>> to "fix" the stupid thing ? The architecture document isn't exactly honest >>> about this. >>> >>> jms578fwupdater.tgz 2,089,194 bytes >>> >>> JMS578FwUpdate 4,130,828 bytes >>> >>> I guess that means some of the devices, have a 4MB SPI flash chip. >>> and that's where the firmware is stored or something. THis could be >>> a small 8 pin DIP near the JMB578 on the circuit board. >>> >>> I don't like to quote "sources" for things like this, unless >>> there is some sort of traceability for them. >>> >>> The firmware may have been written by JMicron, but JMicron are >>> not likely to be serving the file like a RealTek might. >>> >>> And since it's a flasher-firmware thing, the OS firmware support >>> is not of the same delivery type (some devices accept dynamic >>> firmware which is stored in device RAM). This would be a firmware >>> that is stored in an outboard chip from the JMS578. It fixes issue >>> such as TRIM, UASP diaablement, proper support of power saving, >>> and so on. >>> >>> The work you are doing, is similar to the work an enclosure >>> engineer might do, before shipping this project. Each user >>> apparently expected to "sweep the web", "look for bootleg firmware", >>> "install" and "hope for the best". A science project. >> >> That's out of my league :-( > > I also asked on the openSUSE mail list, and a chap named Bengt said: > > +++····················· > I have no experience with this device but it seems like others are having problems as well with idVendor=152d, idProduct=0578 (JMicron Technology JMS578 SATA 6Gb/s) > > https://linux-hardware.org/?id=usb:152d-0578 > ·····················++- It is not the "device" you have to worry about, it is the firmware load that makes a difference. As long as JMicron do not list the firmware(s) they have as part of their production (RAID, non-RAID, frame-based switching, enclosure-handling), it is hard to know precisely how many firmware types there are to choose from, and whether a different one would work better. You would expect some enclosure management support. Some units have a LED per drive, and maybe the controller chip can communicate with the mux and light the lights it wants to light. Another form of input the controllers had in the past, was mode switches, you could select JBOD, RAID0, RAID1, RAID10 with a couple DIP switches on the enclosure. And the firmware would read those and operate the disks (with metadata written on them) accordingly. Like if one drive is the odd drive, the other the even drive, your clusters or inodes end up in the correct order, each time the enclosure boots. You can do a JBOD, and run a softRAID on top of them, which I gather was your plan, until the drives did not behave themselves. Paul
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-04-04 21:52 +0200 |
| Message-ID | <5tp5clx4c8.ln2@Telcontar.valinor> |
| In reply to | #18276 |
On 2025-04-04 20:51, Paul wrote: > On Fri, 4/4/2025 6:16 AM, Carlos E.R. wrote: ... >> I also asked on the openSUSE mail list, and a chap named Bengt said: >> >> +++····················· >> I have no experience with this device but it seems like others are having problems as well with idVendor=152d, idProduct=0578 (JMicron Technology JMS578 SATA 6Gb/s) >> >> https://linux-hardware.org/?id=usb:152d-0578 >> ·····················++- > > It is not the "device" you have to worry about, it is > the firmware load that makes a difference. > > As long as JMicron do not list the firmware(s) they > have as part of their production (RAID, non-RAID, > frame-based switching, enclosure-handling), it is hard to know precisely > how many firmware types there are to choose from, and > whether a different one would work better. > > You would expect some enclosure management support. Some > units have a LED per drive, and maybe the controller chip > can communicate with the mux and light the lights it wants > to light. Yes, there is a tiny blue LED that blinks fast with activity. It is hard to see. I mentioned in another post how to make it blink to identify a disk. > Another form of input the controllers had in the past, > was mode switches, you could select JBOD, RAID0, RAID1, RAID10 > with a couple DIP switches on the enclosure. And the firmware > would read those and operate the disks (with metadata written on them) > accordingly. Like if one drive is the odd drive, the other the even > drive, your clusters or inodes end up in the correct order, > each time the enclosure boots. Yes, that's a different model of box, more expensive. I intentionally did not buy that one because I prefer software raid. > > You can do a JBOD, and run a softRAID on top of them, which I gather > was your plan, until the drives did not behave themselves. No, my box has no modes, it is just separate disks. I will do a software raid 6 on that. This means it will be slow. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Java Jive <java@evij.com.invalid> |
|---|---|
| Date | 2025-04-04 11:28 +0100 |
| Message-ID | <vsoc96$37f4l$1@dont-email.me> |
| In reply to | #18261 |
On 2025-04-04 10:36, Carlos E.R. wrote: > > On 2025-04-04 05:33, Paul wrote: >> >> The work you are doing, is similar to the work an enclosure >> engineer might do, before shipping this project. Each user >> apparently expected to "sweep the web", "look for bootleg firmware", >> "install" and "hope for the best". A science project. > > That's out of my league :-( Should you not just return it as not being fit for purpose? I'm not sure how much help, if any, the following will be, because it's not quite the same sort of thing that you've bought, but I have an external drive bay based on an JMS56x chip, and by and large it works fine. In Windows, occasionally it doesn't register when I plug it in, but that doesn't happen very often, and usually unplugging it, removing ghost devices from Device Manager in Windows, and plugging it back in will get it to work. AFAICR, I've not had any problems with it under Ubuntu. Perhaps I should note also that I've not tried to use all the functionality of it, for instance using it to copy disks directly. It's this: https://www.amazon.co.uk/RSHTECH-Aluminum-Multifunction-External-Tool-Free-Black-Housing/dp/B07WNPG6KP -- Fake news kills! I may be contacted via the contact address given on my website: www.macfh.co.uk
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-04-04 12:47 +0200 |
| Message-ID | <fup4clxr18.ln2@Telcontar.valinor> |
| In reply to | #18264 |
On 2025-04-04 12:28, Java Jive wrote: > On 2025-04-04 10:36, Carlos E.R. wrote: >> >> On 2025-04-04 05:33, Paul wrote: >>> >>> The work you are doing, is similar to the work an enclosure >>> engineer might do, before shipping this project. Each user >>> apparently expected to "sweep the web", "look for bootleg firmware", >>> "install" and "hope for the best". A science project. >> >> That's out of my league :-( > > Should you not just return it as not being fit for purpose? Sure, but which one can I get instead? Probably all 5 disk enclosures will be using the same chipset. I can instead buy 9 or 10 individual, one disk enclosures, with their 10 separate power supplies. I would need an insane cabinet space, too. I would have to cancel the project, and return the hard disks, too. > > I'm not sure how much help, if any, the following will be, because it's > not quite the same sort of thing that you've bought, but I have an > external drive bay based on an JMS56x chip, and by and large it works > fine. In Windows, occasionally it doesn't register when I plug it in, > but that doesn't happen very often, and usually unplugging it, removing > ghost devices from Device Manager in Windows, and plugging it back in > will get it to work. AFAICR, I've not had any problems with it under > Ubuntu. Perhaps I should note also that I've not tried to use all the > functionality of it, for instance using it to copy disks directly. > > It's this: > > https://www.amazon.co.uk/RSHTECH-Aluminum-Multifunction-External-Tool- > Free-Black-Housing/dp/B07WNPG6KP > -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Java Jive <java@evij.com.invalid> |
|---|---|
| Date | 2025-04-04 17:06 +0100 |
| Message-ID | <vsp02n$3qe94$1@dont-email.me> |
| In reply to | #18265 |
On 2025-04-04 11:47, Carlos E.R. wrote: > > On 2025-04-04 12:28, Java Jive wrote: >> >> On 2025-04-04 10:36, Carlos E.R. wrote: >>> >>> On 2025-04-04 05:33, Paul wrote: >>>> >>>> The work you are doing, is similar to the work an enclosure >>>> engineer might do, before shipping this project. Each user >>>> apparently expected to "sweep the web", "look for bootleg firmware", >>>> "install" and "hope for the best". A science project. >>> >>> That's out of my league :-( >> >> Should you not just return it as not being fit for purpose? > > Sure, but which one can I get instead? > > Probably all 5 disk enclosures will be using the same chipset. I can > instead buy 9 or 10 individual, one disk enclosures, with their 10 > separate power supplies. I would need an insane cabinet space, too. > > I would have to cancel the project, and return the hard disks, too. Well, whenever I buy anything like this, I look at the critical reviews, just to get a feel for "What's the worst that can happen?", the answer to which in this case seems to be, "You lose all your data!". First, I went to look at the critical reviews on the link you gave at the start of this thread, but amazon.es wanted me to sign in - sign in, just to read reviews??? - and I don't have an account with them, only amazon.co.uk, so I looked up the critical reviews there instead. There are quite a few, enough to deter me from buying, so maybe return it and try a different make and model with, hopefully, better firmware? https://www.amazon.co.uk/product-reviews/B08DLTKXCP/ref=cm_cr_arp_d_viewpnt_rgt?ie=UTF8&reviewerType=all_reviews&filterByStar=critical&pageNumber=1 -- Fake news kills! I may be contacted via the contact address given on my website: www.macfh.co.uk
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-04-04 19:09 +0200 |
| Message-ID | <jag5clxgsd.ln2@Telcontar.valinor> |
| In reply to | #18272 |
On 2025-04-04 18:06, Java Jive wrote: > On 2025-04-04 11:47, Carlos E.R. wrote: >> >> On 2025-04-04 12:28, Java Jive wrote: >>> >>> On 2025-04-04 10:36, Carlos E.R. wrote: >>>> >>>> On 2025-04-04 05:33, Paul wrote: >>>>> >>>>> The work you are doing, is similar to the work an enclosure >>>>> engineer might do, before shipping this project. Each user >>>>> apparently expected to "sweep the web", "look for bootleg firmware", >>>>> "install" and "hope for the best". A science project. >>>> >>>> That's out of my league :-( >>> >>> Should you not just return it as not being fit for purpose? >> >> Sure, but which one can I get instead? >> >> Probably all 5 disk enclosures will be using the same chipset. I can >> instead buy 9 or 10 individual, one disk enclosures, with their 10 >> separate power supplies. I would need an insane cabinet space, too. >> >> I would have to cancel the project, and return the hard disks, too. > > Well, whenever I buy anything like this, I look at the critical reviews, > just to get a feel for "What's the worst that can happen?", the answer > to which in this case seems to be, "You lose all your data!". First, I > went to look at the critical reviews on the link you gave at the start > of this thread, but amazon.es wanted me to sign in - sign in, just to > read reviews??? That's weird, doesn't happen to me. In fact, I have two separate profiles in firefox, one for looking in Amazon without login, and another profile where I login. This way I avoid they pestering me with mails about what I searched. Sometimes, when opening the uk or the .com amazon pages they ask me to fill a captcha. > - and I don't have an account with them, only > amazon.co.uk, so I looked up the critical reviews there instead. There > are quite a few, enough to deter me from buying, so maybe return it and > try a different make and model with, hopefully, better firmware? > > https://www.amazon.co.uk/product-reviews/B08DLTKXCP/ > ref=cm_cr_arp_d_viewpnt_rgt? > ie=UTF8&reviewerType=all_reviews&filterByStar=critical&pageNumber=1 I looked at the reviews at the Amazon.es site, they were acceptable, more so than other alternatives :-D Funny, when I try your link, it asks ME to login! I had to open instead the https://www.amazon.co.uk/ page first, then search for the product number in your link, "B08DLTKXCP", which is not the same one as I got, which is "B083Q8Z2KM". Mine is 6 GBps, while this one is 10GBps. This one has daisy chain USB, mine doesn't. You also have to be careful with the review, because they bundle several models, namely the one that has internal raid. It happens when the same page in Amazon has two or more model, which you choose pressing a button just below the initial description. On each review there is a text that says "Size Name: USB3.0 RAID". The correct one would have "Size Name: USB3.1 Type C Daisy..." If I click on "see more reviews", it asks for my login. I did not continue :-( Something has changed at Amazon :-/ -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | "J.O. Aho" <user@example.net> |
|---|---|
| Date | 2025-04-04 21:26 +0200 |
| Subject | Re: Amazon (Was: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) |
| Message-ID | <m5aq2iFrb2eU1@mid.individual.net> |
| In reply to | #18273 |
On 04/04/2025 19.09, Carlos E.R. wrote: > On 2025-04-04 18:06, Java Jive wrote: >> but amazon.es wanted me to sign in > > Funny, when I try your link, it asks ME to login! > > If I click on "see more reviews", it asks for my login. I did not > continue :-( > > > Something has changed at Amazon :-/ Yeah, nowadays you have a unified accounts which you should be able to login on multiple different sites. -- //Aho
[toc] | [prev] | [next] | [standalone]
| From | Mark Lloyd <not.email@all.invalid> |
|---|---|
| Date | 2025-04-05 16:22 +0000 |
| Subject | Re: Amazon (Was: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) |
| Message-ID | <67f158cc$0$19$882e4bbb@reader.netnews.com> |
| In reply to | #18278 |
On Fri, 4 Apr 2025 21:26:10 +0200, J.O. Aho wrote: > On 04/04/2025 19.09, Carlos E.R. wrote: >> On 2025-04-04 18:06, Java Jive wrote: > >>> but amazon.es wanted me to sign in >> >> Funny, when I try your link, it asks ME to login! >> >> If I click on "see more reviews", it asks for my login. I did not >> continue :-( >> >> >> Something has changed at Amazon :-/ > > Yeah, nowadays you have a unified accounts which you should be able to > login on multiple different sites. Like when you're on a different site, and see a button "Log in with Amazon"? I've also used some sites that sell something and have a "Pay with Amazon" button. -- Mark Lloyd http://notstupid.us/ "It cannot be too often repeated, that truth scorns the assistance of miracle." [Robert G. Ingersoll]
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-04-05 21:01 +0200 |
| Subject | Re: Amazon (Was: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) |
| Message-ID | <i9b8clxkbr.ln2@Telcontar.valinor> |
| In reply to | #18303 |
On 2025-04-05 18:22, Mark Lloyd wrote: > On Fri, 4 Apr 2025 21:26:10 +0200, J.O. Aho wrote: > >> On 04/04/2025 19.09, Carlos E.R. wrote: >>> On 2025-04-04 18:06, Java Jive wrote: >> >>>> but amazon.es wanted me to sign in >>> >>> Funny, when I try your link, it asks ME to login! >>> >>> If I click on "see more reviews", it asks for my login. I did not >>> continue :-( >>> >>> >>> Something has changed at Amazon :-/ >> >> Yeah, nowadays you have a unified accounts which you should be able to >> login on multiple different sites. > > Like when you're on a different site, and see a button "Log in with > Amazon"? I've also used some sites that sell something and have a "Pay > with Amazon" button. > Those will not work for me. I use a separate, isolated, Firefox profile to deal with Amazon. Actually two, one for searching, and another for login and then purchasing. So they can no associate what I search with my email. I do the same with Gmail. And my normal profile has disabled Amazon cookies. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-04-06 14:44 +0200 |
| Message-ID | <ti9aclxdm6.ln2@Telcontar.valinor> |
| In reply to | #18251 |
On 2025-04-03 23:47, Paul wrote: > Fortunately, you have a PNP of idVendor=152d, idProduct=0578 > and it is a JMicron 578. Listed here: <https://www.smartmontools.org/wiki/Supported_USB-Devices_idVendor-0x1000#a0x1500idVendor0x1700> Description USB bridge idVendor:idProduct iManufacturer Option(s) Tested on Author / Reference Comment (bcdDevice) / iProduct RaidSonic JMicron 0x152d:0x0578 JMicron -d sat Linux 4.8 Noctiflore -d ICY BOX JMS567 SATA 6Gb/s usbjmicron IB-373U3 bridge does not work Enclosure with this USB 3.0 UAS bridge (Pasting a table here is a pain not being able to use html) -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | vallor <vallor@cultnix.org> |
|---|---|
| Date | 2025-04-04 06:30 +0000 |
| Message-ID | <m59ck7Fk3odU1@mid.individual.net> |
| In reply to | #18245 |
On Thu, 3 Apr 2025 22:01:43 +0200, "Carlos E.R." <robin_listas@es.invalid> 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 <https://www.amazon.es/dp/B083Q8Z2KM> > > I think it is this one: > > <https://yottamaster.com/products/yottamaster-aluminum-5-bay-usb3-1- 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? -- -v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti OS: Linux 6.14.0 Release: Mint 22.1 Mem: 258G "I'll have what the guy on the floor is having."
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-04-04 03:53 -0400 |
| Message-ID | <vso35r$2utuc$1@dont-email.me> |
| In reply to | #18259 |
On Fri, 4/4/2025 2:30 AM, vallor wrote: > On Thu, 3 Apr 2025 22:01:43 +0200, "Carlos E.R." <robin_listas@es.invalid> > 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 <https://www.amazon.es/dp/B083Q8Z2KM> >> >> I think it is this one: >> >> <https://yottamaster.com/products/yottamaster-aluminum-5-bay-usb3-1- > 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. Paul
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-04-04 12:53 +0200 |
| Message-ID | <9aq4clxn5a.ln2@Telcontar.valinor> |
| In reply to | #18260 |
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." <robin_listas@es.invalid> >> 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 <https://www.amazon.es/dp/B083Q8Z2KM> >>> >>> I think it is this one: >>> >>> <https://yottamaster.com/products/yottamaster-aluminum-5-bay-usb3-1- >> 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.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-04-04 13:44 +0200 |
| Message-ID | <bat4clx6tg.ln2@Telcontar.valinor> |
| In reply to | #18266 |
On 2025-04-04 12:53, Carlos E.R. wrote: >> It might depend on what firmware is in the box. >> >> https://ralimtek.com/posts/2021/jms578/ ... > «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. Google (<https://serverfault.com/questions/907615/how-to-make-a-raid-disk-light-blink-on-linux>): use "ledctl locate=/dev/sdd". Installed "ledmon". Doesn't work. Telcontar:~ # ledctl locate /dev/sde /dev/shm/ledmon.conf: does not exist, using global config file /etc/ledmon.conf: does not exist, using built-in defaults ledctl: controller discovery: /sys/devices/pci0000:00/0000:00:08.3/0000:31:00.0 - enclosure management not supported. ledctl: controller discovery: /sys/devices/pci0000:00/0000:00:08.2/0000:30:00.0 - enclosure management not supported. ledctl: controller discovery: /sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0 - enclosure management not supported. ledctl: controller discovery: /sys/devices/pci0000:00/0000:00:01.3/0000:03:00.1 - enclosure management not supported. ledctl: missing operand(s)... run ledctl --help for details. Telcontar:~ # ledctl locate=/dev/sde /dev/shm/ledmon.conf: does not exist, using global config file /etc/ledmon.conf: does not exist, using built-in defaults ledctl: controller discovery: /sys/devices/pci0000:00/0000:00:08.3/0000:31:00.0 - enclosure management not supported. ledctl: controller discovery: /sys/devices/pci0000:00/0000:00:08.2/0000:30:00.0 - enclosure management not supported. ledctl: controller discovery: /sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0 - enclosure management not supported. ledctl: controller discovery: /sys/devices/pci0000:00/0000:00:01.3/0000:03:00.1 - enclosure management not supported. ledctl: /dev/sde: device not supported ledctl: IBPI LOCATE: missing block device(s)... pattern ignored. Telcontar:~ # Google: while :; do smartctl -a /dev/sdf; done; Yes, this one works. Improved variant: Telcontar:~ # while :; do smartctl -a /dev/sde; sleep 2; done 1>/dev/null ^C Telcontar:~ # -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
Page 1 of 2 [1] 2 Next page →
Back to top | Article view | alt.comp.os.windows-11
csiph-web