[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problem: kernel 2.4.23 - rootfs mounted read-only



On Fri, 2 Jan 2004 12:16:35 +0100, 
Lukas Ruf <ruf@rawip.org> wrote in message 
<20040102111635.GA8267@tik.ee.ethz.ch>:

> Dear all,
> 
> when returning back to work after the Xmas-break, my root-file system
> was mounted read-only.  However, I have no idea why this happened --
> and problems fixing it.  Any help would be greatly appreciated!
> 
> Checking my logs, I found:
> 
> Dec 25 02:54:00 [kernel]
> Dec 25 02:54:00 [kernel] hda: (__ide_dma_test_irq) called while not
> waiting Dec 25 02:54:00 [kernel] hda: dma_timer_expiry: dma status ==
> 0x20 Dec 25 02:54:00 [kernel] hda: drive not ready for command
> Dec 25 02:54:00 [kernel] hda: status timeout: status=0xd0 { Busy }
> Dec 25 02:54:00 [kernel] hda: timeout waiting for DMA
> Dec 25 02:54:01 [kernel] ide0: reset: success
> Dec 25 02:54:03 [kernel] blk: queue c02cfde0, I/O limit 4095Mb (mask
> 0xffffffff)
> 
> and
> 
> Dec 26 02:50:00 [kernel] hda: dma_timer_expiry: dma status == 0x20
> Dec 26 02:50:00 [kernel] ide0: reset: success
> 
> and
> 
> Dec 30 07:35:52 [kernel] hda: dma_intr: status=0x51 { DriveReady
> SeekComplete Error } Dec 30 07:35:52 [kernel] EXT3-fs error (device
> ide0(3,2)): ext3_get_inode_loc: unable to read inode block -
> inode=972554, block=1966176 Dec 30 07:35:52 [kernel] Remounting
> filesystem read-only Dec 30 07:35:52 [kernel] EXT3-fs error (device
> ide0(3,2)) in start_transaction: Journal has aborted
> 
> Trying to remount the rootfs rw yields
> 
> # mount -o remount,rw /
> mount: block device /dev/hda2 is write-protected, mounting read-only
> 
> # uname -a
> Linux komsys-pc-ruf 2.4.23 #1 Tue Dec 2 17:34:37 CET 2003 i686
> GNU/Linux
> # uptime
>  12:10:54 up 30 days, 17:58,  8 users,  load average: 0.71, 1.37, 1.50
> 
> Does anybody know whether this means: the disk is about to die....

..yup.  Get a new one.  You don't wanna write to your old disk at all,
until you have your data safely transferred to your new disk.  
For the transfer, setup a new fresh debian or use a knoppix, say
http://damnsmalllinux.org/ ,  is pretty good.  Expect some fishing in
the /lost+found tree.

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.



Reply to: