LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 08-13-2012, 02:08 PM   #1
sevs
Member
 
Registered: Jul 2008
Location: Ukraine, Kharkov
Distribution: debian, knoppix, mandriva, asplinux, altlinux
Posts: 108

Rep: Reputation: 19
Another problem with HDD.


Hi there!
Tonight I was abused with something strange.
First I was watching some movie. Then there was a beep. And the next moment I can't create any file in /home directory (with a user) with a message saying that the filesystem is mounted read-only.
Ok, I thought. Let's kill gdm and make fsck. When gdm was killed on its terminal (7th) was following:
Quote:
journaling commit i/o error
.
Next step was fsck with -MCa parameters. After some time passed (enough to check about 50% ofmy /home directory partiotion (/dev/sda5)) it said I'd better start fsck w/o -a paramter. On next boot I just made it. I did fsck -MC (w/o '-a').
It ran through many hard disk errors (as I understood).
Here is kern.log for that time:
Quote:
Aug 13 20:54:06 ksergy kernel: [ 1053.566201] Buffer I/O error on device sda5, logical block 42207871
Aug 13 20:54:06 ksergy kernel: [ 1053.568361] Buffer I/O error on device sda5, logical block 42207872
Aug 13 20:54:06 ksergy kernel: [ 1053.570433] Buffer I/O error on device sda5, logical block 42207873
Aug 13 20:54:06 ksergy kernel: [ 1053.572519] Buffer I/O error on device sda5, logical block 42207874
Aug 13 20:54:06 ksergy kernel: [ 1053.574570] Buffer I/O error on device sda5, logical block 42207875
Aug 13 20:54:06 ksergy kernel: [ 1053.576599] Buffer I/O error on device sda5, logical block 42207876
Aug 13 20:54:06 ksergy kernel: [ 1053.578590] Buffer I/O error on device sda5, logical block 42207877
Aug 13 20:54:06 ksergy kernel: [ 1053.580552] Buffer I/O error on device sda5, logical block 42207878
Aug 13 20:54:06 ksergy kernel: [ 1053.582495] Buffer I/O error on device sda5, logical block 42207879
Aug 13 20:54:06 ksergy kernel: [ 1053.584399] Buffer I/O error on device sda5, logical block 42207880
Aug 13 20:54:06 ksergy kernel: [ 1053.586290] ata1: EH complete
Aug 13 20:54:09 ksergy kernel: [ 1056.589286] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Aug 13 20:54:09 ksergy kernel: [ 1056.591159] ata1.00: irq_stat 0x40000001
Aug 13 20:54:09 ksergy kernel: [ 1056.593020] ata1.00: failed command: READ DMA
Aug 13 20:54:09 ksergy kernel: [ 1056.594854] ata1.00: cmd c8/00:01:82:8a:bd/00:00:00:00:00/ea tag 0 dma 512 in
Aug 13 20:54:09 ksergy kernel: [ 1056.594855] res 51/01:00:82:8a:bd/00:00:0a:00:00/ea Emask 0x1 (device error)
Aug 13 20:54:09 ksergy kernel: [ 1056.598579] ata1.00: status: { DRDY ERR }
Aug 13 20:54:09 ksergy kernel: [ 1056.603136] ata1.00: configured for UDMA/33
Aug 13 20:54:09 ksergy kernel: [ 1056.605001] ata1: EH complete
Aug 13 20:54:12 ksergy kernel: [ 1059.977703] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Aug 13 20:54:12 ksergy kernel: [ 1059.979549] ata1.00: irq_stat 0x40000001
Aug 13 20:54:12 ksergy kernel: [ 1059.981388] ata1.00: failed command: READ DMA
Aug 13 20:54:12 ksergy kernel: [ 1059.983181] ata1.00: cmd c8/00:01:82:8a:bd/00:00:00:00:00/ea tag 0 dma 512 in
Aug 13 20:54:12 ksergy kernel: [ 1059.983182] res 51/01:00:82:8a:bd/00:00:0a:00:00/ea Emask 0x1 (device error)
Aug 13 20:54:12 ksergy kernel: [ 1059.986851] ata1.00: status: { DRDY ERR }
Aug 13 20:54:12 ksergy kernel: [ 1059.991396] ata1.00: configured for UDMA/33
Aug 13 20:54:12 ksergy kernel: [ 1059.993237] ata1: EH complete
Aug 13 20:54:16 ksergy kernel: [ 1063.234743] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Aug 13 20:54:16 ksergy kernel: [ 1063.236617] ata1.00: irq_stat 0x40000001
Aug 13 20:54:16 ksergy kernel: [ 1063.238474] ata1.00: failed command: READ DMA
Aug 13 20:54:16 ksergy kernel: [ 1063.240325] ata1.00: cmd c8/00:01:82:8a:bd/00:00:00:00:00/ea tag 0 dma 512 in
Aug 13 20:54:16 ksergy kernel: [ 1063.240326] res 51/01:00:82:8a:bd/00:00:0a:00:00/ea Emask 0x1 (device error)
Aug 13 20:54:16 ksergy kernel: [ 1063.243958] ata1.00: status: { DRDY ERR }
Aug 13 20:54:16 ksergy kernel: [ 1063.248486] ata1.00: configured for UDMA/33
Aug 13 20:54:16 ksergy kernel: [ 1063.250333] ata1: EH complete
Aug 13 20:54:19 ksergy kernel: [ 1066.350394] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Aug 13 20:54:19 ksergy kernel: [ 1066.352253] ata1.00: irq_stat 0x40000001
Aug 13 20:54:19 ksergy kernel: [ 1066.354073] ata1.00: failed command: READ DMA
Aug 13 20:54:19 ksergy kernel: [ 1066.355905] ata1.00: cmd c8/00:01:82:8a:bd/00:00:00:00:00/ea tag 0 dma 512 in
Aug 13 20:54:19 ksergy kernel: [ 1066.355906] res 51/01:00:82:8a:bd/00:00:0a:00:00/ea Emask 0x1 (device error)
And so on...
After seeing this I cleaned hard disk pins.

Kernel - 2.6.32
Distro - Debian Squeeze.

Thanks in advance.
Sorry for bad English.
 
Old 08-14-2012, 12:53 AM   #2
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,592
Blog Entries: 2

Rep: Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046
This looks like a hardware error. I would recommend to test the disk with the manufacturer's diagnosis tool.
 
1 members found this post helpful.
Old 08-14-2012, 08:40 AM   #3
sevs
Member
 
Registered: Jul 2008
Location: Ukraine, Kharkov
Distribution: debian, knoppix, mandriva, asplinux, altlinux
Posts: 108

Original Poster
Rep: Reputation: 19
Ok. I'm going to test consistency of my HDD tonight.
But what could be the reason for such improper working of HDD?
Are there any recomends for HDD orientation (position, mounting, etc...) for it to work properly?
(I'm not good at formfactors and all this stuff, but I think my HDD is 2.5" (it laptop hdd) and it is SATA HDD).
 
Old 08-14-2012, 08:44 AM   #4
pan64
Senior Member
 
Registered: Mar 2012
Location: Hungary
Distribution: debian i686 (solaris)
Posts: 4,774

Rep: Reputation: 1273Reputation: 1273Reputation: 1273Reputation: 1273Reputation: 1273Reputation: 1273Reputation: 1273Reputation: 1273Reputation: 1273
Probably you should check the exact type and look around the web about that hard disk.
 
1 members found this post helpful.
Old 08-14-2012, 08:46 AM   #5
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,592
Blog Entries: 2

Rep: Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046
Sometimes HDDs just die. One of the reasons for always having a good backup plan.
I think that the manufacturer of your laptop will have taken care of the right orientation for the disk.
 
1 members found this post helpful.
Old 08-14-2012, 02:30 PM   #6
sevs
Member
 
Registered: Jul 2008
Location: Ukraine, Kharkov
Distribution: debian, knoppix, mandriva, asplinux, altlinux
Posts: 108

Original Poster
Rep: Reputation: 19
I still did not ran check on HDD (toomuch work I got tonight).

Quote:
I think that the manufacturer of your laptop will have taken care of the right orientation for the disk.
I mean - is it ok for hard disk to work not in horizontal position but in vertical? As I see it's no importance for electronics and the read-write heads are so lightweight that it's no difference for motors to push it down or pul it up while in vertical position (referred to move head left-right in horizontal position).

And again, sorry for bad English.
 
Old 08-14-2012, 02:39 PM   #7
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,592
Blog Entries: 2

Rep: Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046
No need to apologize for your English.

If I remember correctly (I think I read something about that some years ago) it is pretty save to run disk vertically on the long side, but it should be avoided to run them upside down or vertically on the front side. I don't know if that is still true for modern disks.
 
1 members found this post helpful.
Old 08-14-2012, 05:26 PM   #8
sevs
Member
 
Registered: Jul 2008
Location: Ukraine, Kharkov
Distribution: debian, knoppix, mandriva, asplinux, altlinux
Posts: 108

Original Poster
Rep: Reputation: 19
Quote:
but it should be avoided to run them upside down or vertically on the front side
That's too bad.
So, I'm waiting for weekend to check my hdd with gsmartcontrol.

Anyway, if I've passed fsck is it ok to use the HDD? As I understand there are some sort of bad blocks on it. I think any file system should have bad blocks registry for OS to know where it can write and where it should not.

Last edited by sevs; 08-14-2012 at 05:37 PM. Reason: grammar mistake
 
Old 08-14-2012, 06:10 PM   #9
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,592
Blog Entries: 2

Rep: Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046
Quote:
Originally Posted by sevs View Post
So, I'm waiting for weekend to check my hdd with gsmartcontrol.
I personally prefer the manufacturer's tools and use smartmontools only as a first indicator.

Quote:
Anyway, if I've passed fsck is it ok to use the HDD? As I understand there are some sort of bad blocks on it.
The problem lies deeper. Any disk has a few bad blocks, but the disk controller is able to recognize them and replace them with blocks from a part of the disk that's only purpose is to deliver spare blocks. If the harddrive starts to report bad blocks these spare blocks are already used up. The second problem is that, in most cases, once the disk has problems with bad blocks more and more of them appear.

So my advice would be:
1. Backup your data (which you should do anyways periodically).
2. Don't trust the disk until it is tested and known good.
 
1 members found this post helpful.
Old 08-14-2012, 10:16 PM   #10
sevs
Member
 
Registered: Jul 2008
Location: Ukraine, Kharkov
Distribution: debian, knoppix, mandriva, asplinux, altlinux
Posts: 108

Original Poster
Rep: Reputation: 19
Quote:
I personally prefer the manufacturer's tools and use smartmontools only as a first indicator.
Ok, I should do so.

Quote:
1. Backup your data (which you should do anyways periodically).
That's too much info to backup for me (about 30Gb - no music, no videos, just my work and school docs)
But I'm doing it.

Quote:
2. Don't trust the disk until it is tested and known good.
Till weekend I have to trust it, 'cause its too much work I have.

Thanks for advices.
 
Old 08-14-2012, 11:46 PM   #11
aus9
Guru
 
Registered: Oct 2003
Posts: 5,056

Rep: Reputation: Disabled
try

http://www.ultimatebootcd.com/

as a good range of detection tools for hardware.

2) what journal system were you using?.....I suspect ext4

3) its good to set a check on a regular basis....tune2fs is the tool and I prefer 30 boots which means a weekly check for me.

but if you have important data.....why wouldn't you back up to another media????
and you 'should" do more regular fs checks

good luck

BTW if you only have 30G to backup.....an usb external hard drive it handle that easy peasy
 
1 members found this post helpful.
Old 08-15-2012, 08:27 AM   #12
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,204
Blog Entries: 3

Rep: Reputation: 1433Reputation: 1433Reputation: 1433Reputation: 1433Reputation: 1433Reputation: 1433Reputation: 1433Reputation: 1433Reputation: 1433Reputation: 1433
Member Response

Hi,

I will add that when you change mount orientation for a drive that has been in use for sometime(depends on activity & type) that you can have potential compliance errors.

One should try to keep the drive in the original orientation that the filesystem was create in. Head attachment type will dictate the chance of errors when moved from vertical to horizontal or vice verse. This problem was relevant with older drive designs. Newer portable drives do not have the head gimble issues of older designs.

Look at the new designs for external HDD cases. Most designs will allow you to flip horizontal but cannot stand vertical unless you use a stand attachment (if provided, most are not including this attachment any longer). Older 3 1/2 externals would allow different orientation but the head assembly is a better design and the HDD are designed for the orientation changes. You pay $$ for this.
HTH!
 
1 members found this post helpful.
Old 08-15-2012, 10:16 AM   #13
sevs
Member
 
Registered: Jul 2008
Location: Ukraine, Kharkov
Distribution: debian, knoppix, mandriva, asplinux, altlinux
Posts: 108

Original Poster
Rep: Reputation: 19
I have its boot-flash.

Quote:
2) what journal system were you using?.....I suspect ext4
No,it is ext3. When I was installing the system (actualy upgrading from "Lenny") I heard about ext4, but I also heard that it was some "buggy".So I did not choose it for '/home' directory.

Quote:
3) its good to set a check on a regular basis....tune2fs is the tool and I prefer 30 boots which means a weekly check for me.
Oh, it is set to 28 boots and half-year period. But the thing is that I rarely reboot the system.

Quote:
why wouldn't you back up to another media????
I have only 8Gb stick. And it is all my backup for now.
But I also use Dropbox and I'm going to use google-drive and buy extaernal HDD.

Quote:
One should try to keep the drive in the original orientation that the filesystem was create in. Head attachment type will dictate the chance of errors when moved from vertical to horizontal or vice verse. This problem was relevant with older drive designs. Newer portable drives do not have the head gimble issues of older designs.
You see, I look at any techincs so that there is no old tec for me. (yes, I still use zip-disks and diskettes at my desktop). So, how old drive designs do you mean (approximate year of design) saying 'older drive designs'.

Thanks for help.
 
Old 08-15-2012, 11:09 AM   #14
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,204
Blog Entries: 3

Rep: Reputation: 1433Reputation: 1433Reputation: 1433Reputation: 1433Reputation: 1433Reputation: 1433Reputation: 1433Reputation: 1433Reputation: 1433Reputation: 1433
Member Response

Hi,

HDD diagnostics do not care about the filesystem since this is not destructive test. Best to use the drive manufacturers diagnostic set if possible.

Filesystem maintenance is another story, use 'fsck';
Quote:
excerpt from 'man fsck';
NAME
fsck - check and repair a Linux file system

SYNOPSIS
fsck [-lsAVRTMNP] [-C [fd]] [-t fstype] [filesys...] [--] [fs-specific-options]

DESCRIPTION
fsck is used to check and optionally repair one or more Linux file systems. filesys can be a device name (e.g. /dev/hdc1, /dev/sdb2),
a mount point (e.g. /, /usr, /home), or an ext2 label or UUID specifier (e.g. UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd or
LABEL=root). Normally, the fsck program will try to handle filesystems on different physical disk drives in parallel to reduce the
total amount of time needed to check all of the filesystems.

If no filesystems are specified on the command line, and the -A option is not specified, fsck will default to checking filesystems in
/etc/fstab serially. This is equivalent to the -As options.

The exit code returned by fsck is the sum of the following conditions:
0 - No errors
1 - File system errors corrected
2 - System should be rebooted
4 - File system errors left uncorrected
8 - Operational error
16 - Usage or syntax error
32 - Fsck canceled by user request
128 - Shared library error
The exit code returned when multiple file systems are checked is the bit-wise OR of the exit codes for each file system that is checked.

In actuality, fsck is simply a front-end for the various file system checkers (fsck.fstype) available under Linux. The file system-spe-
cific checker is searched for in /sbin first, then in /etc/fs and /etc, and finally in the directories listed in the PATH environment
variable. Please see the file system-specific checker manual pages for further details.
on the unmounted filesystem and you should boot the system in single user mode or via LiveCD.
 
1 members found this post helpful.
Old 08-23-2012, 09:04 AM   #15
sevs
Member
 
Registered: Jul 2008
Location: Ukraine, Kharkov
Distribution: debian, knoppix, mandriva, asplinux, altlinux
Posts: 108

Original Poster
Rep: Reputation: 19
So, today I've checked my hard disk with DLG tool (it is for WD HDDs) with extended test and it showed no errors.
I didn't try to check HDD with gsmartcontrol.

Thanks to everyone who tried (and did) to help.
 
  


Reply

Tags
hardware, hdd


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
hdd problem kateausten Linux - Newbie 11 05-01-2011 08:36 PM
HDD problem? deliriumfk Linux - Hardware 7 10-23-2010 06:19 AM
Dual HDD Interface Problem, Linux on SATA, NTFS Part on IDE HDD LILO Not Loading Blade44 Linux - Hardware 2 02-01-2005 06:56 PM
hdd problem hariiyer Linux - Hardware 4 01-03-2005 04:26 AM
HDD problem, scancode problem and grub EJ_INSIDE Debian 2 07-15-2004 09:36 AM


All times are GMT -5. The time now is 03:26 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration