Re: [DNG] Can this drive be saved?
On 2020-09-04 22:25, Hendrik Boom wrote: On Fri, Sep 04, 2020 at 02:47:38PM -0500, goli...@devuan.org wrote: A few posts after yours Hendrik suggested checking the lost and found directory and in it I found 57 folders and 15798 other items totaling 16.6 GB. They are mostly edits from audacity (.au) and avidemux (in C). Also some wav and mp3 and graphics stuff too. I couldn't find the associated mpgs or isos and there seems to be some other things missing here and there. Everything in the lost and found can be deleted. Maybe if I do it in small chunks, it won't explode. LOL! Delete the contents all you want, but keep the lost and found directory. -- hendrik Understood. I realize that directory is necessary and would only delete the contents. But a reminder is always good and might be useful to someone else. :) golinux ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
On Fri, Sep 04, 2020 at 11:25:21PM -0400, Hendrik Boom wrote: > Delete the contents all you want, but keep the lost and found directory. If you delete lost+found by accident, you can recreate it with mklost+found(8). On Sat, Sep 05, 2020 at 12:26:21PM +0900, Simon Walter wrote: > Reallocation, to my knowledge, should happen in the background. It's > *possible* that the reallocation event and the FS corruption are unrelated. My understanding is that the drive won't attempt to reallocate a sector until that sector is written to. So, if the e2fsck -f did try to write to that sector, the drive did reallocate it in the background. I do stand to be corrected as always. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] RFC: wiki software
On Fri, Sep 04, 2020 at 07:53:54PM -0700, tom wrote: > How many Gemini and Kristall (or any other Gemini client of your > choosing) https://gemini.circumlunar.space/ As it turns out, we were talking about that at the last meeting, and there's probably interest in it. -- Mason Loring Bliss ma...@blisses.orgEwige Blumenkraft! (if awake 'sleep (aref #(sleep dream) (random 2))) -- Hamlet, Act III, Scene I signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
On Fri, Sep 04, 2020 at 09:19:42PM -0500, goli...@devuan.org wrote: > === START OF READ SMART DATA SECTION === > SMART Status command failed: scsi error medium or hardware error (serious) > SMART overall-health self-assessment test result: PASSED > Warning: This result is based on an Attribute check. You said this is a USB attached drive. That probably showed up because the USB bridge doesn't support passing a given SMART command(s) to the drive. > SMART Attributes Data Structure revision number: 16 > Vendor Specific SMART Attributes with Thresholds: > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED > WHEN_FAILED RAW_VALUE --- snip --- > 5 Reallocated_Sector_Ct 0x0033 199 199 140Pre-fail Always > - 1 So we know that one sector was reallocated. Whether that happened when e2fsck attempted to write to it, or earlier, we don't know. > 196 Reallocated_Event_Count 0x0032 199 199 000Old_age Always > - 1 > 197 Current_Pending_Sector 0x0032 200 200 000Old_age Always > - 0 > 198 Offline_Uncorrectable 0x0030 200 200 000Old_age Offline > - 0 Other than that one sector, the rest of the drive looks to be useable so far. > SMART Self-test log structure revision number 1 > Num Test_DescriptionStatus Remaining LifeTime(hours) > LBA_of_first_error > # 1 Extended offlineCompleted without error 00%55 - Again, that confirms to me the drive reallocated one bad sector, and the rest of it seems to be OK so far. > SMART Selective self-test log data structure revision number 1 > SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS > 100 Not_testing > 200 Not_testing > 300 Not_testing > 400 Not_testing > 500 Not_testing > Selective self-test flags (0x0): You asked about this in an earlier message. The selective test portion is used to report the status of the automatic testing the drive does by itself if that's enabled, and your smartctl output shows that automatic self tests are enabled on your drive. All the above says is that the drive isn't running automatic self tests right now, so nothing to worry about here. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
On Fri, Sep 04, 2020 at 02:00:13PM -0700, Gregory Nowak wrote: > On Fri, Sep 04, 2020 at 03:03:55PM -0500, goli...@devuan.org wrote: > > This particular drive has no data that is not backed up elsewhere so I am > > comfortable experimenting with it a bit as a learning experience. OTOH, > > trashing the remaining life it has for no reason wouldn't make sense. > > You're not alone in that line of reasoning. I also use drives with > reallocated sectors. I however do make sure I take frequent backups of > those drives as I've stated in this thread before. I also verify the > new backups before deleting the old to make sure I haven't backed up > bad data. While some of the drives I've had died almost right away > after starting to reallocate sectors, others are still doing fine so > far years later. > > If drives grew on trees I might not be taking this approach. Since > they don't grow on trees, and since I like to squeeze the last drop > out of things I own before recycling them (including cell phones and > computers), > this is the approach I personally take. Others have disagreed with > this approach, and others will likely continue to disagree. I would > also add my voice to those who suggested doing a long SMART test. Good luck. I always do a through write/read test on every new drive to check all of it can be written and read back correctly. I've sent some of them back under warranty and gotten a replacement. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
On Fri, Sep 04, 2020 at 02:47:38PM -0500, goli...@devuan.org wrote: > > A few posts after yours Hendrik suggested checking the lost and found > directory and in it I found 57 folders and 15798 other items totaling 16.6 > GB. They are mostly edits from audacity (.au) and avidemux (in C). Also some > wav and mp3 and graphics stuff too. I couldn't find the associated mpgs or > isos and there seems to be some other things missing here and there. > > Everything in the lost and found can be deleted. Maybe if I do it in small > chunks, it won't explode. LOL! Delete the contents all you want, but keep the lost and found directory. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
On 9/5/20 11:19 AM, goli...@devuan.org wrote: On 2020-09-04 20:46, Simon Walter wrote: On 9/5/20 1:34 AM, Andreas Messer wrote: Hi golinux, On Fri, Sep 04, 2020 at 01:50:07AM -0500, goli...@devuan.org wrote: On 2020-09-01 00:07, goli...@devuan.org wrote: [...] I have no idea how reliable the repaired drive is after this radical surgery. Can it be written to or files deleted? Should I even try? [...] I wouldn't use a drive anymore which has started reallocating sectors, well which has reallocated sectors all. It's on it's way out for sure. However, I am interested in how you are able to know that sectors on golinux's disk have been relocated - from the information provided to this mailing list. I know it's possible to see that in the SMART data, but I didn't see that posted. Are short reads always surface errors? Best regards, Simon Simon . . . SMART data attached. I hadn't noticed this before . . . sounds ominous . . . SMART Status command failed: scsi error medium or hardware error (serious) Note that I ran this from GSmartControl not a terminal. I think it's because you are connected via USB. From my experience, the best way, possibly the only thorough way, to diagnose a SATA disk drive is connected to a SATA controller directly, which is why I really like notebooks that have eSATA ports. About my above question to Andreas, I am interested to learn if this is indeed the case: short reads indicate surface error. I have gotten this error over USB before. When connecting the same disk to a known working SATA controller, I was able to use it fine and no errors occurred. USB -> SATA controllers/cases in my experience are of poor quality and fail before the disk does. I am not one to hang on to a failing disk, but you sound thorough. So I'd suggest using a SATA controller to read the SMART data and run other diagnostics. If you are a data hoarder and like disks, I'd suggest getting your hands on some hardware that has a SATA controller. It doesn't need to be fancy or new. Pretty much any working desktop is fine. In your SMART data: Reallocated_Sector_Ct = 1 However: SMART overall-health self-assessment test result: PASSED Reallocation, to my knowledge, should happen in the background. It's *possible* that the reallocation event and the FS corruption are unrelated. If that count keeps going up, don't use the disk. Eventually the surface will not be able to store data/be magnetised. I am keen to learn more about disk recovery. So please, anyone, correct me if I am wrong. Best regards, Simon ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] RFC: wiki software
On Fri, 4 Sep 2020 00:51:01 -0400 Mason Loring Bliss wrote: > Hi all! We're looking for opinions about wiki software. First choice > at the moment is TWiki but we want more options and more perspective > to get us to the best possible decision. > > Goals, not in a particular order: > > * Ideally not Python, PHP, Java unless it's otherwise perfect. > > * Supports ACLs for per-account and/or per-group editing privs. > Ability to disable edits by people not logged in. > > * Potentially supports ACL-based visibility in addition to editing > privs. > > * Supports at least a minimum live editor, with mark-up being fine - > no need for WYSIWYG. > > * Flat files on the back end - ideally content can be captured to > version control, can come from version control, etc. > > * JavaScript not required for clients. > > We'll continue poking at TWiki while we gather data. > How many Gemini and Kristall (or any other Gemini client of your choosing) https://gemini.circumlunar.space/ native format is markdown, supports data and query entry, identities based on client certificates supporting both persistent and transient identities. Protocol is dead simple to code for. Already a wide choice of client software https://gemini.circumlunar.space/clients.html with no degradation of service at all for even text-only clients. Compatible with DIY-computing. The entire spec is readable with 15 minutes of your time gemini://gemini.circumlunar.space/docs/specification.gmi and only 31K big. -- / QOTD: \ || \ "I'm just a boy named 'su'..." / \ \ /\ /\ //\\_//\\ \_ _// / / * * \/^^^] \_\O/_/[ ] / \_[ / \ \_ / / [ [ / \/ _/ _[ [ \ /_/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
On 2020-09-04 20:46, Simon Walter wrote: On 9/5/20 1:34 AM, Andreas Messer wrote: Hi golinux, On Fri, Sep 04, 2020 at 01:50:07AM -0500, goli...@devuan.org wrote: On 2020-09-01 00:07, goli...@devuan.org wrote: [...] I have no idea how reliable the repaired drive is after this radical surgery. Can it be written to or files deleted? Should I even try? [...] I wouldn't use a drive anymore which has started reallocating sectors, well which has reallocated sectors all. It's on it's way out for sure. However, I am interested in how you are able to know that sectors on golinux's disk have been relocated - from the information provided to this mailing list. I know it's possible to see that in the SMART data, but I didn't see that posted. Are short reads always surface errors? Best regards, Simon Simon . . . SMART data attached. I hadn't noticed this before . . . sounds ominous . . . SMART Status command failed: scsi error medium or hardware error (serious) Note that I ran this from GSmartControl not a terminal. golinux smartctl 6.4 2014-10-07 r4002 [i686-linux-3.16.0-4-686-pae] (local build) Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green Device Model: WDC WD10EACS-00D6B1 Serial Number:WD-WCAU49079944 LU WWN Device Id: 5 0014ee 202a5ed4c Firmware Version: 01.01A01 User Capacity:1,000,204,886,016 bytes [1.00 TB] Sector Size: 512 bytes logical/physical Device is:In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 2.5, 3.0 Gb/s Local Time is:Fri Sep 4 21:05:44 2020 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART Status command failed: scsi error medium or hardware error (serious) SMART overall-health self-assessment test result: PASSED Warning: This result is based on an Attribute check. General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection:(24000) seconds. Offline data collection capabilities:(0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 2) minutes. Extended self-test routine recommended polling time:( 275) minutes. Conveyance self-test routine recommended polling time:( 5) minutes. SCT capabilities: (0x303f) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 198 196 051Pre-fail Always - 1183 3 Spin_Up_Time0x0027 160 160 021Pre-fail Always - 6991 4 Start_Stop_Count0x0032 100 100 000Old_age Always - 66 5 Reallocated_Sector_Ct 0x0033 199 199 140Pre-fail Always - 1 7 Seek_Error_Rate 0x002e 100 253 000Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000Old_age Always - 56 10 Spin_Retry_Count0x0032 100 253 000Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000Old_age Always - 0 12 Power_Cycle_Count 0x0032
Re: [DNG] Can this drive be saved?
On 9/5/20 1:34 AM, Andreas Messer wrote: Hi golinux, On Fri, Sep 04, 2020 at 01:50:07AM -0500, goli...@devuan.org wrote: On 2020-09-01 00:07, goli...@devuan.org wrote: [...] I have no idea how reliable the repaired drive is after this radical surgery. Can it be written to or files deleted? Should I even try? [...] I wouldn't use a drive anymore which has started reallocating sectors, well which has reallocated sectors all. It's on it's way out for sure. However, I am interested in how you are able to know that sectors on golinux's disk have been relocated - from the information provided to this mailing list. I know it's possible to see that in the SMART data, but I didn't see that posted. Are short reads always surface errors? Best regards, Simon ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
On 2020-09-04 19:24, spiralofhope wrote: On Fri, 04 Sep 2020 15:03:55 -0500 goli...@devuan.org wrote: ...2 new 500 GB WD Black drives... You have good taste. LOL! It's a learning process if you're paying attention. Note that the funky drive I'm currently playing with is a 1 TB WD Caviar Green. I've had a Black arrive DOA but once they are running it's always been like the Energizer Bunny. Not sure if they still have the 5 yr. warranty though . . . While I'm here I'll post the Selective Self-test log which supposedly completed without error a few minutes ago. It took just over 4 hours. It doesn't look quite right to me; I thought there would be more verbose details. Am I missing something? I have never run this test before: Complete selective self-test log: SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 100 Not_testing 200 Not_testing 300 Not_testing 400 Not_testing 500 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. Some comments on exactly what that means would be appreciated. Do I need to do something else? Should I now have more confidence in this drive? Thanks again. golinux ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] RFC: wiki software
On Fri, 4 Sep 2020 00:51:01 -0400 Mason Loring Bliss wrote: Dokuwiki and PMWiki is very best wiki engine > Hi all! We're looking for opinions about wiki software. First choice > at the moment is TWiki but we want more options and more perspective > to get us to the best possible decision. > > Goals, not in a particular order: > > * Ideally not Python, PHP, Java unless it's otherwise perfect. > > * Supports ACLs for per-account and/or per-group editing privs. > Ability to disable edits by people not logged in. > > * Potentially supports ACL-based visibility in addition to editing > privs. > > * Supports at least a minimum live editor, with mark-up being fine - > no need for WYSIWYG. > > * Flat files on the back end - ideally content can be captured to > version control, can come from version control, etc. > > * JavaScript not required for clients. > > We'll continue poking at TWiki while we gather data. > > -- > Mason Loring Bliss ma...@blisses.orgEwige > Blumenkraft! (if awake 'sleep (aref #(sleep dream) (random 2))) -- > Hamlet, Act III, Scene I -- att, pekman ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
On Fri, 04 Sep 2020 15:03:55 -0500 goli...@devuan.org wrote: > ...2 new 500 GB WD Black drives... You have good taste. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
On Fri, Sep 04, 2020 at 03:03:55PM -0500, goli...@devuan.org wrote: > This particular drive has no data that is not backed up elsewhere so I am > comfortable experimenting with it a bit as a learning experience. OTOH, > trashing the remaining life it has for no reason wouldn't make sense. You're not alone in that line of reasoning. I also use drives with reallocated sectors. I however do make sure I take frequent backups of those drives as I've stated in this thread before. I also verify the new backups before deleting the old to make sure I haven't backed up bad data. While some of the drives I've had died almost right away after starting to reallocate sectors, others are still doing fine so far years later. If drives grew on trees I might not be taking this approach. Since they don't grow on trees, and since I like to squeeze the last drop out of things I own before recycling them (including cell phones and computers), this is the approach I personally take. Others have disagreed with this approach, and others will likely continue to disagree. I would also add my voice to those who suggested doing a long SMART test. Good luck. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
On 2020-09-04 11:34, Andreas Messer wrote: Hi golinux, On Fri, Sep 04, 2020 at 01:50:07AM -0500, goli...@devuan.org wrote: On 2020-09-01 00:07, goli...@devuan.org wrote: [...] I have no idea how reliable the repaired drive is after this radical surgery. Can it be written to or files deleted? Should I even try? [...] I wouldn't use a drive anymore which has started reallocating sectors, well which has reallocated sectors all. During manufacturing the drive, it can happen that some sectors are bad, but these sectors are already "reallocated" during the manufacturing end test and will not show up in the SMART information. When a magnetic disc drive starts reallocating sectors, it is an indicator that something within drive starts to be become bad/broken. (Or even has been from the beginning of its live) There is a high chance, that one will observe more and more reallocations. And this is a guarantee for data loss. Just for the record: The magnetic drives in my 24/7 NAS are starting/stopping about 5 to 10 times a day (standby), according to SMART these drives now have roughly 15k start/stops and about 7k power on hours: They don't have a single reallocated sector. If you can afford it, I would suggest you to replace it. cheers, Andreas Andreas . . . it's always good to get feedback from those with more experience than I. I don't have much confidence in hardware coming right OOTB. Of the items I've purchased over the years, quite a few have been DOA or failed shortly thereafter for whatever reason. This particular drive has no data that is not backed up elsewhere so I am comfortable experimenting with it a bit as a learning experience. OTOH, trashing the remaining life it has for no reason wouldn't make sense. I have some older spares that I can reuse and 2 new 500 GB WD Black drives waiting to be formatted. BTW . . .thanks for fixing apt in chimaera. :D golinux ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
On 2020-09-04 05:38, Simon Walter wrote: On 9/4/20 3:50 PM, goli...@devuan.org wrote: Well . . . I decided to run an fsck on the misbehaving harddrive. It started off by identifying the errors and rewriting them and then went through Free block counts, Inode bitmap differences and Free inodes and directory count. Some snippets of the output are posted below. I did not stick around to watch all of it so may have missed something. It took a long time to sort itself! Out of curiosity, was it connected via eSATA or USB? I forgot what kind of dock you got. The drive is still in the external case. Connection is USB with AC adapter. Testing it on the dock would have been the next step. I did finally get the dock out of the box but have not fired it up yet. I am old, slow and methodical . . . When it finished, I mounted the drive without issue and could read the remaining directories and files. However the /media/xx/cstwo/600 directory mentioned in the original mounting error below was nowhere to be found: "Error when getting information for file '/media/xx/cstwo/600': Input/output error." It's possible that data is not actually gone and can be recovered if you know what you are looking for. However, as you stated, you have a copy of the data elsewhere. A few posts after yours Hendrik suggested checking the lost and found directory and in it I found 57 folders and 15798 other items totaling 16.6 GB. They are mostly edits from audacity (.au) and avidemux (in C). Also some wav and mp3 and graphics stuff too. I couldn't find the associated mpgs or isos and there seems to be some other things missing here and there. Everything in the lost and found can be deleted. Maybe if I do it in small chunks, it won't explode. LOL! Then I ran the SMART Short offline test and it completed without error I have no idea how reliable the repaired drive is after this radical surgery. Can it be written to or files deleted? Should I even try? From my experience, SMART data is reliable. To give some idea, I have experience with over a hundred disks since they started to include SMART. So probably not that much compared to others on this list. I would say there is no problem with the underlying disk and the corruption occurred at the filesystem level, which is one reason an entire directory is missing, rather than at the disk level. If you want more assurance, run the long test. You can get some idea of how quickly your drive is deteriorating by monitoring changes to the SMART data (smartd). I've been able to predict failure before it happens. It's never been sudden. So if your disk "PASSED" it's probably fine to use it. Modern disk drives will move your data to good sectors when it detects failure looming in bad sectors. So head failure is an issue, and can also be predicted by SMART data. Mishandling of drives is something that SMART can't predict of course. ;) Thanks for the useful info Simon. I will run the long SMART test later today. Best regards, Simon ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
On Fri, Sep 04, 2020 at 01:50:07AM -0500, goli...@devuan.org wrote: > On 2020-09-01 00:07, goli...@devuan.org wrote: > > Thanks to everyone who has responded to this thread (some off-list). I > > just wanted to drop a short note updating you that the dock arrived > > earlier today but I haven't yet had a chance to open the box. I am not > > an impulsive person. I tend to measure 6 times and cut once! So it's > > going to take me a while to sort through all the suggestions and > > decide how to proceed. I'll post when I have figured that out and the > > stars align. Stay tuned . . . > > > > golinux > > Well . . . I decided to run an fsck on the misbehaving harddrive. It started > off by identifying the errors and rewriting them and then went through Free > block counts, Inode bitmap differences and Free inodes and directory count. > Some snippets of the output are posted below. I did not stick around to > watch all of it so may have missed something. It took a long time to sort > itself! You might want to compare the contents of the disk with a recent backup, and see if they match. When they don't, you should heck whether it' because (1) the data on disk have become bad, or (2) the data has changed legitmately sine the last backup. Of course it's possible that the data went bad before that backup and garbage has been backed up. > > == > > When it finished, I mounted the drive without issue and could read the > remaining directories and files. However the /media/xx/cstwo/600 > directory mentioned in the original mounting error below was nowhere to be > found: Have you checked the top-level lost and found directory? Stray files end up there if fsck doen't know where they belong. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
On Fri, 4 Sep 2020 18:34:29 +0200 Andreas Messer wrote: > Hi golinux, > > On Fri, Sep 04, 2020 at 01:50:07AM -0500, goli...@devuan.org wrote: > > On 2020-09-01 00:07, goli...@devuan.org wrote: > > [...] > > I have no idea how reliable the repaired drive is after this radical > > surgery. Can it be written to or files deleted? Should I even try? > > [...] > > I wouldn't use a drive anymore which has started reallocating > sectors, well which has reallocated sectors all. I very strongly agree. Using a drive that's had troubles in the past is asking for lost or altered data. > During manufacturing the drive, it can happen that some sectors are > bad, but these sectors are already "reallocated" during the > manufacturing end test and will not show up in the SMART information. > When a magnetic disc drive starts reallocating sectors, it is an > indicator that something within drive starts to be become bad/broken. > (Or even has been from the beginning of its live) There is a high > chance, that one will observe more and more reallocations. And this > is a guarantee for data loss. The preceding is what I've observed. If a sector goes bad, other sectors soon follow. SteveT Steve Litt Autumn 2020 featured book: Thriving in Tough Times http://www.troubleshooters.com/thrive ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
Hi golinux, On Fri, Sep 04, 2020 at 01:50:07AM -0500, goli...@devuan.org wrote: > On 2020-09-01 00:07, goli...@devuan.org wrote: > [...] > I have no idea how reliable the repaired drive is after this radical > surgery. Can it be written to or files deleted? Should I even try? > [...] I wouldn't use a drive anymore which has started reallocating sectors, well which has reallocated sectors all. During manufacturing the drive, it can happen that some sectors are bad, but these sectors are already "reallocated" during the manufacturing end test and will not show up in the SMART information. When a magnetic disc drive starts reallocating sectors, it is an indicator that something within drive starts to be become bad/broken. (Or even has been from the beginning of its live) There is a high chance, that one will observe more and more reallocations. And this is a guarantee for data loss. Just for the record: The magnetic drives in my 24/7 NAS are starting/stopping about 5 to 10 times a day (standby), according to SMART these drives now have roughly 15k start/stops and about 7k power on hours: They don't have a single reallocated sector. If you can afford it, I would suggest you to replace it. cheers, Andreas -- gnuPG keyid: 8C2BAF51 fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51 signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
Il 04/09/20 08:50, goli...@devuan.org ha scritto: > On 2020-09-01 00:07, goli...@devuan.org wrote: >> Thanks to everyone who has responded to this thread (some off-list). I >> just wanted to drop a short note updating you that the dock arrived >> earlier today but I haven't yet had a chance to open the box. I am not >> an impulsive person. I tend to measure 6 times and cut once! So it's >> going to take me a while to sort through all the suggestions and >> decide how to proceed. I'll post when I have figured that out and the >> stars align. Stay tuned . . . >> >> golinux > > Well . . . I decided to run an fsck on the misbehaving harddrive. It started > off by identifying the errors and rewriting them and then went through Free > block counts, Inode bitmap differences and Free inodes and directory count. > Some snippets of the output are posted below. I did not stick around to watch > all of it so may have missed something. It took a long time to sort itself! > > == > > root@devuan:/home/xx# fsck /dev/sdc1 -y > fsck from util-linux 2.25.2 > e2fsck 1.42.12 (29-Aug-2014) > cstwo contains a file system with errors, check forced. > Pass 1: Checking inodes, blocks, and size > Error reading block 40042498 (Attempt to read block from filesystem resulted > in short read) while getting next inode from scan. Ignore error? yes > Force rewrite? yes > Error reading block 41943042 (Attempt to read block from filesystem resulted > in short read) while getting next inode from scan. Ignore error? yes > Force rewrite? yes > yada, yada > > == > > Free blocks count wrong for group #6302 (22328, counted=25579). > Fix? yes > > Free blocks count wrong for group #6678 (21, counted=22). > Fix? yes > > Free blocks count wrong (72019929, counted=75713399). > Fix? yes > yada, yada > > == > > Inode bitmap differences: -(20021249--20021280) -(20971521--20971552) > -(21250049--21250065) -(23756801--23756811) -(25772033--25772051) > -(25772053--25772057) -(25772059--25772064) -(25772067--25772069) > -(25772073--25772074) > yada, yada > > == > > [ending with] > > Free inodes count wrong for group #6278 (13844, counted=14355). > Fix? yes > > Directories count wrong for group #6278 (19, counted=0). > Fix? yes > > cstwo: * FILE SYSTEM WAS MODIFIED * > cstwo: 191841/122109952 files (1.9% non-contiguous), 168476601/24419 > blocks > > == > > When it finished, I mounted the drive without issue and could read the > remaining directories and files. However the /media/xx/cstwo/600 > directory mentioned in the original mounting error below was nowhere to be > found: > > "Error when getting information for file '/media/xx/cstwo/600': > Input/output error." > > Then I ran the SMART Short offline test and it completed without error Hi, better run the long offline test, takes about 2 hrs but check whole disk surface and will detect other bad sectors if there are any. Ciao, Tito > I have no idea how reliable the repaired drive is after this radical surgery. > Can it be written to or files deleted? Should I even try? > > Thanks to all and especially g4sra for detailed suggestions and advice. > > Now onto the next project needed to moving on from jessie at long last. > > Take care all, > > golinux > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
On 9/4/20 3:50 PM, goli...@devuan.org wrote: Well . . . I decided to run an fsck on the misbehaving harddrive. It started off by identifying the errors and rewriting them and then went through Free block counts, Inode bitmap differences and Free inodes and directory count. Some snippets of the output are posted below. I did not stick around to watch all of it so may have missed something. It took a long time to sort itself! Out of curiosity, was it connected via eSATA or USB? I forgot what kind of dock you got. ... When it finished, I mounted the drive without issue and could read the remaining directories and files. However the /media/xx/cstwo/600 directory mentioned in the original mounting error below was nowhere to be found: "Error when getting information for file '/media/xx/cstwo/600': Input/output error." It's possible that data is not actually gone and can be recovered if you know what you are looking for. However, as you stated, you have a copy of the data elsewhere. Then I ran the SMART Short offline test and it completed without error I have no idea how reliable the repaired drive is after this radical surgery. Can it be written to or files deleted? Should I even try? From my experience, SMART data is reliable. To give some idea, I have experience with over a hundred disks since they started to include SMART. So probably not that much compared to others on this list. I would say there is no problem with the underlying disk and the corruption occurred at the filesystem level, which is one reason an entire directory is missing, rather than at the disk level. If you want more assurance, run the long test. You can get some idea of how quickly your drive is deteriorating by monitoring changes to the SMART data (smartd). I've been able to predict failure before it happens. It's never been sudden. So if your disk "PASSED" it's probably fine to use it. Modern disk drives will move your data to good sectors when it detects failure looming in bad sectors. So head failure is an issue, and can also be predicted by SMART data. Mishandling of drives is something that SMART can't predict of course. ;) Best regards, Simon ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can this drive be saved?
On 2020-09-01 00:07, goli...@devuan.org wrote: Thanks to everyone who has responded to this thread (some off-list). I just wanted to drop a short note updating you that the dock arrived earlier today but I haven't yet had a chance to open the box. I am not an impulsive person. I tend to measure 6 times and cut once! So it's going to take me a while to sort through all the suggestions and decide how to proceed. I'll post when I have figured that out and the stars align. Stay tuned . . . golinux Well . . . I decided to run an fsck on the misbehaving harddrive. It started off by identifying the errors and rewriting them and then went through Free block counts, Inode bitmap differences and Free inodes and directory count. Some snippets of the output are posted below. I did not stick around to watch all of it so may have missed something. It took a long time to sort itself! == root@devuan:/home/xx# fsck /dev/sdc1 -y fsck from util-linux 2.25.2 e2fsck 1.42.12 (29-Aug-2014) cstwo contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and size Error reading block 40042498 (Attempt to read block from filesystem resulted in short read) while getting next inode from scan. Ignore error? yes Force rewrite? yes Error reading block 41943042 (Attempt to read block from filesystem resulted in short read) while getting next inode from scan. Ignore error? yes Force rewrite? yes yada, yada == Free blocks count wrong for group #6302 (22328, counted=25579). Fix? yes Free blocks count wrong for group #6678 (21, counted=22). Fix? yes Free blocks count wrong (72019929, counted=75713399). Fix? yes yada, yada == Inode bitmap differences: -(20021249--20021280) -(20971521--20971552) -(21250049--21250065) -(23756801--23756811) -(25772033--25772051) -(25772053--25772057) -(25772059--25772064) -(25772067--25772069) -(25772073--25772074) yada, yada == [ending with] Free inodes count wrong for group #6278 (13844, counted=14355). Fix? yes Directories count wrong for group #6278 (19, counted=0). Fix? yes cstwo: * FILE SYSTEM WAS MODIFIED * cstwo: 191841/122109952 files (1.9% non-contiguous), 168476601/24419 blocks == When it finished, I mounted the drive without issue and could read the remaining directories and files. However the /media/xx/cstwo/600 directory mentioned in the original mounting error below was nowhere to be found: "Error when getting information for file '/media/xx/cstwo/600': Input/output error." Then I ran the SMART Short offline test and it completed without error I have no idea how reliable the repaired drive is after this radical surgery. Can it be written to or files deleted? Should I even try? Thanks to all and especially g4sra for detailed suggestions and advice. Now onto the next project needed to moving on from jessie at long last. Take care all, golinux ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
