[NTLUG:Discuss] Fedora Core system Read Only

Stuart Johnston saj at thecommune.net
Thu Jan 25 15:09:03 CST 2007


You might try disabling the journal:

tune2fs -O ^has_journal /dev/hda2

Terry Henderson wrote:
> It says it is mounted rw in the output of command "mount" but you
> still cannot write to the filesystem., and you cannot force remount as
> read-write [mount / -o remount,rw]
>   See captured info below:
> =======================================
> Script started on Thu 25 Jan 2007 09:16:42 AM CST
> Filesystem           1K-blocks      Used Available Use% Mounted on
> /dev/hda2             19251804   7624620  10649228  42% /
> /dev/hda1               101086     20180     75687  22% /boot
> none                    127992         0    127992   0% /dev/shm
> /dev/hdb1             19541504   4002080  15539424  21% /mnt/oldComputer
> [root at localhost root]# lesscate  /etc/fstab
> LABEL=/                 /                       ext3    defaults        1 1
> LABEL=/boot             /boot                   ext3    defaults        1 2
> none                    /dev/pts                devpts  gid=5,mode=620  0 0
> none                    /proc                   proc    defaults        0 0
> none                    /dev/shm                tmpfs   defaults        0 0
> /dev/hda3               swap                    swap    defaults        0 0
> /dev/hdb1               /mnt/oldComputer        vfat    rw,defaults     0 0
> /dev/fd0                /mnt/floppy             auto    noauto,owner,kudzu 0 0
> /dev/sda1               /mnt/memstick           auto    noauto,user     0 0
> /dev/cdrom              /mnt/cdrom              udf,iso9660
> noauto,owner,kudzu,ro 0 0
> ===========================================
> Part of dmesg:
> ===========================================
> 
> Script started on Thu 25 Jan 2007 09:24:07 AM CST
> eth0: KTI ET32P2 found at 0xd000, IRQ 10, 00:40:F6:14:94:79.
> journal_bmap_R9c46d717: journal block not found at offset 1036 on ide0(3,2)
> Aborting journal on device ide0(3,2).
> ext3_abort called.
> EXT3-fs abort (device ide0(3,2)): ext3_journal_start: Detected aborted journal
> Remounting filesystem read-only
> EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted
> EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted
> parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
> parport0: irq 7 detected
> parport0: Printer, EPSON Stylus C84
> lp0: using parport0 (polling).
> lp0: console ready
> EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted
> EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted
> EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted
> Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
> SCSI device sda: 990865 512-byte hdwr sectors (507 MB)
> sda: Write Protect is off
>  sda: sda1
> [root at localhost root]#
> Script done on Thu 25 Jan 2007 09:24:38 AM CST
> 
> ========================================
> 
> On 1/24/07, Terry Henderson <trryhend at gmail.com> wrote:
>> On 1/24/07, Wayne Walker <wwalker at bybent.com> wrote:
>>> mount -o remount,rw /
>>>
>> Yes, I'm wondering why I didn't try that, but going back over there
>> tomorrow, will see what I can do.  But, I'm really curious about why
>> it's happening in the first place.
>>
>>> On Wed, Jan 24, 2007 at 01:35:42PM -0600, Terry Henderson wrote:
>>>> A friend's computer has Core1 and had filesystem errors this morning.  He ran:
>>>>    fsck -y /dev/hda2
>>>> and seemed to have fixed it, BUT:  Now it mounts the whole filesystem
>>>> read-only and so it's impossible to do anything,much at all with it.
>>>> I went over to look at it, (didn't have much time there, but):
>>>> I found that I could mount my thunbdrive rw, so I did, and quickly
>>>> captured some info that might give us some clues:
>>>> ==============================================
>>>> Filesystem           1K-blocks      Used Available Use% Mounted on
>>>> /dev/hda2             19251804   7624604  10649244  42% /
>>>> /dev/hda1               101086     20180     75687  22% /boot
>>>> none                    127992         0    127992   0% /dev/shm
>>>> /dev/hdb1             19541504   4002080  15539424  21% /mnt/oldComputer
>>>>
>>>> Disk /dev/sda: 507 MB, 507322880 bytes
>>>> 16 heads, 63 sectors/track, 983 cylinders
>>>> Units = cylinders of 1008 * 512 = 516096 bytes
>>>>
>>>>    Device Boot    Start       End    Blocks   Id  System
>>>> /dev/sda1             1       983    495313+   6  FAT16
>>>>
>>>> Disk /dev/hda: 20.4 GB, 20404101120 bytes
>>>> 255 heads, 63 sectors/track, 2480 cylinders
>>>> Units = cylinders of 16065 * 512 = 8225280 bytes
>>>>
>>>>    Device Boot    Start       End    Blocks   Id  System
>>>> /dev/hda1   *         1        13    104391   83  Linux
>>>> /dev/hda2            14      2448  19559137+  83  Linux
>>>> /dev/hda3          2449      2480    257040   82  Linux swap
>>>>
>>>> Disk /dev/hdb: 20.0 GB, 20020396032 bytes
>>>> 255 heads, 63 sectors/track, 2434 cylinders
>>>> Units = cylinders of 16065 * 512 = 8225280 bytes
>>>>
>>>>    Device Boot    Start       End    Blocks   Id  System
>>>> /dev/hdb1   *         1      2434  19551073+   c  Win95 FAT32 (LBA)
>>>> total 0
>>>> [root at localhost root]# ls -l /var/lock/subystem
>>>> -rw-r--r--  1 root root 0 Jan 24 10:24 apmd
>>>> -rw-r--r--  1 root root 0 Jan 24 10:24 iptables
>>>> -rw-r--r--  1 root root 0 Jan 24 10:24 kudzu
>>>> -rw-r--r--  1 root root 0 Jan 24 10:24 netfs
>>>> -rw-r--r--  1 root root 0 Jan 24 10:24 network
>>>> -rw-r--r--  1 root root 0 Jan 24 10:24 nfslock
>>>> -rw-r--r--  1 root root 0 Jan 24 10:24 portmap
>>>> -rw-r--r--  1 root root 0 Jan 24 10:24 random
>>>> -rw-------  1 root root 0 Jan 24 10:24 syslog
>>>> [root at localhost root]# mount
>>>> /dev/hda2 on / type ext3 (rw)
>>>> none on /proc type proc (rw)
>>>> none on /dev/pts type devpts (rw,gid=5,mode=620)
>>>> usbdevfs on /proc/bus/usb type usbdevfs (rw)
>>>> /dev/hda1 on /boot type ext3 (rw)
>>>> none on /dev/shm type tmpfs (rw)
>>>> /dev/hdb1 on /mnt/oldComputer type vfat (rw)
>>>> Script started on Wed 24 Jan 2007 10:46:33 AM CST
>>>> [root at localhost root]# touch testfile
>>>> touch: cannot touch `testfile': Read-only file system
>>>> [root at localhost root]# touch /home/dell/testfile
>>>> touch: cannot touch `/home/dell/testfile': Read-only file system
>>>> =========================================
>>>> Also;  I saw something during boot up that indicated that ext3
>>>> journaling was failing, or... well, I think that may be because the
>>>> filesystem is being mounted read-only.  So, does anyone have a clue as
>>>> to what may have happened, and / or, what to do about it?
>>>>
>>>> _______________________________________________
>>>> http://www.ntlug.org/mailman/listinfo/discuss
>>> --
>>>
>>> Wayne Walker
>>>
>>> www.unwiredbuyer.com - when you just can't be by the computer
>>>
>>> wwalker at bybent.com                    Do you use Linux?!
>>> http://www.bybent.com                 Get Counted!  http://counter.li.org/
>>> Perl - http://www.perl.org/           Perl User Groups - http://www.pm.org/
>>> Jabber:  wwalker at jabber.gnumber.com   AIM:     lwwalkerbybent
>>> IRC:     wwalker on freenode.net
>>>
>>
>> --
>> Registered Linux User 188099
>>                   <><
>>
> 
> 



More information about the Discuss mailing list