Filsystemet blir plötsligt skrivskyddat

[wiberg83]

Fick ny hårddisk från Acer, efter problem med förra. Installerade Ubuntu och lade in lite program och sånt. Allt verkade fungera.
Men så plötsligt går det inte starta program. Startar om datorn. När det sedan händer igen så har jag som tur är redan terminalen uppe. Testar att kopiera en fil och får felet att filsystemet endast är läsbart.
Detta kunde hända förut, innan jag bytte hårddisk. Trodde det var disken som var problemet, för vid uppstart fick jag felmeddeladet ERROR FIXED DISK #.
Nu får jag inte det längre, men av någon anledning så blir disken skrivskyddad spontant. Den fungerade flera timmar efter installation, sen inte ens 5 minuter efter varje omstart, om jag ens kommer in i Gnome.
Vet någon vad som kan vara felet? Är det någon komponent i anslutning till hårddisken som är trasig eller vad är det?
Datorn är en Acer Aspire 5102 WLMi, med ATI Radeon Xpress1100, 1024 MB DDR RAM, numera en Western Digital hårddisk.

[zoombywoof]

Låter skumt, låter ju som att systemet inte gillar din hårddisk (oavsett sort...) Enda sättet att kunna säga nått mer är att få lite info från loggarna. Eftersom problemet inte verkar dyka upp förrän efter en liten stund, kan det ha loggats grejer som relaterar till detta.

Kolla in /var/log/messages, /var/log/syslog och se om du har några entries som kan härledas till hårddisken. Kommandot dmesg i ett terminalfönster direkt efter boot kan vara bra också.

Ett annat alternativ är att starta datorn i recovery mode se om samma sak händer, men då bör inte GUI.et startas utan du hänvisas till kommandoprompt.

GL

/zw

[wiberg83]

Så här såg det ut när jag körde dmesg när det blev fel igen: (Det yttrar sig genom att det inte går att spara filer, så filsystemet är alltså helt plötsligt read-only.)

Kod: Markera allt

[  584.252000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.252000] ide: failed opcode was: unknown
[  584.252000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.252000] ide: failed opcode was: unknown
[  584.252000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.252000] ide: failed opcode was: unknown
[  584.252000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.252000] ide: failed opcode was: unknown
[  584.252000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.252000] ide: failed opcode was: unknown
[  584.252000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.252000] ide: failed opcode was: unknown
[  584.252000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.252000] ide: failed opcode was: unknown
[  584.252000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.252000] ide: failed opcode was: unknown
[  584.252000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.252000] ide: failed opcode was: unknown
[  584.256000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.256000] ide: failed opcode was: unknown
[  584.256000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.256000] ide: failed opcode was: unknown
[  584.256000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.256000] ide: failed opcode was: unknown
[  584.256000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.256000] ide: failed opcode was: unknown
[  584.260000] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[  584.260000] hda: dma_intr: error=0x44 { DriveStatusError UncorrectableError }, LBAsect=70644886356567, high=4210763, low=5980759, sector=190513687
[  584.260000] ide: failed opcode was: unknown
[  584.260000] end_request: I/O error, dev hda, sector 190513687
[  584.260000] Buffer I/O error on device hda1, logical block 23814203
[  584.260000] lost page write due to I/O error on hda1
[  584.260000] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[  584.260000] hda: dma_intr: error=0x44 { DriveStatusError UncorrectableError }, LBAsect=70644886356575, high=4210763, low=5980767, sector=190513695
[  584.260000] ide: failed opcode was: unknown
[  584.260000] end_request: I/O error, dev hda, sector 190513695
[  584.260000] Buffer I/O error on device hda1, logical block 23814204
[  584.260000] lost page write due to I/O error on hda1
[  584.260000] Aborting journal on device hda1.
[  584.260000] ext3_abort called.
[  584.260000] EXT3-fs error (device hda1): ext3_journal_start_sb: Detected aborted journal
[  584.260000] Remounting filesystem read-only
[  584.260000] EXT3-fs error (device hda1) in ext3_ordered_commit_write: IO failure
[  584.260000] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[  584.260000] hda: dma_intr: error=0x44 { DriveStatusError UncorrectableError }, LBAsect=70644920243311, high=4210765, low=6313071, sector=224400495
[  584.260000] ide: failed opcode was: unknown
[  584.260000] end_request: I/O error, dev hda, sector 224400495
[  584.260000] Buffer I/O error on device hda1, logical block 28050054
[  584.260000] lost page write due to I/O error on hda1
[  584.260000] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[  584.260000] hda: dma_intr: error=0x44 { DriveStatusError UncorrectableError }, LBAsect=70644921419767, high=4210765, low=7489527, sector=225593271
[  584.260000] ide: failed opcode was: unknown
[  584.260000] end_request: I/O error, dev hda, sector 225593271
[  584.260000] Buffer I/O error on device hda1, logical block 28199151
[  584.260000] lost page write due to I/O error on hda1
[  584.260000] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[  584.260000] hda: dma_intr: error=0x44 { DriveStatusError UncorrectableError }, LBAsect=70644921855719, high=4210765, low=7925479, sector=226029223
[  584.260000] ide: failed opcode was: unknown
[  584.260000] end_request: I/O error, dev hda, sector 226029223
[  584.260000] Buffer I/O error on device hda1, logical block 28253645
[  584.260000] lost page write due to I/O error on hda1
[  584.260000] __journal_remove_journal_head: freeing b_frozen_data
[  584.264000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.264000] ide: failed opcode was: unknown
[  584.264000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.264000] ide: failed opcode was: unknown
[  584.264000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.264000] ide: failed opcode was: unknown
[  584.264000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.264000] ide: failed opcode was: unknown
[  584.272000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.272000] ide: failed opcode was: unknown
[  584.272000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.272000] ide: failed opcode was: unknown
[  584.272000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.272000] ide: failed opcode was: unknown
[  584.272000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.272000] ide: failed opcode was: unknown
[  584.276000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.276000] ide: failed opcode was: unknown
[  584.276000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.276000] ide: failed opcode was: unknown
[  584.276000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.276000] ide: failed opcode was: unknown
[  584.276000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.276000] ide: failed opcode was: unknown
[  584.276000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.276000] ide: failed opcode was: unknown
[  584.276000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.276000] ide: failed opcode was: unknown
[  584.276000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.276000] ide: failed opcode was: unknown
[  584.276000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.276000] ide: failed opcode was: unknown
[  584.276000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.276000] ide: failed opcode was: unknown
[  584.276000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.276000] ide: failed opcode was: unknown
[  584.280000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.280000] ide: failed opcode was: unknown
[  584.280000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.280000] ide: failed opcode was: unknown
[  584.280000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.280000] ide: failed opcode was: unknown
[  584.280000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.280000] ide: failed opcode was: unknown
[  584.284000] hdb: status error: status=0x50 { DriveReady SeekComplete }
[  584.284000] ide: failed opcode was: unknown

Ska man ändra i fstab så att under options så tar man bort att hårddisken ska monteras som read-only vid fel? Kan det vara någon hårdvarukomponent mellan HDDn och moderkortet? Minns att Acer bytte ut moderkortet första gången jag skickade dit den...inte tittade efter vad som orsakade hårddiskfelet iaf...
Får jag inte bot på detta snart så ska jag skriva ett tredje argt brev till Acer och kräva en ny dator, för det känns som ett typiskt måndagsexemplar. Har stått ut med dem i över ett år nu så jag har iaf haft tålamod.

[Lars]

Du kan kolla med Smartmontools om det är något fel på hårddisken.

[zoombywoof]

din hda disk mår inte bra verkar det som, IO error på flera olika sektorer. Dax att skicka tillbaka kanske ?

[wiberg83]

Det är det jag har gjort. Senast så fick jag Acer att gå med på att jag enbart skulle skicka in hårddisken och så fick jag en helt ny. (Skrev ner serienumret på den gamla för att vara säker, men jag fick till och med en av ett annat märke så de bytte iaf.)
Problemen som uppstår är dock desamma. Borde då inte rimligtvis vara fel på någon annan komponent, men som i sin tur orsakar fel på hårddisken?

[Bowmore]

Tänkte först att du har nåt termiskt problem, kan ju vara nästan vad som helst då.

Men kan kanske vara någon inställning i bios som spökar.
Du kan ju börja med att se om dessa två kommando kan ge nån ledtråd

Kod: Markera allt

sudo hdparm /dev/sda
sudo hdparm -i /dev/sda

Nu är inte jag nån hejare på alla bios-inställningar men det finns säkert andra här som kan hjälpa till.

[radiobuzzer]

Hej,

I cannot speak Swedish, so I haven't fully understood the post, BUT it seems that we are having EXACTLY the same problem, on exactly the same computer, and at the same period.

This is really weird. So far I had believed that this is a hardware failure of either my hard disk, or the controller/motherboard. But if you are having the same problems, something else might be around ? Eg something relative to the controller drivers? I don't know what to say.

I am using ACER Aspire 5102 WLMI, AMD Turion 64x2 (1.6 Ghz), with a 100GB 5400rpm PATA HDD.

I have already submitted my problems to the English speaking forum.

Kod: Markera allt

 sudo hdparm -i /dev/hda

/dev/hda:

 Model=ST9100824A, FwRev=3.06, SerialNo=5PL1TX8B
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
 BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=off
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=195371568
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4 
 DMA modes:  mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 
 AdvancedPM=yes: unknown setting WriteCache=enabled
 Drive conforms to: ATA/ATAPI-6 T13 1410D revision 2:  ATA/ATAPI-1,2,3,4,5,6

 * signifies the current active mode

[wiberg83]

I have my suspicions that it could have something to do with Ubuntu parking the drive very often when on battery power, eventually damaging the drive. I have gotten my laptop back from service, but not installed Ubuntu on it yet, since I'm waiting to see if the problem occurs anyway. But when I do, I will post here and say what happened and if I found a way around it.

[radiobuzzer]

I have my suspicions that it could have something to do with Ubuntu parking the drive very often when on battery power, eventually damaging the drive.

That may be an explanation. My problem occured one month after I started using the laptop every day in train, on the way to work; therefore being based on battery and suspend mode.

I have gotten my laptop back from service, but not installed Ubuntu on it yet, since I'm waiting to see if the problem occurs anyway. But when I do, I will post here and say what happened and if I found a way around it.

Do you have information about what the service changed on your computer? A new hard disk or something related to the motherboard?

[wiberg83]

The last service included
- a replaced motherboard,
- new hard drive (hitachi),
- BIOS re-flash,
- and something I can't remember right now...

The problem has occured earlier, and sometimes only an hour or so after installing Ubuntu and running on DC power.

[radiobuzzer]

Oh my god. I guess that was covered by your guarrantee, cause otherwise is like buying a new laptop. Unfortunately my guarrantee has expired, so I don't know if I can do anything about it...

That's why I am trying to figure out what's wrong, so that I can try to do a cheap service myself, which will be also faster than the ACER service. Or just buy a new laptop.

On the other side it's strange that they changed both the motherboard and the hard disk, since it sounds like only one of them is enough for causing the problem. And this BIOS reflash is, I guess, a regular update...

[wiberg83]

It was covered, since they didn't manage to fix it before the warranty expired. (Not the first time I've had to send it to them.) Otherwise I hadn't sent it to Acer for repair. Hopefully this time it will work.

[radiobuzzer]

I have my suspicions that it could have something to do with Ubuntu parking the drive very often when on battery power

Ok, I was kind of sure that it is not just a software problem and something needs to be fixed. Though, if there is a software reason behind that, this is very serious and needs to be investigated. Besides, this coincidence, me and you having the same problem at the same system can be an indication for something wrong, as you suggest. If this can be mentioned to the Ubuntu bug tracking system, that would be great, since it makes sure that we won't have this problem again, either.

I would like us to summarize here technical details regarding our system, before the problem occurred. If many of the match, that would be an indication of sth wrong:

• Beginning of December, I formatted my disk and installed UbuntuStudio. This distro uses a realtime kernel, which didn't work well and it is known for stretching the devices. So I kept it only for one week, and then went back to the normal "generic" kernel.
  Middle January I bought a new power cord, since I lost the old one
  Middle December I bought a new battery, but I started intensively using it, along with suspend mode, beginning of March, while traveling in the train every day. The error occurred two weeks after that and I am really suspicious about it, since I was never proud of how the power management of ACER is handled by Ubuntu.

[wiberg83]

I think there have been bug reports on this issue, though not on the exact same system configuration we're running. Check
https://bugs.launchpad.net/ubuntu/+sour ... +bug/59695
for details. There are a number of fixes around as well apparently. I'm going to try some of them when I find one that seems suitable for my hard drive, and when I find the time to do it...