[SOLVED] Permanent filesystem corruption on reiserfs, ext3 and ext4 - disk failure?
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Permanent filesystem corruption on reiserfs, ext3 and ext4 - disk failure?
I have been having problems with filesystem corruption on my eeepc 1000H for a long time now. I have tried using different filesystems, kernels and distributions (arch, slackware) to no effect. I am starting to grow suspicious that this problem lies somewhere else, as I haven't seen anyone else having similar problems in such a variety of scenarios.
I have tried testing my ram using memtest86+, didn't come up with anything after a full run through. I also have tried using e2fsck -c to check for bad blocks, it finds none. I had a go at using smartctl but wasn't really sure what I was doing. I did a long test and it came up with nothing anyway.
This problem is in addition to the problems I've been having with my intel graphics chip and KMS. A lot of the time there are lockups when booting into X, which can only be gotten out of by a hard reset. This is sometimes what causes the original filesystem errors. I've stopped messing around with KMS for now to eliminate this but my current system in unbootable.
I'm guessing my disk is wrecked but have as yet seen no definitive proof. Can anyone recommend anything that I should do?
I am currently on ext4 with a custom kernel 2.6.33-rc6 (the stock kernel shipping with slackware does not have the elantech extension for psmouse included). When I was using arch, I was just using the stock kernels.
I'm still on ext3 because I want others to have the headaches with ext4 and to have all of them sorted before I go near it.
If things continually find no disk errors, the disk is probably OK. I'd go to 'safe defaults' in the BIOS. Next I'd back up fully elsewhere. Elaborate on your problems with KMS. You can boot from an install cd, or if the kernel boots boot with init=/bin/bash as a kernel option. You'll get a root shell instead of running init. You'll have to work at it from there
/sbin/mount /dev/whatsit -t ext4 /
a PATH statement, etc. but you can get in and repair things.
HDD model is ST980811AS from hdparm -I. From google I get that it's a Seagate Momentus 80GB
Here's my lspci -v output:
Code:
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
Subsystem: ASUSTeK Computer Inc. Device 8340
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information <?>
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 8340
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f7f00000 (32-bit, non-prefetchable) [size=512K]
I/O ports at dc00 [size=8]
Memory at d0000000 (32-bit, prefetchable) [size=256M]
Memory at f7ec0000 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
Subsystem: ASUSTeK Computer Inc. Device 8340
Flags: bus master, fast devsel, latency 0
Memory at f7f80000 (32-bit, non-prefetchable) [size=512K]
Capabilities: [d0] Power Management version 2
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
Subsystem: ASUSTeK Computer Inc. Device 831a
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f7eb8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel <?>
Capabilities: [130] Root Complex Link <?>
Kernel driver in use: HDA Intel
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 00001000-00001fff
Memory behind bridge: 40000000-401fffff
Prefetchable memory behind bridge: 0000000040200000-00000000403fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 830f
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: fbf00000-fbffffff
Prefetchable memory behind bridge: 0000000040400000-00000000405fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 830f
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel driver in use: pcieport
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=02, sec-latency=0
I/O behind bridge: 00002000-00002fff
Memory behind bridge: f8000000-fbefffff
Prefetchable memory behind bridge: 00000000f0000000-00000000f6ffffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 830f
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel driver in use: pcieport
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. Device 830f
Flags: bus master, medium devsel, latency 0, IRQ 23
I/O ports at d400 [size=32]
Kernel driver in use: uhci_hcd
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. Device 830f
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at d480 [size=32]
Kernel driver in use: uhci_hcd
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. Device 830f
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at d800 [size=32]
Kernel driver in use: uhci_hcd
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. Device 830f
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at d880 [size=32]
Kernel driver in use: uhci_hcd
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. Device 830f
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at f7eb7c00 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=05, subordinate=05, sec-latency=32
Capabilities: [50] Subsystem: ASUSTeK Computer Inc. Device 830f
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
Subsystem: ASUSTeK Computer Inc. Device 830f
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information <?>
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02) (prog-if 80 [Master])
Subsystem: ASUSTeK Computer Inc. Device 830f
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 19
I/O ports at 01f0 [size=8]
I/O ports at 03f4 [size=1]
I/O ports at 0170 [size=8]
I/O ports at 0374 [size=1]
I/O ports at ffa0 [size=16]
Capabilities: [70] Power Management version 2
Kernel driver in use: ata_piix
01:00.0 Network controller: RaLink RT2860
Subsystem: RaLink Device 2790
Physical Slot: eeepc-wifi
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at fbef0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Kernel driver in use: rt2860
Kernel modules: rt2860sta, rt2800pci
03:00.0 Ethernet controller: Attansic Technology Corp. Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (rev b0)
Subsystem: ASUSTeK Computer Inc. Device 8324
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at fbfc0000 (64-bit, non-prefetchable) [size=256K]
I/O ports at ec00 [size=128]
Capabilities: [40] Power Management version 2
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [58] Express Endpoint, MSI 00
Capabilities: [6c] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [180] Device Serial Number ff-22-52-d9-00-23-54-ff
Kernel driver in use: ATL1E
My problems with KMS don't exist any more as I have stopped using it! There are various posts on this forum about it being unstable. My problem occurs at the moment before X is involved anyway, just booting using text mode from lilo.
I've tried booting from a usb stick and running fsck from there, it returns the same results. When I boot up normally in slackware it always returns me to the single-user shell anyway so that's no different is it?
I'll attach a couple of outputs from consecutive runs of
I think that this drive is reasonably likely to fail. The reasons being:
Code:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
189 High_Fly_Writes 0x003a 018 018 000 Old_age Always - 82
193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always - 471825
When value goes down to threshold, the drive can fail at any time. This is more true for Pre-fail attributes than for Old_age (means the drive is old and has reached end of life in a statistical sense)
There's also the error listed there.
This suggests the drive is old and is wearing out, this may be a reason for the persistent corruption. It also seems that the drive has been overheating, and has overheated at least once.
Last edited by H_TeXMeX_H; 02-10-2010 at 09:04 AM.
That's the second laptop I've killed then. I guess it serves me right for using them more or less as desktops! Thanks a lot for interpreting that smartctl output H_TeXMeX_H. Now seems like as good a time as any to have a look at the world of SSDs!
Have you any errors in the logs? particularly /var/log/messages?
Is acpid running?
Do you hear a fan blowing warm air and does it change speed?
My laptop always blows warm air. If the box is lightly used, the fan remains slow. If I'm compiling, the fan speed rises.
If you set up again, install acpitools. Then you can run acpitool -t and find your internal temperatures. Also run lm_sensors, let it set up your sensors, and run acpid with the -l option for a week. Then you can look in the logs and see all the signals the box gives, and set up scripts and events to do what you want with them. Slackware sadly gives you squat there. For instance, my laptop has a hibernate script on the lid switch, so you turn off by closing the lid.
Thanks for the tips business_kid. There's already a package that I use to handle acpi, it's called eeepc-acpi-scripts, made by Alien Bob. This, along with kde and the eeepc kernel module, handles most powersaving, suspend2ram etc. and I dynamically underclock anyway. I've kept my eye on the temperature in the past but as there's only an intel atom processor inside the eee 1000h heat has not really been an issue in general.
Having said that, I recently sent it back to be repaired for a seperate issue and they (ASUS) replaced my motherboard without putting a heatsink on the processor. I didn't realise that this was the case until it suddenly shut down, having reached the critical temperature. As you can imagine my heartfelt thanks and respect goes out to the helpful folk at ASUS. It is worth noting that I was experiencing these errors before this happened (hence not mentioning it) but that would probably explain why smartctl also shows some high temperatures in the past.
Anyway, I've bitten the bullet and ordered myself a 30GB SSD. I think I'm still within my warranty period no the old hard disk but I kinda wanted an SSD anyway! I'll mark this thread as solved when it arrives this weekend, assuming that was the problem of course.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.