Seagate's SeaTools for Linux won't start on my system. The file is rather old and in a funky format, but it looks like it ought to run. Nevertheless, it won't run. Can anyone tell me what's goi ng on? Here's what happens:
$ ls -l st-rwxr-xr-x. 1 jonrysh jonrysh 180149 Sep 12 2001 st $ file st st: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.2.5, not stripped
$ st
bash: ./st: No such file or directory $ strace st execve("./st", ["st"], 0x7ffc80690900 /* 76 vars */) = -1 ENOENT (No such file or directory) open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3 fstat(3, {st_mode=S_IFREG|0644, st_size=2997, ...}) = 0 read(3, "# Locale name alias data base.\n#"..., 4096) = 2997 read(3, "", 4096) = 0 close(3) = 0 open("/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) fstat(2, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 4), ...}) = 0 write(2, "strace: exec: No such file or di"..., 40strace: exec: No such file or directory ) = 40 getpid() = 18983 exit_group(1) = ? +++ exited with 1 +++
On Thu, 12 Apr 2018 06:05:12 -0700, Jonathan Ryshpan wrote:
Seagate's SeaTools for Linux won't start on my system. The file is rather old and in a funky format, but it looks like it ought to run. Nevertheless, it won't run. Can anyone tell me what's goi ng on? Here's what happens:
$ ls -l st-rwxr-xr-x. 1 jonrysh jonrysh 180149 Sep 12 2001 st $ file st st: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.2.5, not stripped
$ st
bash: ./st: No such file or directory $ strace st
What do you get for "ldd st"?
On Thu, 2018-04-12 at 15:37 +0200, Michael Schwendt wrote:
On Thu, 12 Apr 2018 06:05:12 -0700, Jonathan Ryshpan wrote:
Seagate's SeaTools for Linux won't start on my system. The file is rather old and in a funky format, but it looks like it ought to run. Nevertheless, it won't run. Can anyone tell me what's going on? Here's what happens:
$ ls -l st-rwxr-xr-x. 1 jonrysh jonrysh 180149 Sep 12 2001 st $ file st st: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.2.5, not stripped
$ st
bash: ./st: No such file or directory $ strace st
What do you get for "ldd st"?
$ ldd st
not a dynamic executable
On Thu, 12 Apr 2018 08:30:43 -0700, Jonathan Ryshpan wrote:
$ file st st: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.2.5, not stripped
$ st
bash: ./st: No such file or directory $ strace st
What do you get for "ldd st"?
$ ldd st
not a dynamic executable
You've tried that on x86_64 not i686, right? Have you installed basic runtime packages as to execute i386 programs? Such as glibc.i686?
On 04/12/18 21:05, Jonathan Ryshpan wrote:
Seagate's SeaTools for Linux won't start on my system. The file is rather old and in a funky format, but it looks like it ought to run. Nevertheless, it won't run. Can anyone tell me what's going on? Here's what happens:
Yes, it would appear that the utility is from 2001. If it hadn't been updated for changes in linux since that date it my not run.
$ ls -l st -rwxr-xr-x. 1 jonrysh jonrysh 180149 Sep 12 2001 st $ file st st: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.2.5, not stripped
$ st bash: ./st: No such file or directory
$ strace st execve("./st", ["st"], 0x7ffc80690900 /* 76 vars */) = -1 ENOENT (No such file or directory) open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3 fstat(3, {st_mode=S_IFREG|0644, st_size=2997, ...}) = 0 read(3, "# Locale name alias data base.\n#"..., 4096) = 2997 read(3, "", 4096) = 0 close(3) = 0 open("/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) fstat(2, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 4), ...}) = 0 write(2, "strace: exec: No such file or di"..., 40strace: exec: No such file or directory ) = 40 getpid() = 18983 exit_group(1) = ? +++ exited with 1 +++
Those files above don't exist on my system and "dnf whatprovides" for each of them returns "Error: No Matches found".
Now, you may be able to "force" it to work by installing glibc-langpack-en which provides /usr/share/locale/en_GB/LC_MESSAGES/libc.mo and then creating a link to it from one of the locations the program is looking for it. Or, it may get past that and trip over something else that has changed since 2001.
On 04/12/18 21:05, Jonathan Ryshpan wrote:
Seagate's SeaTools for Linux won't start on my system. The file is rather old and in a funky format, but it looks like it ought to run. Nevertheless, it won't run. Can anyone tell me what's going on? Here's what happens:
I suppose the larger question is, why use an old tool when most drives these days support S.M.A.R.T. ? I think SMART came into being around 2003.
On Fri, 2018-04-13 at 05:47 +0800, Ed Greshko wrote:
On 04/12/18 21:05, Jonathan Ryshpan wrote:
Seagate's SeaTools for Linux won't start on my system. The file is rather old and in a funky format, but it looks like it ought to run. Nevertheless, it won't run. Can anyone tell me what's going on? Here's what happens:
I suppose the larger question is, why use an old tool when most drives these days support S.M.A.R.T. ? I think SMART came into being around 2003.
A very good question. This drive, a Seagate USB Backup Plus Portable Drive, doesn't seem to support SMART: Here's a try: # smartctl --xall -T permissive /dev/sdc smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.15.15-300.fc27.x86_64] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: scsi error unsupported field in scsi command
=== START OF INFORMATION SECTION === Device Model: [No Information Found] Serial Number: [No Information Found] Firmware Version: [No Information Found] Device is: Not in smartctl database [for details use: -P showall] ATA Version is: [No Information Found] Local Time is: Fri Apr 13 21:56:30 2018 PDT SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported. SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled. A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
I'm trying to get SeaTools for DOS, which is a self booting test suite, intended to boot from a CD-ROM, running on a flash drive, but so far without success.
The problem that started all this is that the drive, which I use for backup, has started making an alarming beeping noise. After not using it for a while the noise has gone away, and I have made another backup successfully. Time to get a replacement; but I'm still curious what's going on with the drive.
On 04/14/18 13:09, Jonathan Ryshpan wrote:
On Fri, 2018-04-13 at 05:47 +0800, Ed Greshko wrote:
On 04/12/18 21:05, Jonathan Ryshpan wrote:
Seagate's SeaTools for Linux won't start on my system. The file is rather old and in a funky format, but it looks like it ought to run. Nevertheless, it won't run. Can anyone tell me what's going on? Here's what happens:
I suppose the larger question is, why use an old tool when most drives these days support S.M.A.R.T. ? I think SMART came into being around 2003.
A very good question. This drive, a Seagate USB Backup Plus Portable Drive, doesn't seem to support SMART: Here's a try: # smartctl --xall -T permissive /dev/sdc smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.15.15-300.fc27.x86_64] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: scsi error unsupported field in scsi command
=== START OF INFORMATION SECTION === Device Model: [No Information Found] Serial Number: [No Information Found] Firmware Version: [No Information Found] Device is: Not in smartctl database [for details use: -P showall] ATA Version is: [No Information Found] Local Time is: Fri Apr 13 21:56:30 2018 PDT SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported. SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled. A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
I'm trying to get SeaTools for DOS, which is a self booting test suite, intended to boot from a CD-ROM, running on a flash drive, but so far without success.
The problem that started all this is that the drive, which I use for backup, has started making an alarming beeping noise. After not using it for a while the noise has gone away, and I have made another backup successfully. Time to get a replacement; but I'm still curious what's going on with the drive.
That's a bummer.
If you use "parted /dev/sdc" and "print". It should tell you the make/model of the drive.
On 04/13/2018 10:09 PM, Jonathan Ryshpan wrote:
A very good question. This drive, a Seagate USB Backup Plus Portable Drive, doesn't seem to support SMART: Here's a try:
That's probably your problem. There's a USB to SATA converter inside that is not passing the SMART commands to the drive. I would be extremely surprised if that old Seagate software would be able to handle it.
-
Ed Greshko -
Jonathan Ryshpan -
Michael Schwendt -
Samuel Sieb