[opensuse] Deleting corrupted files
An external disk had a bit of a prob when copying data to it, and I now have a bunch of corrupted files on it: -????????? ? ? ? ? ? pb072311.jpg -????????? ? ? ? ? ? pb072312.jpg -????????? ? ? ? ? ? pb072313.jpg -????????? ? ? ? ? ? pb072314.jpg john@boss:/media/disk/data/draw/camera/misc> ls -la pb0723* ls: cannot access pb072302.jpg: Input/output error ls: cannot access pb072303.jpg: Input/output error ls: cannot access pb072304.jpg: Input/output error ls: cannot access pb072305.jpg: Input/output error Is there any way to delete these? Thanks, John. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2009-11-26 at 22:04 +1000, John Bennett wrote:
An external disk had a bit of a prob when copying data to it, and I now have a bunch of corrupted files on it: -????????? ? ? ? ? ? pb072311.jpg -????????? ? ? ? ? ? pb072312.jpg -????????? ? ? ? ? ? pb072313.jpg -????????? ? ? ? ? ? pb072314.jpg
john@boss:/media/disk/data/draw/camera/misc> ls -la pb0723* ls: cannot access pb072302.jpg: Input/output error ls: cannot access pb072303.jpg: Input/output error ls: cannot access pb072304.jpg: Input/output error ls: cannot access pb072305.jpg: Input/output error
Is there any way to delete these?
I suspect your situation is more complicated than that. The directory itself is probably corrupt. I would make a backup of all that I could off the partition before doing anything else. After that is secure, try running fsck on the partition. If you are lucky, it can repair things. As a minimum, more files might become accessible. Or, it may go south. Which is why you should make the backup BEFORE playing with fsck. After all this, I personally would re-format the partition. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 26 November 2009 13:04:52, John Bennett wrote:
An external disk had a bit of a prob when copying data to it, and I now have a bunch of corrupted files on it: -????????? ? ? ? ? ? pb072311.jpg -????????? ? ? ? ? ? pb072312.jpg -????????? ? ? ? ? ? pb072313.jpg -????????? ? ? ? ? ? pb072314.jpg
john@boss:/media/disk/data/draw/camera/misc> ls -la pb0723* ls: cannot access pb072302.jpg: Input/output error ls: cannot access pb072303.jpg: Input/output error ls: cannot access pb072304.jpg: Input/output error ls: cannot access pb072305.jpg: Input/output error
Is there any way to delete these? Thanks, John.
I had a similar problem with some files that I copied from a very old Win98- backup. In dolphin I could not rename nor delete them. However in a root console I could still use the rm command with wildcards, i.e. cd to-the-directory-containing the files rm pb07231*.jpg *Be careful with the rm command* and doubleckeck that the wildcard you are using will not include files you want to keep! hth Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
cd to-the-directory-containing the files rm pb07231*.jpg
*Be careful with the rm command* and doubleckeck that the wildcard you are using will not include files you want to keep!
Thank you. I could finally delete some "strange" files here :-) Karl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 26 Nov 2009, Cristian Rodríguez wrote:
On 26/11/09 09:04, John Bennett wrote:
Is there any way to delete these? Thanks, John.
I suggest you to format the partition.
That's a bit radical. If 'rm' refuses to delete a file you can still go for 'debugfs' (if you are on an ext2/3/4 filesystem). And run a filesystem check afterwards. Steffen -- Das Nichtrauchen entfernt uns von der Zivilisation und setzt den Mann mit seinem Dackel gleich. -- J. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 11/26/2009 09:14 AM, Steffen Winterfeldt pecked at the keyboard and wrote:
On Thu, 26 Nov 2009, Cristian Rodríguez wrote:
On 26/11/09 09:04, John Bennett wrote:
Is there any way to delete these? Thanks, John.
I suggest you to format the partition.
That's a bit radical.
If 'rm' refuses to delete a file you can still go for 'debugfs' (if you are on an ext2/3/4 filesystem). And run a filesystem check afterwards.
Steffen
Let's not forget that with files/folders that have corrupted ownership you will need to remove them as the root user. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 26 Nov 2009 22:34:52 John Bennett wrote:
An external disk had a bit of a prob when copying data to it, and I now have a bunch of corrupted files on it: -????????? ? ? ? ? ? pb072311.jpg -????????? ? ? ? ? ? pb072312.jpg -????????? ? ? ? ? ? pb072313.jpg -????????? ? ? ? ? ? pb072314.jpg
john@boss:/media/disk/data/draw/camera/misc> ls -la pb0723* ls: cannot access pb072302.jpg: Input/output error ls: cannot access pb072303.jpg: Input/output error ls: cannot access pb072304.jpg: Input/output error ls: cannot access pb072305.jpg: Input/output error
Is there any way to delete these? Thanks, John.
I also recently had a number of zero length files left over from a process gone wrong, with some illegal/unprintable characters in the filenames. To remove them was fairly simple: find . -size 0 -print0 | xargs -0 rm -f In your case you could use something like: find . -maxdepth 1 -name pb\*.jpg -print0 | xargs -0 rm -f The -print0 | xargs -0 takes care of non-printable characters/special characters/spaces in the file names and ensures that they're passed through intact to the rm -f command. The -maxdepth 1 stops recursion into subdirectories and the wildcard needs to be escaped (hence the backslash) otherwise find will complain that "paths must precede expressions". HTH. Rodney. -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 27/11/09 00:01, Rodney Baker wrote:
On Thu, 26 Nov 2009 22:34:52 John Bennett wrote:
An external disk had a bit of a prob when copying data to it, and I now have a bunch of corrupted files on it: -????????? ? ? ? ? ? pb072311.jpg -????????? ? ? ? ? ? pb072312.jpg
In your case you could use something like:
find . -maxdepth 1 -name pb\*.jpg -print0 | xargs -0 rm -f
The -print0 | xargs -0 takes care of non-printable characters/special characters/spaces in the file names and ensures that they're passed through intact to the rm -f command. The -maxdepth 1 stops recursion into subdirectories and the wildcard needs to be escaped (hence the backslash) otherwise find will complain that "paths must precede expressions".
HTH.
Rodney.
Nope, still no joy...: john@boss:/media/disk/data/draw/camera/misc> sudo find . -maxdepth 1 -name pb\*.jpg -print0 |xargs -0 rm -f root's password: rm: cannot remove `./pb012292.jpg': Permission denied rm: cannot remove `./pb012293.jpg': Permission denied rm: cannot remove `./pb012294.jpg': Permission denied rm: cannot remove `./pb012295.jpg': Permission denied rm: cannot remove `./pb012296.jpg': Permission denied Ah well, might have to do the "task of no return" - ie format.... :-( I actually suspect that it is the external enclosure that is creating the prob... it is a Ritmo, and I don't hold a lot of faith in them... Thanks, John -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 27 Nov 2009 20:14:47 John Bennett wrote:
On 27/11/09 00:01, Rodney Baker wrote:
On Thu, 26 Nov 2009 22:34:52 John Bennett wrote:
An external disk had a bit of a prob when copying data to it, and I now have a bunch of corrupted files on it: -????????? ? ? ? ? ? pb072311.jpg -????????? ? ? ? ? ? pb072312.jpg
In your case you could use something like:
find . -maxdepth 1 -name pb\*.jpg -print0 | xargs -0 rm -f
The -print0 | xargs -0 takes care of non-printable characters/special characters/spaces in the file names and ensures that they're passed through intact to the rm -f command. The -maxdepth 1 stops recursion into subdirectories and the wildcard needs to be escaped (hence the backslash) otherwise find will complain that "paths must precede expressions".
HTH.
Rodney.
Nope, still no joy...: john@boss:/media/disk/data/draw/camera/misc> sudo find . -maxdepth 1 -name pb\*.jpg -print0 |xargs -0 rm -f
root's password:
rm: cannot remove `./pb012292.jpg': Permission denied rm: cannot remove `./pb012293.jpg': Permission denied rm: cannot remove `./pb012294.jpg': Permission denied rm: cannot remove `./pb012295.jpg': Permission denied rm: cannot remove `./pb012296.jpg': Permission denied
Ah well, might have to do the "task of no return" - ie format.... :-( I actually suspect that it is the external enclosure that is creating the prob... it is a Ritmo, and I don't hold a lot of faith in them...
Thanks, John
What is the result of mount? Is the external drive mounted read-only or with read/write priveleges? Is there a write-protect switch that has been accidentally turned on? -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 27/11/09 21:21, Rodney Baker wrote:
On Fri, 27 Nov 2009 20:14:47 John Bennett wrote:
On 27/11/09 00:01, Rodney Baker wrote:
On Thu, 26 Nov 2009 22:34:52 John Bennett wrote:
An external disk had a bit of a prob when copying data to it, and I now
rm: cannot remove `./pb012292.jpg': Permission denied rm: cannot remove `./pb012293.jpg': Permission denied Ah well, might have to do the "task of no return" - ie format.... :-( I actually suspect that it is the external enclosure that is creating the prob... it is a Ritmo, and I don't hold a lot of faith in them...
Thanks, John
What is the result of mount? Is the external drive mounted read-only or with read/write priveleges? Is there a write-protect switch that has been accidentally turned on?
Problem solved (for now). Think it is suspect hardware... Ran fsck (again..) and this time it appears to have cleaned it up - fixed all the probs and file system now clean. Thannks for all the assistance/suggestions. May have to look at a new enclosure... Thanks, John. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 27 November 2009 05:49:15 and regarding:
On 27/11/09 21:21, Rodney Baker wrote:
On Fri, 27 Nov 2009 20:14:47 John Bennett wrote:
On 27/11/09 00:01, Rodney Baker wrote:
On Thu, 26 Nov 2009 22:34:52 John Bennett wrote:
An external disk had a bit of a prob when copying data to it, and I now
rm: cannot remove `./pb012292.jpg': Permission denied rm: cannot remove `./pb012293.jpg': Permission denied Ah well, might have to do the "task of no return" - ie format.... :-( I actually suspect that it is the external enclosure that is creating the prob... it is a Ritmo, and I don't hold a lot of faith in them...
Thanks, John
What is the result of mount? Is the external drive mounted read-only or with read/write priveleges? Is there a write-protect switch that has been accidentally turned on?
Problem solved (for now). Think it is suspect hardware... Ran fsck (again..) and this time it appears to have cleaned it up - fixed all the probs and file system now clean. Thannks for all the assistance/suggestions. May have to look at a new enclosure... Thanks, John.
-- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 27 November 2009 05:49:15 and regarding:
On 27/11/09 21:21, Rodney Baker wrote:
On Fri, 27 Nov 2009 20:14:47 John Bennett wrote:
On 27/11/09 00:01, Rodney Baker wrote:
On Thu, 26 Nov 2009 22:34:52 John Bennett wrote:
An external disk had a bit of a prob when copying data to it, and I now
rm: cannot remove `./pb012292.jpg': Permission denied rm: cannot remove `./pb012293.jpg': Permission denied Ah well, might have to do the "task of no return" - ie format.... :-( I actually suspect that it is the external enclosure that is creating the prob... it is a Ritmo, and I don't hold a lot of faith in them...
Thanks, John
What is the result of mount? Is the external drive mounted read-only or with read/write priveleges? Is there a write-protect switch that has been accidentally turned on?
Problem solved (for now). Think it is suspect hardware... Ran fsck (again..) and this time it appears to have cleaned it up - fixed all the probs and file system now clean. Thannks for all the assistance/suggestions. May have to look at a new enclosure... Thanks, John.
John, Keep an eye on it. I have had the same issue on a 10.3 server after connecting to it with 11.2. I'm not sure it is hardware. I think 11.2 may have a significant language or utf-8 issue that may be causing the corruption. My server appeared to be suffering a disk failure of /home in a raid array and the following was filling the logs. However, I'm suspicious that an 11.2 issue might be to blame. I am seeing some really weird stuff when connecting remotely with 11.2. All kinds of weird characters in 'mc' and sometimes the 'mc' display spirals like a barber-pole looking like there are two tabs added after every newline character. If this is happening because of some type of encoding problem, I could see the problem being hardware and not software. However I don't know enough about what the following errors mean to know yet. Can anybody help up out?? It looks like sda is failing, but fsck cleans it up without much effort. It seems fine until I ssh or sftp in from 11.2, then when I check the logs I'm seeing errors. Another curious issue is connecting to the server from 11.2 causes some type of 30 second delay before the connection is established. Connecting with 11.0 or Archlinux works just fine. I have no idea what this issue could be other than hardware, but I've been watching things pretty close and there seems to be some issue with remote connections from 11.2. I know the server hasn't changed software-wise. It's 10.3 and nothing is changing on that box. Please, someone much smarter than I on disk error, let me know what this looks like to you. Thanks... Dec 3 18:03:53 nirvana dhcpd: Wrote 0 new dynamic host decls to leases file. Dec 3 18:03:53 nirvana dhcpd: Wrote 38 leases to leases file. Dec 3 18:03:53 nirvana dhcpd: DHCPREQUEST for 192.168.6.120 from 00:25:00:df:fe:2c (iPod-touch-2) via eth0 Dec 3 18:03:53 nirvana dhcpd: DHCPACK on 192.168.6.120 to 00:25:00:df:fe:2c (iPod-touch-2) via eth0 Dec 3 18:05:01 nirvana /usr/sbin/cron[21144]: (root) CMD (/root/.local/rcron) Dec 3 18:05:42 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 3 18:05:42 nirvana kernel: ata3.00: BMDMA stat 0x25 Dec 3 18:05:42 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in Dec 3 18:05:42 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error) Dec 3 18:05:42 nirvana kernel: ata3.00: configured for UDMA/133 Dec 3 18:05:42 nirvana kernel: ata3: EH complete Dec 3 18:05:44 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 3 18:05:44 nirvana kernel: ata3.00: BMDMA stat 0x25 Dec 3 18:05:44 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in Dec 3 18:05:44 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error) Dec 3 18:05:44 nirvana kernel: ata3.00: configured for UDMA/133 Dec 3 18:05:44 nirvana kernel: ata3: EH complete Dec 3 18:05:46 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 3 18:05:46 nirvana kernel: ata3.00: BMDMA stat 0x25 Dec 3 18:05:46 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in Dec 3 18:05:46 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error) Dec 3 18:06:30 nirvana kernel: ata3.00: configured for UDMA/133 Dec 3 18:06:30 nirvana kernel: ata3: EH complete Dec 3 18:06:30 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 3 18:06:30 nirvana kernel: ata3.00: BMDMA stat 0x25 Dec 3 18:06:30 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in Dec 3 18:06:30 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error) Dec 3 18:06:30 nirvana kernel: ata3.00: configured for UDMA/133 Dec 3 18:06:30 nirvana kernel: ata3: EH complete Dec 3 18:06:30 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 3 18:06:30 nirvana kernel: ata3.00: BMDMA stat 0x25 Dec 3 18:06:30 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in Dec 3 18:06:30 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error) Dec 3 18:06:30 nirvana kernel: ata3.00: configured for UDMA/133 Dec 3 18:06:30 nirvana kernel: ata3: EH complete Dec 3 18:06:30 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 3 18:06:30 nirvana kernel: ata3.00: BMDMA stat 0x25 Dec 3 18:06:30 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in Dec 3 18:06:30 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error) Dec 3 18:06:30 nirvana kernel: ata3.00: configured for UDMA/133 Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor] Dec 3 18:06:30 nirvana kernel: Descriptor sense data with sense descriptors (in hex): Dec 3 18:06:30 nirvana kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Dec 3 18:06:30 nirvana kernel: 34 8c 0c 39 Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed Dec 3 18:06:30 nirvana kernel: end_request: I/O error, dev sda, sector 881593401 Dec 3 18:06:30 nirvana kernel: ata3: EH complete Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Write Protect is off Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2009-12-04 at 04:22 -0600, David C. Rankin wrote: ...
Please, someone much smarter than I on disk error, let me know what this looks like to you. Thanks...
Dec 3 18:05:42 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 3 18:05:42 nirvana kernel: ata3.00: BMDMA stat 0x25 Dec 3 18:05:42 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in Dec 3 18:05:42 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error) Dec 3 18:05:42 nirvana kernel: ata3.00: configured for UDMA/133 Dec 3 18:05:42 nirvana kernel: ata3: EH complete Dec 3 18:05:44 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 3 18:05:44 nirvana kernel: ata3.00: BMDMA stat 0x25 Dec 3 18:05:44 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in Dec 3 18:05:44 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error) Dec 3 18:05:44 nirvana kernel: ata3.00: configured for UDMA/133 Dec 3 18:05:44 nirvana kernel: ata3: EH complete Dec 3 18:05:46 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 3 18:05:46 nirvana kernel: ata3.00: BMDMA stat 0x25 Dec 3 18:05:46 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in Dec 3 18:05:46 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error)
Watch out: "media error", and more than one time.
Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
This is prety bad. Hard disks have some space allocated by the manufacturer to remap the bad sectors that develop during its lifetime. This is normal, don't worry. The problem is when that space fills up completely, and that has happened to your's, I think. It means end of life for the HD. smartctl --health /dev/sda smartctl -a /dev/sda Backup your data, then run the smartctl short and long tests. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAksbm4kACgkQtTMYHG2NR9WTPQCglui2Byg7iWpQ/ASoJJUTEerU TEoAoJRrk1Yxg+q+leMcNFLPVaWiDQ// =cJ92 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. wrote:
Watch out: "media error", and more than one time.
Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
This is prety bad.
Hard disks have some space allocated by the manufacturer to remap the bad sectors that develop during its lifetime. This is normal, don't worry. The problem is when that space fills up completely, and that has happened to your's, I think. It means end of life for the HD.
smartctl --health /dev/sda smartctl -a /dev/sda
Backup your data, then run the smartctl short and long tests.
-- Cheers, Carlos E. R.
Any action should really only be undertaken if the fault can be verified using an alternative cabling setup. Cabling or communication issues could create similar reports, all cables can fail over time. Further actions should be taken according to result, it should be noted evidence of consistent failures on one cabling and communication type indicates something more complex is going on. Bad sectors do and will occur over time, this is to be expected. It is a serious issue if and only if the number of sectors affected are continuing to rise relatively rapidly, or the sector numbers affected is inconsistent; an alert condition if not. A file level backup (e.g rsync) is essential in all cases. Then a rebuild format of partitions taking in account known bad sectors may still give a usable drive in the latter case, a new drive is the only solution the first. - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAksc5EgACgkQasN0sSnLmgJWywCg0ikv2ONg6gpspsjyi94A5/T9 4a4AoPGRIh18lTDJnmeqG8m0O/HakUa/ =BbRP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2009-12-07 at 11:17 +0000, G T Smith wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Carlos E. R. wrote:
Watch out: "media error", and more than one time.
Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
This is prety bad.
Hard disks have some space allocated by the manufacturer to remap the bad sectors that develop during its lifetime. This is normal, don't worry. The problem is when that space fills up completely, and that has happened to your's, I think. It means end of life for the HD.
smartctl --health /dev/sda smartctl -a /dev/sda
OOC, I ran smartctl --health on a few systems. On one, I get: === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED Please note the following marginal Attributes: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 9 Power_On_Seconds 0x0012 001 001 020 Old_age Always FAILING_NOW 61430h+32m+38s That looks ominous. I do not have any problems with the system. The disk is mainly letting the OS boot and run. All activity is on another disk. Is it just reporting that the disk as been powered on for over 5 years and is getting old? -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2009-12-07 at 12:37 +0100, Roger Oberholtzer wrote:
OOC, I ran smartctl --health on a few systems. On one, I get:
=== START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED Please note the following marginal Attributes: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 9 Power_On_Seconds 0x0012 001 001 020 Old_age Always FAILING_NOW 61430h+32m+38s
That looks ominous. I do not have any problems with the system. The disk is mainly letting the OS boot and run. All activity is on another disk. Is it just reporting that the disk as been powered on for over 5 years and is getting old?
I think so, yes. I report "failed" when the value is lower than the treshold, if I understand it correctly. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAksdKFcACgkQtTMYHG2NR9VO4QCePIEVZkl4UcnbMJl9Z2d1Cdmk tJQAniF8VJdUQIMro+z8tQXXXgEzNQoG =clYu -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2009-12-07 at 11:17 -0000, G T Smith wrote: ...
Bad sectors do and will occur over time, this is to be expected. It is a serious issue if and only if the number of sectors affected are continuing to rise relatively rapidly, or the sector numbers affected is inconsistent; an alert condition if not.
That's true, but I seriously suspect that the reallocation space has been spent completely. Notice that this realocation is internal to the disk, cables do not intervene. That's why I asked to run the test, to learn if the reallocation space is spent or not. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAksdKXYACgkQtTMYHG2NR9UzggCfdy5z8fh/8AfGObxb6SdcSM+4 VcIAoJINW7PGTTbF+gA+7LQ7+kslReHR =AbPt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
An external disk had a bit of a prob when copying data to it, and I now have a bunch of corrupted files on it: -????????? ? ? ? ? ? pb072311.jpg -????????? ? ? ? ? ? pb072312.jpg -????????? ? ? ? ? ? pb072313.jpg -????????? ? ? ? ? ? pb072314.jpg
john@boss:/media/disk/data/draw/camera/misc> ls -la pb0723* ls: cannot access pb072302.jpg: Input/output error ls: cannot access pb072303.jpg: Input/output error ls: cannot access pb072304.jpg: Input/output error ls: cannot access pb072305.jpg: Input/output error
(Probably) the filesystem is corrupted. I would copy/clone the the whole partition (using eg. dd) just to make data safe (don't forget to unmount the partition first). Then you can experiment with one of the copies to recover the files and fix filesystem; try to run fsck, or this might help as well: http://www.cgsecurity.org/ (photorec, testdisk) Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (12)
-
Carlos E. R. -
Cristian Rodríguez -
Daniel Bauer -
David C. Rankin -
G T Smith -
Istvan Gabor -
John Bennett -
Karl Sinn -
Ken Schneider - openSUSE -
Rodney Baker -
Roger Oberholtzer -
Steffen Winterfeldt