Fedora Linux Support Community & Resources Center
  #1  
Old 3rd March 2009, 09:30 PM
BrillianceLin Offline
Registered User
 
Join Date: Jan 2007
Posts: 143
fsck how to?

Hi everyone
I find out these message in my system log when my harddrive spin like crazy and temporary freeze the machine (when I logon, shutdown or reboot the machine as well).

Mar 3 03:36:44 localhost kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Mar 3 03:36:44 localhost kernel: ata1.00: BMDMA stat 0x24
Mar 3 03:36:44 localhost kernel: ata1.00: cmd c8/00:08:0a:f0:f0/00:00:00:00:00/e5 tag 0 dma 4096 in
Mar 3 03:36:44 localhost kernel: res 51/40:03:0f:f0:f0/00:00:00:00:00/e5 Emask 0x9 (media error)
Mar 3 03:36:44 localhost kernel: ata1.00: status: { DRDY ERR }
Mar 3 03:36:44 localhost kernel: ata1.00: error: { UNC }
Mar 3 03:36:45 localhost kernel: ata1.00: configured for UDMA/100
Mar 3 03:36:45 localhost kernel: ata1: EH complete
Mar 3 03:36:49 localhost kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Mar 3 03:36:49 localhost kernel: ata1.00: BMDMA stat 0x24
Mar 3 03:36:49 localhost kernel: ata1.00: cmd c8/00:08:0a:f0:f0/00:00:00:00:00/e5 tag 0 dma 4096 in
Mar 3 03:36:49 localhost kernel: res 51/40:03:0f:f0:f0/00:00:00:00:00/e5 Emask 0x9 (media error)
Mar 3 03:36:49 localhost kernel: ata1.00: status: { DRDY ERR }
Mar 3 03:36:49 localhost kernel: ata1.00: error: { UNC }
Mar 3 03:36:49 localhost kernel: ata1.00: configured for UDMA/100
Mar 3 03:36:49 localhost kernel: ata1: EH complete
Mar 3 03:36:54 localhost kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Mar 3 03:36:54 localhost kernel: ata1.00: BMDMA stat 0x24
Mar 3 03:36:54 localhost kernel: ata1.00: cmd c8/00:08:0a:f0:f0/00:00:00:00:00/e5 tag 0 dma 4096 in
Mar 3 03:36:54 localhost kernel: res 51/40:03:0f:f0:f0/00:00:00:00:00/e5 Emask 0x9 (media error)
Mar 3 03:36:54 localhost kernel: ata1.00: status: { DRDY ERR }
Mar 3 03:36:54 localhost kernel: ata1.00: error: { UNC }
Mar 3 03:36:54 localhost kernel: ata1.00: configured for UDMA/100
Mar 3 03:36:54 localhost kernel: ata1: EH complete
Mar 3 03:36:58 localhost kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Mar 3 03:36:58 localhost kernel: ata1.00: BMDMA stat 0x24
Mar 3 03:36:58 localhost kernel: ata1.00: cmd c8/00:08:0a:f0:f0/00:00:00:00:00/e5 tag 0 dma 4096 in
Mar 3 03:36:58 localhost kernel: res 51/40:03:0f:f0:f0/00:00:00:00:00/e5 Emask 0x9 (media error)
Mar 3 03:36:58 localhost kernel: ata1.00: status: { DRDY ERR }
Mar 3 03:36:58 localhost kernel: ata1.00: error: { UNC }
Mar 3 03:36:58 localhost kernel: ata1.00: configured for UDMA/100
Mar 3 03:36:58 localhost kernel: ata1: EH complete
Mar 3 03:37:03 localhost kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Mar 3 03:37:03 localhost kernel: ata1.00: BMDMA stat 0x24
Mar 3 03:37:03 localhost kernel: ata1.00: cmd c8/00:08:0a:f0:f0/00:00:00:00:00/e5 tag 0 dma 4096 in
Mar 3 03:37:03 localhost kernel: res 51/40:03:0f:f0:f0/00:00:00:00:00/e5 Emask 0x9 (media error)
Mar 3 03:37:03 localhost kernel: ata1.00: status: { DRDY ERR }
Mar 3 03:37:03 localhost kernel: ata1.00: error: { UNC }
Mar 3 03:37:03 localhost kernel: ata1.00: configured for UDMA/100
Mar 3 03:37:03 localhost kernel: ata1: EH complete
Mar 3 03:37:07 localhost kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Mar 3 03:37:07 localhost kernel: ata1.00: BMDMA stat 0x24
Mar 3 03:37:07 localhost kernel: ata1.00: cmd c8/00:08:0a:f0:f0/00:00:00:00:00/e5 tag 0 dma 4096 in
Mar 3 03:37:07 localhost kernel: res 51/40:03:0f:f0:f0/00:00:00:00:00/e5 Emask 0x9 (media error)
Mar 3 03:37:07 localhost kernel: ata1.00: status: { DRDY ERR }
Mar 3 03:37:07 localhost kernel: ata1.00: error: { UNC }
Mar 3 03:37:07 localhost kernel: ata1.00: configured for UDMA/100
Mar 3 03:37:07 localhost kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
Mar 3 03:37:07 localhost kernel: sd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
Mar 3 03:37:07 localhost kernel: Descriptor sense data with sense descriptors (in hex):
Mar 3 03:37:07 localhost kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Mar 3 03:37:07 localhost kernel: 05 f0 f0 0f
Mar 3 03:37:07 localhost kernel: sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
Mar 3 03:37:07 localhost kernel: end_request: I/O error, dev sda, sector 99676175
Mar 3 03:37:07 localhost kernel: ata1: EH complete
Mar 3 03:37:08 localhost kernel: sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
Mar 3 03:37:08 localhost kernel: sd 0:0:0:0: [sda] Write Protect is off
Mar 3 03:37:08 localhost kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 3 03:37:08 localhost kernel: sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
Mar 3 03:37:08 localhost kernel: sd 0:0:0:0: [sda] Write Protect is off
Mar 3 03:37:08 localhost kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

So, I wanna run fsck and tried to fix this problem. But I do not know how to unmount the systemdrive. Cause it will not let you to do that once you have booted into system. And I tried go into live USB. But it seems like the live usb is not able to access my systemdrive. Of course, running fsck on a mounted drive is a suicide move. I hope some one can give me a hint how to solve this problem. It seems like a common bug on SATA drive. Not only F10, but some people have the same problem on other distributor like Unbuntu and Debian. I just hope the fsck trick can at lest get rid of this thing temporary.
My hard drive vendor is Fujisu. But I forgot the model of the hard drive....
Any idea?
__________________
If Microsoft is god, then now it is time for me to bring it down to hell!
Reply With Quote
  #2  
Old 3rd March 2009, 09:42 PM
stefan1975 Offline
"Stefan the converted" -- forum Macintosh® Glee Club leader
 
Join Date: May 2007
Location: 127.0.0.1
Age: 39
Posts: 1,247
what about booting a live-cd (fedora or systemrescue) with the options:

boot: linux rescue nomount

and then in a terminal do something like:

Code:
fsck.ext[2/3/4] -vfy /dev/sda[1/2/3/...]

or

e2fsck -y /dev/sda[1/2/3...]
does that work?
stefan
__________________
"$ su - bofh"
OS: Mac OSX Snow Leopard (x64 by default), W7_Enterprise_X64, F12_x64_KDE
Hardware: late 2009 Macbook 13", MSI Wind 10"
Browser: Opera 10.10, Safari 4
Registered linux user #459910
Reply With Quote
  #3  
Old 3rd March 2009, 10:39 PM
BrillianceLin Offline
Registered User
 
Join Date: Jan 2007
Posts: 143
Quote:
Originally Posted by stefan1975 View Post
what about booting a live-cd (fedora or systemrescue) with the options:

boot: linux rescue nomount

and then in a terminal do something like:

Code:
fsck.ext[2/3/4] -vfy /dev/sda[1/2/3/...]

or

e2fsck -y /dev/sda[1/2/3...]
does that work?
stefan
Hi Stefan, thanks for your reply. I did not see the boot: linux rescue nomount option. But there is a option with called boot. Is it the one you are talking about. Thanks for your hint, I will tried it out when it is clear they are the same thing.
BL
__________________
If Microsoft is god, then now it is time for me to bring it down to hell!
Reply With Quote
  #4  
Old 4th March 2009, 06:44 AM
stefan1975 Offline
"Stefan the converted" -- forum Macintosh® Glee Club leader
 
Join Date: May 2007
Location: 127.0.0.1
Age: 39
Posts: 1,247
when you boot F10 you have to press <escape> i think and in the GRUB (bootloader) options where all the boot options are (like quiet and 2.6.27.bla) add rescue nomount. I have not used this under F10 so I am guessing a little here that it still works.

Another option might be to boot in single user mode (init 1 or init s from a terminal) and unmount the partitions from there. And some of the latest live cd's have a boot option that let you recover broken systems, at least when booting from a cd your disk will not be mounted.

stefan
__________________
"$ su - bofh"
OS: Mac OSX Snow Leopard (x64 by default), W7_Enterprise_X64, F12_x64_KDE
Hardware: late 2009 Macbook 13", MSI Wind 10"
Browser: Opera 10.10, Safari 4
Registered linux user #459910
Reply With Quote
  #5  
Old 4th March 2009, 07:42 AM
BrillianceLin Offline
Registered User
 
Join Date: Jan 2007
Posts: 143
Quote:
Originally Posted by stefan1975 View Post
when you boot F10 you have to press <escape> i think and in the GRUB (bootloader) options where all the boot options are (like quiet and 2.6.27.bla) add rescue nomount. I have not used this under F10 so I am guessing a little here that it still works.

Another option might be to boot in single user mode (init 1 or init s from a terminal) and unmount the partitions from there. And some of the latest live cd's have a boot option that let you recover broken systems, at least when booting from a cd your disk will not be mounted.

stefan
Thanks, But it seem the live usb(CD, same thing from a ISO image) can not access to ext3 partition. Maybe it is a new feature they add on Feodra 10 to prevent some one mess up the filesystem. I will tried your suggestion out one by one till one of em works. Just hope one of them will.

BL
__________________
If Microsoft is god, then now it is time for me to bring it down to hell!
Reply With Quote
  #6  
Old 4th March 2009, 01:48 PM
BrillianceLin Offline
Registered User
 
Join Date: Jan 2007
Posts: 143
Quote:
Originally Posted by stefan1975 View Post
when you boot F10 you have to press <escape> i think and in the GRUB (bootloader) options where all the boot options are (like quiet and 2.6.27.bla) add rescue nomount. I have not used this under F10 so I am guessing a little here that it still works.

Another option might be to boot in single user mode (init 1 or init s from a terminal) and unmount the partitions from there. And some of the latest live cd's have a boot option that let you recover broken systems, at least when booting from a cd your disk will not be mounted.

stefan
Things getting funny. fsck said the hard drive I tried to repair is not a ext2/3 drive. But in fact it is otherwise I can not install Fedora in it. I think the lvm is preventing live usb acecess to the partition. Any though...
__________________
If Microsoft is god, then now it is time for me to bring it down to hell!
Reply With Quote
  #7  
Old 4th March 2009, 02:08 PM
stefan1975 Offline
"Stefan the converted" -- forum Macintosh® Glee Club leader
 
Join Date: May 2007
Location: 127.0.0.1
Age: 39
Posts: 1,247
oooooo, it is LVM. That changes things a bit. I do not use LVM myself. From what I recall you can FSCK a LVM partition just fine, but you have to select *not* the physical disk (/dev/sda1) but the volume (/dev/VolGroup00/LogVol00) instead.

you can check the volume groups with "lvdisplay"

stefan
__________________
"$ su - bofh"
OS: Mac OSX Snow Leopard (x64 by default), W7_Enterprise_X64, F12_x64_KDE
Hardware: late 2009 Macbook 13", MSI Wind 10"
Browser: Opera 10.10, Safari 4
Registered linux user #459910
Reply With Quote
  #8  
Old 5th March 2009, 06:41 AM
BrillianceLin Offline
Registered User
 
Join Date: Jan 2007
Posts: 143
Quote:
Originally Posted by stefan1975 View Post
oooooo, it is LVM. That changes things a bit. I do not use LVM myself. From what I recall you can FSCK a LVM partition just fine, but you have to select *not* the physical disk (/dev/sda1) but the volume (/dev/VolGroup00/LogVol00) instead.

you can check the volume groups with "lvdisplay"

stefan
I did tried that, but it pop up something like error 2 on fsck /dev/... I can not remember what exact the last section of the complain but the error 2 was definitely there. I have no idea what that mean. Is it possible the LVM causing this kind of error? I have made a clean reinstall and see what will happen. No, matter what the outcome will be, I can now access to system drive under live USB mode(which I couldn't if the system drive is LVM). Therefore, I can at least perform rescue or back up in USB mode under my current knowledge to operate the system. I am sure there is a way to do the some thing for LVM. But I still need time to find out.
Just for curious, how do I boot the kernel from grub without mounting the system drive? If I can do that it will make life a bit easier some time. I tried boot into init 1. But there system drive was still mounted, and can not be unmount.
Thanks for all your help, I will see what will happen for the rest of the week.


Well, just after I post this reply, the problem comeback again. So, the LVM does not create this problem, it is something else...
__________________
If Microsoft is god, then now it is time for me to bring it down to hell!

Last edited by BrillianceLin; 5th March 2009 at 07:22 AM.
Reply With Quote
  #9  
Old 5th March 2009, 01:10 PM
Iron_Mike Offline
Registered User
 
Join Date: Jul 2005
Location: Ft Huachuca, AZ
Posts: 3,772
Try this: Open a terminal window and change to root and type:

touch /forcefsck

Then reboot, it will force a file check. You will see that the boot splash is taking it's time going through the boot cycle.

Mike
Reply With Quote
  #10  
Old 6th March 2009, 12:09 PM
BrillianceLin Offline
Registered User
 
Join Date: Jan 2007
Posts: 143
Quote:
Originally Posted by Iron_Mike View Post
Try this: Open a terminal window and change to root and type:

touch /forcefsck

Then reboot, it will force a file check. You will see that the boot splash is taking it's time going through the boot cycle.

Mike
Long time no see, thanks for your suggestion.
__________________
If Microsoft is god, then now it is time for me to bring it down to hell!
Reply With Quote
  #11  
Old 7th March 2009, 02:19 AM
Iron_Mike Offline
Registered User
 
Join Date: Jul 2005
Location: Ft Huachuca, AZ
Posts: 3,772
So do you get any errors when you boot? If not any errors in the log are non fatal, so don't worry about it...

Mike
Reply With Quote
  #12  
Old 7th March 2009, 04:53 AM
BrillianceLin Offline
Registered User
 
Join Date: Jan 2007
Posts: 143
Quote:
Originally Posted by Iron_Mike View Post
So do you get any errors when you boot? If not any errors in the log are non fatal, so don't worry about it...

Mike
No, nothing show up during the boot. But it seems like error will pile up over time and the boot time and shut down time will be long enough challenging my patient. I have made a clean install couple days ago, and did not use LVM to tried to rule out it is lvm cause this problem. So far it seems it the problem is not created by lvm. But lvm may have something to do with the error accumulation. I have not let the system keep running for 2 week as before. So, I think I have to wait for while. I do not know it is a kernel problem. Cause the current kernel 2.6.27.19-170.2.35 and the last one keep make no different.
But thanks for the info. I will let it run, if it keep pile up, I will fsck it and see if the problem will temporary go away.
__________________
If Microsoft is god, then now it is time for me to bring it down to hell!
Reply With Quote
  #13  
Old 7th March 2009, 03:07 AM
Nokia Offline
Registered User
 
Join Date: Aug 2006
Location: /dev/realm/{Abba,Carpenters,...stage}
Posts: 3,286
The output in the first post seems more like a kernel error/bug to me. I might be wrong, but nevertheless it wouldn't hurt trying a newer kernel first before engaging in dangerous activities like using fsck on a buggy kernel on what could be a normal functioning drive.

(In other words, yes I see those media errors messages, but I'm not sure where the culprit is)
__________________
For safer browsing, use OpenDNS nameservers 208.67.222.222 and 208.67.220.220

SELinux User Guide

AutoPager
Reply With Quote
Reply

Tags
fsck

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

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 On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Cannot run fsck Hillbilly Using Fedora 5 5th July 2007 08:26 PM
Cannot run fsck.. please help cyberbob Using Fedora 4 30th April 2007 05:05 PM


Current GMT-time: 21:01 (Monday, 01-09-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat