Oh. Um, try the -T permissive option (and possibly more than one of them, like ‘-T permissive -T permissive’ IIRC, but if its through a USB to sata (or whatever) device, then you’ll probably need to use the -d TYPE option (see the man page for details). But try permissive first.
Rusty
From: PLUG-discuss [mailto:plug-discuss-bounces@lists.phxlinux.org] On Behalf Of Michael
Sent: Thursday, November 29, 2018 7:38 AM
To: PLUG
Subject: Re: rm
Thank you so much. But unfortunately it is saying:
$ sudo smartctl -a /dev/sdc
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.15.0-39-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org<http://www.smartmontools.org>
Read Device Identity failed: scsi error unsupported field in scsi command
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
I don't know if this matters but it is an external drive.
On Thu, Nov 29, 2018 at 9:28 AM Carruth, Rusty <Rusty.Carruth@smartm.com<mailto:Rusty.Carruth@smartm.com>> wrote:
Nope, you didn’t break anything. For some reason, they called it ‘smartmontools’, so use that instead of smartctl in the apt-get command.
(Actually, at one level smartmontools makes sense as a name, but it makes remembering what to type a bit harder when doing the apt-get…)
Rusty
From: PLUG-discuss [mailto:plug-discuss-bounces@lists.phxlinux.org<mailto:plug-discuss-bounces@lists.phxlinux.org>] On Behalf Of Michael
Sent: Wednesday, November 28, 2018 6:35 PM
To: PLUG
Subject: Re: rm
I think I broke it!
bmike1@MikesBeast ~ $ sudo hdparm -a /dev/sdc
[sudo] password for bmike1:
/dev/sdc:
readahead = 256 (on)
bmike1@MikesBeast ~ $ sudo smartctl -a /dev/sdc
sudo: smartctl: command not found
bmike1@MikesBeast ~ $ sudo smartctl -a /dev/sdc
sudo: smartctl: command not found
bmike1@MikesBeast ~ $ sudo apt install smartctl
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package smartctl is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'smartctl' has no installation candidate
bmike1@MikesBeast ~ $
On Wed, Nov 28, 2018 at 12:24 PM Carruth, Rusty <Rusty.Carruth@smartm.com<mailto:Rusty.Carruth@smartm.com>> wrote:
Running hdparm -a /dev/sda on one of my machines:
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-24-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org<http://www.smartmontools.org>
=== START OF INFORMATION SECTION ===
Model Family: Seagate Constellation ES.3
Device Model: ST1000NM0033-9ZM173
…
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
….
Self-test execution status: ( 0) The previous self-test routine completed
…
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x010f 084 063 --- Pre-fail Always - 235752913
3 Spin_Up_Time 0x0103 096 096 --- Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 --- Old_age Always - 41
5 Reallocated_Sector_Ct 0x0133 100 100 --- Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 090 060 --- Pre-fail Always - 983913522
9 Power_On_Hours 0x0032 082 082 --- Old_age Always - 15937
10 Spin_Retry_Count 0x0013 100 100 --- Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 --- Old_age Always - 40
184 End-to-End_Error 0x0032 100 100 --- Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 --- Old_age Always - 0
188 Command_Timeout 0x0032 100 100 --- Old_age Always - 0
189 High_Fly_Writes 0x003a 100 100 --- Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 066 056 --- Old_age Always - 34 (Min/Max 29/39)
191 G-Sense_Error_Rate 0x0032 100 100 --- Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 --- Old_age Always - 39
193 Load_Cycle_Count 0x0032 100 100 --- Old_age Always - 1651
194 Temperature_Celsius 0x0022 034 044 --- Old_age Always - 34 (0 22 0 0 0)
195 Hardware_ECC_Recovered 0x001a 050 014 --- Old_age Always - 235752913
196 Reallocated_Event_Count 0x0032 000 000 --- Old_age Always - 21845
197 Current_Pending_Sector 0x0012 100 100 --- Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 --- Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 --- Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 --- Old_age Offline - 51784420702786
241 Total_LBAs_Written 0x0000 100 253 --- Old_age Offline - 79938736737
242 Total_LBAs_Read 0x0000 100 253 --- Old_age Offline - 90381241252
SMART Error Log Version: 1
No Errors Logged
…
Notice that we have ‘pre-fail’ and ‘old-age’ above, and especially the ‘Overall-health self-assessment’. That one is the one that the BIOS checks to see if the drive is dying.
The important ones in the above list, from the point of view of failure alerting (IMHO), are reallocated sector count (5), raw read error rate (1), attributes 10-188, hardware ecc recovered (195), reallocated event count (196), offline uncorrectable (198). (If you see a lot of UDMA CRC Errors, that’s probably a cabling issue, assuming I actually understand what the vendor is using that attribute for!).
First, let me back up and say that, since there were no errors logged, this drive is PROBABLY happy and not going to fail ‘real soon’. But, the raw read error and seek error rates aren’t as low as I’d like. On the other hand, this IS a rotating drive, so maybe that’s normal. On the other hand, I compared that drive with another rotator, and that other one has 0 raw read errors, 0 reallocated sectors, 0 seek errors, 0 reallocated events, 0 offline uncorrectable, etc. The second one has been running 21,596 hours.
A third drive has similar zeros for errors, but yet has had 8 errors:
ATA Error Count: 8 (device log contains only the most recent five errors)
…
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 8 occurred at disk power-on lifetime: 5610 hours (233 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 18 2d aa 03 e0 Error: ICRC, ABRT at LBA = 0x0003aa2d = 240173
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ca 00 28 1d aa 03 e0 08 48d+06:41:01.204 WRITE DMA
Anyway, watch these numbers, and if they start changing much start looking for a replacement disk ☺ If you start getting lots of errors in the error log, that’s probably significant also.
Rusty
From: PLUG-discuss [mailto:plug-discuss-bounces@lists.phxlinux.org<mailto:plug-discuss-bounces@lists.phxlinux.org>] On Behalf Of Michael
Sent: Tuesday, November 27, 2018 11:00 AM
To: PLUG
Subject: Re: rm
What do the p r e f a i l attributes look like?
On Tue, Nov 27, 2018, 00:28 Carruth, Rusty <Rusty.Carruth@smartm.com<mailto:Rusty.Carruth@smartm.com> wrote:
You might want to check syslog (or messages) to see if the drive is getting errors. (which is to say, getting ready to die)
Or use smartctl -a to see what the SMART attributes say (look for the ‘pre-fail’ attributes). Or, best, do both.
Rusty
From: PLUG-discuss [mailto:plug-discuss-bounces@lists.phxlinux.org<mailto:plug-discuss-bounces@lists.phxlinux.org>] On Behalf Of Michael
Sent: Thursday, November 22, 2018 8:50 AM
To: PLUG
Subject: Re: rm
I ran fsck. It just returned through. So then I reformatted it with gparted. So all is well (I guess). I did have to restart the computer after the reformat though (don't remember why) but everything seemed okay. Oh yeaaaaa! I think I had to restart it because it would not unmount and I figured I would try to restart it and if it would gracefully do so it would be good. And it did and upon restart the drive auto mounted.
On Wed, Nov 21, 2018 at 11:56 PM Eric Oyen <eric.oyen@icloud.com<mailto:eric.oyen@icloud.com>> wrote:
Ok, unmount the drive, then run
Sudo fsck <your device here>
When completed, remount and then try to remove the files using:
Sudo rm -rf <name of files here>
-Eric
On Nov 21, 2018, at 8:53 PM, Michael <bmike1@gmail.com<mailto:bmike1@gmail.com>> wrote:
this is interesting: I tried accessing 'Neil' from the GUI but get an error:
Sorry, could not display all the contents of "Neil": Error when getting information for file '/media/bmike1/Seagate Expansion Drive/Documents/Business/CablingJobs/Neil/IMG_20150205_180721.jpg': Input/output error)
and when I attempt to access it from a tty get:
$ ls Neil/
ls: cannot access 'Neil/IMG_20150205_180604.jpg': Input/output error
ls: cannot access 'Neil/IMG_20150205_180721.jpg': Input/output error
ls: cannot access 'Neil/IMG_20150205_180827.jpg': Input/output error
ls: cannot access 'Neil/IMG_20150205_180903.jpg': Input/output error
ls: cannot access 'Neil/IMG_20150205_180917.jpg': Input/output error
ls: cannot access 'Neil/quote.docx': Input/output error
IMG_20150205_180559.jpg IMG_20150205_180827.jpg quote.docx
IMG_20150205_180604.jpg IMG_20150205_180903.jpg
IMG_20150205_180721.jpg IMG_20150205_180917.jpg
On Wed, Nov 21, 2018 at 10:44 PM Michael <bmike1@gmail.com<mailto:bmike1@gmail.com>> wrote:
how do I delete the following files>?
/media/bmike1/Seagate Expansion Drive/Documents/Business/CablingJobs $ sudo rm -rf Neil/
rm: cannot remove 'Neil/IMG_20150205_180604.jpg': Input/output error
rm: cannot remove 'Neil/IMG_20150205_180721.jpg': Input/output error
rm: cannot remove 'Neil/IMG_20150205_180827.jpg': Input/output error
rm: cannot remove 'Neil/IMG_20150205_180903.jpg': Input/output error
rm: cannot remove 'Neil/IMG_20150205_180917.jpg': Input/output error
rm: cannot remove 'Neil/quote.docx': Input/output error
these are the only files on the drive.
--
:-)~MIKE~(-:
--
:-)~MIKE~(-:
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org<mailto:PLUG-discuss@lists.phxlinux.org>
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org<mailto:PLUG-discuss@lists.phxlinux.org>
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
--
:-)~MIKE~(-:
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org<mailto:PLUG-discuss@lists.phxlinux.org>
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org<mailto:PLUG-discuss@lists.phxlinux.org>
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
--
:-)~MIKE~(-:
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org<mailto:PLUG-discuss@lists.phxlinux.org>
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
--
:-)~MIKE~(-:
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
(text/plain)