Custom Query (1405 matches)

$ ln -s /dev/sda /tmp/foo $ smartctl /tmp/foo smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, ​http://smartmontools.sourceforge.net

/tmp/foo: Unable to detect device type ...

$ smartctl /dev/sda # this works fine

$ smartctl -a /dev/block/8:0 # FAIL, as above

$ smartctl /dev/disk/by-path/pci-0000\:00\:1f.2-scsi-0\:0\:0\:0 # this works fine, too

Even if all the links point to /dev/sda, only some of them can be specified as arguments to smartctl - which does not make sence IMHO.

I would expect any symbolic link (which may be nested quite deep) that finally resolves to a device should allow successful execution of smartctl.

In my use case, I have quite a bunch of disks that are used for experiments and switched between machines regularily. Therefore I set up symlinks like /data/dev/disk1 -> /dev/disk/by-id/ABC-123456 with a fixed mapping of the disk$i names and prefer to access the devices via /data/dev/disk$i (and mount them to /data/disk$i) so I don't have to care which /dev/sdX name it currently has (and I don't accidentally access the wrong one - I don't care about the port where it is connected but about the actual physical disk). Using /dev/disk/by-id/ABC-123456 directly is quite cumbersome because they are quite long, look different from vendor to vendor and are not contiguous. UUIDs or something similar is not useful either because the disks get repartitioned and filesystems get recreated regularily. While sfdisk, mkfs, mount, hdparm, ... work in this setup, smartctl does not.

Andreas

For unknown reasons, I've got around 2TB (assuming 512 bytes per sector) of unreadable sectors:

smartd[5904]: Device: /dev/twa0 [3ware_disk_29], 4294967295 Currently unreadable (pending) sectors smartd[5904]: Device: /dev/twa0 [3ware_disk_29], 4294967295 Offline uncorrectable sectors

The disk is a 750GB ST3750640A with firmware version 3.AAE. The RAID controller has not reported any issues with this disk. There are multiple disks of this model and firmware revision attached. This is the only abnormal one. As smartmontools is reporting this as an issue, upstream monitoring systems are being triggered. Can a way to supress this specific number of bad sectors, or condition (2TB on a 750GB disk) be created?

Nor does disk appear to have an issue:

START OF READ SMART DATA SECTION

SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 8040 - # 2 Extended offline Interrupted (host reset) 30% 8027 - # 3 Extended offline Completed without error 00% 7904 - # 4 Extended offline Completed without error 00% 7881 - # 5 Extended offline Completed without error 00% 7744 - # 6 Extended offline Completed without error 00% 7597 - # 7 Extended offline Completed without error 00% 7576 - # 8 Extended offline Completed without error 00% 7523 - # 9 Extended offline Completed without error 00% 7500 - #10 Extended offline Completed without error 00% 7376 - #11 Extended offline Completed without error 00% 7353 - #12 Extended offline Completed without error 00% 7204 - #13 Extended offline Completed without error 00% 7057 - #14 Extended offline Completed without error 00% 6889 - #15 Extended offline Completed without error 00% 6764 - #16 Extended offline Completed without error 00% 6596 - #17 Extended offline Completed without error 00% 6449 - #18 Extended offline Completed without error 00% 6303 - #19 Extended offline Completed without error 00% 6155 - #20 Extended offline Completed without error 00% 6008 - #21 Extended offline Completed without error 00% 5863 -

Regards, John Jore

Please add scterc set command to smartd if possible