LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 08-18-2004, 08:58 PM   #1
mr_a_ali
Member
 
Registered: Aug 2004
Location: USA
Distribution: SuSE 9.1 (Personal)
Posts: 49

Rep: Reputation: 15
Unhappy main hard drive won't boot...read-only mode?


Hi,

Well my poor computer won't startup now. What happens during the startup is it says

fsck failed. Please repair manually and reboot. The root file system is currently mounted read-only. To remount it read-write do:

bash# mount -n -o remount,rw/


It prompts me to login as root, which I do, and the shell is called "none" instead of "bash". I try the above command, but then it just doesn't work and gives me usage info for "mount". But I can't figure out what I'm supposed to type to get it into read-write mode again. Can someone help please?

I think that my hard drive is /dev/hda2 (?)

Thank you
 
Old 08-19-2004, 03:39 AM   #2
nukkel
Member
 
Registered: Mar 2003
Location: Belgium
Distribution: Hardened gentoo
Posts: 323

Rep: Reputation: 30
It's always dangerous to run a fils system check/repair (fsck) on a mounted filesystem. The problem here is you can't unmount the root (/) filesystem...

So the best way to repair your / file system, is to boot from the SuSE CD/DVD and then choose "rescue system" (at least this worked back in the SuSE 7.3 days). It will not touch your hard drive but boots into a small system with shell, all directly from the CD.

The advantage is that now the root (/) file system on the hard drive isn't even mounted ('cos the system booted from CD) so you can safely do "fsck /dev/hda2" or wherever your / resides. If you're not sure you can mount it on /mnt, using "mount /dev/hda2 /mnt" then see inside /mnt if it is the right partition, then "umount /mnt" and then do the fsck thing.
Then fsck should be able to repair the partition, unless it is really really screwed up.
Then just type reboot and eject the CD.

Hope this helps!
 
Old 08-19-2004, 08:24 AM   #3
mr_a_ali
Member
 
Registered: Aug 2004
Location: USA
Distribution: SuSE 9.1 (Personal)
Posts: 49

Original Poster
Rep: Reputation: 15
I tried this, and I think the problem here is "reparing manually"

when I do fsck /dev/hda2 , it says

fsck.reiserfs /dev/hda2 failed (status 0x10). Run manually!

This is all while I'm in Rescue Mode running off the SuSE CD.
 
Old 08-19-2004, 08:42 AM   #4
nukkel
Member
 
Registered: Mar 2003
Location: Belgium
Distribution: Hardened gentoo
Posts: 323

Rep: Reputation: 30
OK, it looks like a ReiserFS file system. Try the following then (still in rescue mode):

1. Do a "reiserfsck --check /dev/hda2"

2. If it says something about "fixable corruptions", do "reiserfsck --fix-fixable /dev/hda2"
OR
If it complains about "fatal corruptions", do "reiserfsck --rebuild-tree /dev/hda2". In this case it's best to make a BACKUP first because it means the partition is seriously damaged...

Good luck!
 
Old 08-19-2004, 08:54 AM   #5
mr_a_ali
Member
 
Registered: Aug 2004
Location: USA
Distribution: SuSE 9.1 (Personal)
Posts: 49

Original Poster
Rep: Reputation: 15
The damage is extensive, apparently, and I have no idea what I did to cause it in the first place... 4 days on linux and I already screwed up my first install

Oh well, reinstallation it is. Thanks for the help tho.
 
Old 08-19-2004, 09:02 AM   #6
nukkel
Member
 
Registered: Mar 2003
Location: Belgium
Distribution: Hardened gentoo
Posts: 323

Rep: Reputation: 30
No problem. Strange though, ReiserFS is a pretty solid thingy... If you get this again after reinstalling, it could be helpful to drop a post in the laptop forum... See I once knew someone with a laptop that kept screwing up his hard drive; turned out, when the laptop goes into suspend the BIOS saves all RAM contents to disk, and his BIOS apparently wrote it right onto his linux partition !!! like it didn't know it couldn't use that disk area.

Just to say, if the problem persists, it could be laptop-specific...

good luck with it anyway.
 
Old 09-29-2004, 02:10 AM   #7
linx win
Member
 
Registered: Jan 2004
Posts: 390

Rep: Reputation: 31
nukkel

I got a simillar message but for another reason. I have my boot system in the mbr of hda while my SuSE 9.1 system is in hdb8. I removed hda from my system and hdb became hda. I installed another copy of SuSE on hda9 and added the previous copy to its boot list because I did not know how to do that in the mbr. Now when I start SuSE (hda8) I get :

fsck failed. Please repair manually and reboot. The root file system is currently mounted read-only. To remount it read-write do:

bash# mount -n -o remount,rw/

I did as you mentioned above:

"reiserfsck --check /dev/hda8"

and do "reiserfsck --fix-fixable /dev/hda8"

and both told me no corruptions. Can you help me?

Last edited by linx win; 09-29-2004 at 02:53 AM.
 
Old 09-29-2004, 02:58 AM   #8
nukkel
Member
 
Registered: Mar 2003
Location: Belgium
Distribution: Hardened gentoo
Posts: 323

Rep: Reputation: 30
Hi,

sounds wierd,
have you tried booting the newer system (on hda9) and check the older system from there?

It can also be, the older SuSE still thinks it has to boot from hdb8; in that case, make sure that, in the LILO boot config, the "root=..." line for the old SuSE is set to /dev/hda8.
 
Old 09-29-2004, 09:03 AM   #9
linx win
Member
 
Registered: Jan 2004
Posts: 390

Rep: Reputation: 31
Thanks for reply.
Yes, I am able to boot the new system on hda9, but what should I do to check the older system?
This is what I have in the grub file:
kernel (hd0,7) /boot/valinuz root=/dev/hda8 ......
initrd (h0,7)/boot/initrd

I have started the resecue mode in the older system and installed a new kernel hoping that it will solve the problem by making a new initrd and valinuz but no success. What should I do? Any idea?
 
Old 09-29-2004, 02:14 PM   #10
ij dakar
LQ Newbie
 
Registered: Sep 2004
Location: Santo Domingo, Dominican Republic
Distribution: Slackware 10
Posts: 8

Rep: Reputation: 0
I have a problem just like those above, just that i know what could cause it . In my PC i have slack running on hdb2 with the ext2 fs, and i made 3 accounts, me and my two brothers beside the root. Me and the bigger are the only ones that knows the root pass and know how to power down from an user session(that's using th "su" command), but my smaller bro doesn't knows the root pass, so he cant power down, so he just turns off the PC without unmounting the HDs, and i know linux is very sensitive about that(it runs a forced check every time this happens).So, now it seems to happen the same thing as mr_a_li.

I would like to know how to use the fsck to check the dev( i have the rescue disk so i can do it from there) and how to let my bro's session power down without asking the root password.
 
Old 10-02-2004, 07:53 AM   #11
linx win
Member
 
Registered: Jan 2004
Posts: 390

Rep: Reputation: 31
I managed to solve the problem by making my hard disk to boot as slave (hdb). Thanks.
 
Old 10-02-2004, 09:59 AM   #12
nukkel
Member
 
Registered: Mar 2003
Location: Belgium
Distribution: Hardened gentoo
Posts: 323

Rep: Reputation: 30
very strange...

well, what matters is it works
 
Old 10-02-2004, 06:18 PM   #13
ij dakar
LQ Newbie
 
Registered: Sep 2004
Location: Santo Domingo, Dominican Republic
Distribution: Slackware 10
Posts: 8

Rep: Reputation: 0
Forget about the post above

I found out what was the problem, i coul only solve it by reinstalling my slack again. Thanks for the effort
 
Old 04-05-2005, 11:16 PM   #14
i_newton
LQ Newbie
 
Registered: Apr 2005
Distribution: Suse 9.1 and CentOS4.0
Posts: 1

Rep: Reputation: 0
Talking

I had the same problem. I found the fix for my situation. It started when I installed a new slave drive on my system. There were entries in the /etc/fstab file that were still referencing partitions on the old drive. So, every time the system tried to process the "non-existant" partitions, the result would be the error:

fsck failed. Please repair manually and reboot. The root file system is currently mounted read-only. To remount it read-write do:

bash# mount -n -o remount,rw/




I then edited the fstab file to comment out the device missing partition entries and I was basck in business! My system would once again boot normally

Hope this helps someone.
 
Old 04-23-2005, 07:03 AM   #15
FeathersMc
LQ Newbie
 
Registered: Dec 2004
Location: Sydney
Distribution: Suse
Posts: 12

Rep: Reputation: 0
Thank you, Thank you people. I just spent a frustrating couple of hours unable to boot, just because I played around with the partition table (*slaps self).

This thread got me going again (especially the bit about editing out the missing partition).
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Read only hard drive causes hang at boot Chrontius Debian 6 08-03-2005 09:38 AM
DMA Mode of Hard Drive Ace2005 Linux - Hardware 6 07-21-2005 07:23 AM
My hard drive seems to be read-only hominy Linux - General 15 07-01-2005 08:42 AM
EZ-Drive Hard Drive -- Cannot Read Contents redhatman Linux - Newbie 3 09-02-2004 06:37 PM
expand main partition to another hard drive? halo14 Red Hat 3 08-09-2004 04:54 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 12:26 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration