From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ookhoi Subject: Re: Read only rootfs after reiserfsck Date: Wed, 12 Nov 2003 12:42:56 +0100 Message-ID: <20031112114256.GS21370@favonius> References: <000001c3a707$58db90e0$7dea1d97@delta> <3FAEA7CA.4000301@gmx.net> <011b01c3a89d$28e03520$0100007f@delta> <3FB19C6E.7030109@gmx.net> Reply-To: ookhoi@humilis.net Mime-Version: 1.0 Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com Content-Disposition: inline In-Reply-To: <3FB19C6E.7030109@gmx.net> List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Carl-Daniel Hailfinger Cc: Paolo Azzaroli , ReiserFS List Carl-Daniel Hailfinger wrote (ao): > Can anyone else shed some light on the issue? What is in /etc/fstab, and what does 'fdisk -l /dev/hda' say? > Paolo Azzaroli wrote: > > Dear Sir:, I apreciated Your suggestion, I tried it, but it doesn't > > fix my problem. > > Anyway, many thank for your kindly attention > > Paolo Azzaroli > > > > ----- Original Message ----- > > From: "Carl-Daniel Hailfinger" > > To: "Paolo Azzaroli" > > Cc: > > Sent: Sunday, November 09, 2003 9:47 PM > > Subject: Re: Read only rootfs after reiserfsck > > > > > > > >> Paolo Azzaroli wrote: > >> > >>> Dear Sir, My Linux box has a distro SuSE 8.1, and its HD has 1 swap > >>> partition, 3 reiserfs partitions, apart from a NTFS partition (where > >>> resides Win2K). > >>> Some days ago the Linux box filesystem had triubles, maybe because > >>> of not correct shutdown. > >>> After then I repaired the fs (reiserfsck --check etc . . . ); the > >>> check operation reported successfull. > >>> But when booting the Linux box, the linux root partitions is > >>> "read-only"; the contents of /etc/mtab and /proc/mounts are > >>> different. I can mount the root partition (mount -n -o remount,rw > >>> /dev/hda3), but attempt to mount/umount other partitions are > >>> frustated by messages as "already mounted or busy"/ "not mounted". > >> > >> Delete all lines in /etc/mtab which reference filesystems other than > >> your root partition. That should fix it.