You are not logged in.
Solution: Discard old laptop, buy new laptop
I have an Acer Aspire 5103WLMi. For about 2 months now, Arch has been running smoothly. Until 2 weeks ago.
It all started when I tried to install and configure autofs on Arch x86_64. On the next reboot, all manner of errors were printed to the screen, to the effect that the internal hard drive was only being mounted read-only, rendering the system unusable. I tried to find a solution, but there were no references to read-only anywhere; fstab, grub etc. None that I could find.
I tried reinstalling. However, x86_64 Arch refused to boot properly first time due to the exact same error; and I *know* that I'm configuring everything correctly. I managed (somehow) to coerce i686 Arch to install, and things "work".
Seemingly out of the blue, during normal operation, all running applications will stop, and spit out error after error to the effect of "Cannot Write to Read Only Filesystem!". Sakura won't load (Input/Output error, apparently), and the only way to shut down the laptop is a hard reset (I can't log in as root or use sudo because it wants to write to the filesystem first, which it obviously can't.
Now, I'm going to be giving the insides of this laptop a good cleanout this weekend, and I'm in the process of backing up all of my data, but I was wondering if anyone else has come across a similar form of misbehaviour; or (with a bit of luck) some potential solutions?
This is very peculiar, because there seems to be no reason why the laptop suddenly loses write permissions to the hard drive. Cheers.
Edit: I think I should point out that my /boot partition is Ext2, and / and /home are Ext3
Last edited by aphirst (2013-03-27 14:51:38)
ArchLinux | x86_64 | linux-ck-ivybridge
ThinkPad X230 | 12.5" | i5-3320M (2.5GHz) | HD 4000 | 16GB (1600MHz) | 256GB mSATA SSD | 2TB HDD
ThinkPad T430 | 14.1" | i7-3520M (2.9GHz) | GF108M (NVS 5400M) | 16GB (1600MHz) | 256GB mSATA SSD | 1TB HDD | 500GB HDD
Offline
Could you please post your /etc/autofs/auto.media configuration file? Hopefully your HDD partitions aren't listed in there...
Last edited by kclive18 (2008-07-14 14:30:52)
My Rigs:
- Mid-2007 iMac 20", Intel 2GHz Core 2 Duo, 2x1GB DDR2-800, 250GB SATA HDD, and...MIGHTY MOUSE!!! , OSX 10.5 Leopard, ATI Radeon 2400XT 128MB
- HP zv6203cl, AMD Athlon 64 3200 S939, 2x512MB DDR400, 80GB 4200rpm HDD, ATI Radeon Xpress 200M 128MB, Arch i686
- 1986 Gibson SG Junior Cherry Red, Ibanez 15W amp, DigiTech RP250 modeling processor
Offline
Be sure to keep your data backed up! I had a similar problem and it turned out my hdd was slowly dying. (Being about 3/4 years old...but I let it fall down once ) Check the state with smartctl to see if there are any problems.
Offline
Smartctl gives me the impression it's my Hard Drive:
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1711
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 6194
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 3291
10 Spin_Retry_Count 0x0033 223 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1218
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 294
193 Load_Cycle_Count 0x0032 088 088 000 Old_age Always - 123904
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Lifetime Min/Max 15/62)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 17
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 118
222 Loaded_Hours 0x0032 094 094 000 Old_age Always - 2425
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 444
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
Everything being either Old_age or Pre-fail is not encouraging. Additionally, in the output is what I believe to be records of what caused my strange read-only behaviour:
Error 19 occurred at disk power-on lifetime: 3287 hours (136 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 01 11 18 6a e1 Error: ICRC, ABRT 1 sectors at LBA = 0x016a1811 = 23730193
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 48 c4 17 6a e1 00 04:43:08.023 READ DMA
c8 00 48 14 e3 69 e1 00 04:43:08.022 READ DMA
c8 00 a0 5c e2 69 e1 00 04:43:08.010 READ DMA
c8 00 08 9c e5 69 e1 00 04:43:08.010 READ DMA
c8 00 20 5c e5 69 e1 00 04:43:08.009 READ DMA
Could this truly be referring to my problem, since the 'logs' show that the *exact same* error occurred many times.
Not that this tells me how to fix it...
Well, if anyone knows if there is a solution, I'd love to know. If the only solution is to ditch the Hard Drive, fair enough. Either way: I'm backing up all of my important data ASAP.
Cheers.
Oh, and kclive18, after I noticed that I couldn't get onto my Drive, I reinstalled arch, leaving no trace of /etc/autofs/auto.media.
Additionally, somehow I have now been able to install Arch x86_64, but the problems still occur...
ArchLinux | x86_64 | linux-ck-ivybridge
ThinkPad X230 | 12.5" | i5-3320M (2.5GHz) | HD 4000 | 16GB (1600MHz) | 256GB mSATA SSD | 2TB HDD
ThinkPad T430 | 14.1" | i7-3520M (2.9GHz) | GF108M (NVS 5400M) | 16GB (1600MHz) | 256GB mSATA SSD | 1TB HDD | 500GB HDD
Offline
Update: I have replaced the Hard Drive.
I get the same error.
I am pissed ^___^
I;m starting to think "was there something Ubuntu automagically managed/maintained which arch isn't doing; which made my hard drive not magically unmount itself"?
If anyone has *any* ideas, *please* help.
ArchLinux | x86_64 | linux-ck-ivybridge
ThinkPad X230 | 12.5" | i5-3320M (2.5GHz) | HD 4000 | 16GB (1600MHz) | 256GB mSATA SSD | 2TB HDD
ThinkPad T430 | 14.1" | i7-3520M (2.9GHz) | GF108M (NVS 5400M) | 16GB (1600MHz) | 256GB mSATA SSD | 1TB HDD | 500GB HDD
Offline
I have had one idea. I will take apart the laptop and attempt to gauge whether or not the internal HDD connection is satisfactory. Possibly, the connection could momentarily loosen, and cause all sorts of hard-drives-aren-hot-swappable failures.
I will post back tomorrow ... Still, other ideas are *most* welcome.
ArchLinux | x86_64 | linux-ck-ivybridge
ThinkPad X230 | 12.5" | i5-3320M (2.5GHz) | HD 4000 | 16GB (1600MHz) | 256GB mSATA SSD | 2TB HDD
ThinkPad T430 | 14.1" | i7-3520M (2.9GHz) | GF108M (NVS 5400M) | 16GB (1600MHz) | 256GB mSATA SSD | 1TB HDD | 500GB HDD
Offline
It seems that the Hard Drive is hard0connected to the Motherboard; but upon googling for "acer 5100 ide controller" I found HUNDREDS of results of people stating almost identical problems to myself:
<< It stopped showing up altogether a month or so ago. I've done the registry edit suggested for this drive, as well as opened up the computer to check the connection to the motherboard. The drive light comes on when a disc is inserted or when the eject button is pushed, but nothing registers in Windows. In addition, the drive doesn't show up in BIOS setup. Any ideas? >>
Oh, and this Particularly accurate description of my symptoms
This is bad. I simply haven't the money to buy a new laptop; and I can't sell this one knowing that the recipient won't be able to actually use it. Any ideas, please?
ArchLinux | x86_64 | linux-ck-ivybridge
ThinkPad X230 | 12.5" | i5-3320M (2.5GHz) | HD 4000 | 16GB (1600MHz) | 256GB mSATA SSD | 2TB HDD
ThinkPad T430 | 14.1" | i7-3520M (2.9GHz) | GF108M (NVS 5400M) | 16GB (1600MHz) | 256GB mSATA SSD | 1TB HDD | 500GB HDD
Offline
Well, in the end, I've managed to almost completely solve the problems that I've been experiencing. My solution: a complete re-assembly of my laptop.
I got terribly bored, disassembled every component held in with cross/flat-head screws, thoroughly cleaned, replaced all thermal paste, and meticulously (and tightly) assembled everything. I now get the error at most once a month. (I did this at Christmas).
I no longer have any doubts in my mind that this is a hardware issue, as I have been able to replicate the issue on several versions (old and new) of several Linux distributions (Debian, Ubuntu, DSL, Fedora), and on Windows (XP and 98). But I'm a happy bunny now.
I really do appreciate all the help and discussion, though, as it did help me from getting *really* stressed. Cheers, guys. ^_^
ArchLinux | x86_64 | linux-ck-ivybridge
ThinkPad X230 | 12.5" | i5-3320M (2.5GHz) | HD 4000 | 16GB (1600MHz) | 256GB mSATA SSD | 2TB HDD
ThinkPad T430 | 14.1" | i7-3520M (2.9GHz) | GF108M (NVS 5400M) | 16GB (1600MHz) | 256GB mSATA SSD | 1TB HDD | 500GB HDD
Offline
Ah, some absolute closure.
The laptop 'died'. As in, will not boot from any manner of connected device (IDE/USB/etc.).
New laptop after results day, I hope.
ArchLinux | x86_64 | linux-ck-ivybridge
ThinkPad X230 | 12.5" | i5-3320M (2.5GHz) | HD 4000 | 16GB (1600MHz) | 256GB mSATA SSD | 2TB HDD
ThinkPad T430 | 14.1" | i7-3520M (2.9GHz) | GF108M (NVS 5400M) | 16GB (1600MHz) | 256GB mSATA SSD | 1TB HDD | 500GB HDD
Offline