Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Original Poster
Rep:
Well, as they say, the guilty always come back to the scene of the crime ... .
At long last (before the next reorganization of my disks) I tried it what with the extraction of the .ima file, dd'ed it over to an USB-stick and booted that -- and got
Code:
- Init Disk Bad or missing Command Interpreter: command.com /P /E:256
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Original Poster
Rep:
Quote:
Originally Posted by JZL240I-U
Ah okay. Thanks for the link. I think I'll risk it for learning's sake ... I'll mark this thread as solved...
I learned, that there is no real reason for win and mac versions. The update will run under FreeDOS. I'll undo the [solved] label of the thread, updating the firmware still doesn't work.
Similar problem here: Seagate Expansion Desktop is not recognized. Since it is USB3, USB2 compatible, not SATA, I am afraid to run the application as proposed by Alecz20.
Problem: The external HD 2TB from Seagate worked fine in linux. There are two ext2 partitions and one vfat partition (empty). One of the ext2 is my backup, which I need by this time. Now opensuse does not recognize it anymore, as I show next. Googling showed similar troubles to exist, but none of them solved.
> lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 009: ID 0bc2:3320 Seagate RSS LLC SRD00F2 [Expansion Desktop Drive]
What dev is it? Unknown:
Code:
> sudo /usr/sbin/fdisk -l
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes, 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x000777b1
Device Boot Start End Blocks Id System
/dev/sda1 * 123715584 165662719 20973568 83 Linux
/dev/sda2 165662720 1214240767 524289024 83 Linux
/dev/sda3 115345408 119539711 2097152 82 Linux swap / Solaris
/dev/sda4 1214240768 1953523711 369641472 83 Linux
Partition table entries are not in disk order
/dev/sda{1..5} belongs to the internal HD, not the external one. Additional outputs /dev/sda{1..3} were expected here, but they did not came.
However, kernel sees something, like serial numer, vendor:
Code:
> sudo dmesg | tail
[440442.772236] SFW2-INext-DROP-DEFLT IN=enp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:76d0:2bff:fe81:e911 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
[440698.724327] SFW2-INext-DROP-DEFLT IN=enp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:76d0:2bff:fe81:e911 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
[441210.436975] SFW2-INext-DROP-DEFLT IN=enp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:76d0:2bff:fe81:e911 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
[442233.848545] SFW2-INext-DROP-DEFLT IN=enp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:76d0:2bff:fe81:e911 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
[443712.658629] usb 2-1.1: new high-speed USB device number 9 using ehci-pci
[443712.805098] usb 2-1.1: New USB device found, idVendor=0bc2, idProduct=3320
[443712.805103] usb 2-1.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[443712.805105] usb 2-1.1: Product: Expansion Desk
[443712.805108] usb 2-1.1: Manufacturer: Seagate
[443712.805110] usb 2-1.1: SerialNumber: NA4M02XA
It seems the computer only detects the enclosure, not the drive inside. I would not flash this drive as it is. Instead try it on another machine or take out of the enclosure and connect it directly.
To rule out any Software issue, boot from a LiveCD/LiveUSB and check.
This is how dmesg should look like:
Code:
usb 3-3.4: New USB device found, idVendor=0bc2, idProduct=3320
usb 3-3.4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
usb 3-3.4: Product: Expansion Desk
usb 3-3.4: Manufacturer: Seagate
usb 3-3.4: SerialNumber: NAxxxxx
usb-storage 3-3.4:1.0: USB Mass Storage device detected
usb-storage 3-3.4:1.0: Quirks match for vid 0bc2 pid 3320: 2000000
scsi host11: usb-storage 3-3.4:1.0
...
scsi 9:0:0:0: Direct-Access Seagate Expansion Desk 0319 PQ: 0 ANSI: 6
sd 9:0:0:0: Attached scsi generic sg8 type 0
sd 9:0:0:0: [sdg] 732566646 4096-byte logical blocks: (3.00 TB/2.72 TiB)
sd 9:0:0:0: [sdg] Write Protect is off
sd 9:0:0:0: [sdg] Mode Sense: 2b 00 10 08
sd 9:0:0:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA
sd 9:0:0:0: [sdg] 732566646 4096-byte logical blocks: (3.00 TB/2.72 TiB)
sdg: sdg1 sdg2 sdg3
sd 9:0:0:0: [sdg] 732566646 4096-byte logical blocks: (3.00 TB/2.72 TiB)
sd 9:0:0:0: [sdg] Attached SCSI disk
Thank you for both replies. I tested the external HD in an older machine but newer kernel, 4.1.12, gentoo install. It immediately attributed a /dev name. It mounted smoothly on the first try. All the data are there, partitions file systems etc. So the hardware is perfect.
The review on link given by Alecz20 made use of kernel 3.19.
My current kernel in opensuse is 3.12.53. I think I'll just wait for kernel upgrade.
I had a similar issue on an Ubuntu system after I messed up some things in the kernel. It appears that I removed a package that included USB support of some sort. I solved the issue by plugging the hard drive directly in the SATA port.
Check that you have the same Linux kernel components on both machines. particularly:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.