You are not logged in.
Hi !
I have a problem with Arch, when I boot to Arch after one hour all the files seems to disappear of my HDD, they're no reachable, my computer slows down and finally he stops reacting. I have to hard reboot...
When I boot after that I have fsck errors after each hard reboot but also when I reboot normally, I have these errors :
/dev/sda3: recovering journal
/dev/sda3 contains a file system with errors, check forced.
/dev/sda3:
Inodes that were part of a corrupted orphaned linked list found.
/dev/sda3: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options)
*****FILESYSTEM CHECK FAILED*****
* please run fsck manually. After le- *
* aving this maintenance shell, the *
* system will reboot automatically *
**********************************
sh: can't access tty; job control turned off
[rootfs /]#_At first I thought about my HDD was about to die, but I installed Arch on another HDD and I had the same errors as the first HDD.
Do you know what is happening to me ? Do you need more information ?
Thanks !
Edit : Is that possible that the problem is about the kernel ? This problem seems to have appeared at the same time as I updated from 3.7 to 3.8. Coincidence or not ?
Last edited by Ichigo-Roku (2013-03-22 15:48:29)
Offline
Entire dmesg log would help when the computer starts to slow down.
This could be an issue with the ATA/SATA cable or controller or even PSU.
Try to change the cable and/or (s)ata port on the mainboard and see if that helps. If you could get an output from smartctl utility it would be great:
smartctl -a /dev/sda
Last edited by combuster (2013-03-22 08:36:45)
Offline
These errors are typical for cable/controller issue, change those first and then see if anything has changed.
This also could be a bug in controller driver, but for that you could try to install kernel-lts and see if the problem is resolved.
Offline
A few minutes after my last answer I updated my arch and saw that a new update of linux package was available. It's Linux 3.8.4-1-ARCH and it solved the problem, it's been more than one hour and I don't have any problems anymore.
So it really was the controller driver. Thanks to you I now understand why it happened.
Problem solved.
Offline
Yeah, funny thing is I cant find any patch in the last two stable releases in 3.8.x series that could have resolved this issue.
One was related to the loopback devices (this shouldn't be it), other one for DM (that really could have been it based on the commit log) but it was already present in 3.8.3 and I don't think you have a configuration that could have triggered the bug (maybe I'm wrong).
I'm puzzled but I'm really glad that this problem is solved.
Offline
There is all my configuration if I'm not forgotten something :
CPU : Intel Core i3 3220
Mobo : Gigabyte Z77-DS3H
GPU : Nvidia GTX 650 Ti
PSU : Cooler Master Silent Pro M (500W)
HDD : Samsung Spinpoint F1 1To
RAM : G.Skill RipJaws PC3-12800 CL9-9-9-24
Last edited by Ichigo-Roku (2013-03-23 08:18:53)
Offline