LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-14-2005, 12:28 PM   #1
Sushy
Member
 
Registered: Sep 2005
Distribution: FreeBSD
Posts: 84

Rep: Reputation: 15
Problems with root filesystem


Hi!

I have Samba File Server with RAID 1 mirroring.
The problem is that after booting bare.i root=/dev/hda1 noinitrd ro
from my Slackware 10.2 Install CD
I can`t boot up my linux anymore.

Everything stops when booting root file system,
simply it can`t boot root file system anymore
I can only log in as single user as root with read-only priviledges to restore the file system, but how?
When booting root file system something is corrupted, but what?


I think it is connected with md0 device (mirroring)...
But why it happens so, because I only run bare.i root=/dev/hda1 noinitrd ro,
so after that this problem appeared

Why, what should I do now?!
Any suggestions?

Thank you.
 
Old 10-14-2005, 10:44 PM   #2
routers
Member
 
Registered: Aug 2005
Location: Malaysia - KULMY / CNXTH
Distribution: Slackware, Fedora, FreeBSD, Sun O/S 5.10, CentOS
Posts: 787
Blog Entries: 6

Rep: Reputation: 75
if u can login single user then edit /etc/fstab comment the line md0
save it then reboot system , should work this way

after that troubleshoot again what cos ur problem

bare.i root=/dev/hda1 noinitrd rw <- see this

Last edited by routers; 10-14-2005 at 10:48 PM.
 
Old 10-15-2005, 06:09 AM   #3
Sushy
Member
 
Registered: Sep 2005
Distribution: FreeBSD
Posts: 84

Original Poster
Rep: Reputation: 15
Quote:
Originally posted by routers
if u can login single user then edit /etc/fstab comment the line md0
save it then reboot system , should work this way

after that troubleshoot again what cos ur problem

bare.i root=/dev/hda1 noinitrd rw <- see this

How should I comment, did you think with # or ;
?
What is the main goal doing this way?
 
Old 10-15-2005, 06:17 AM   #4
routers
Member
 
Registered: Aug 2005
Location: Malaysia - KULMY / CNXTH
Distribution: Slackware, Fedora, FreeBSD, Sun O/S 5.10, CentOS
Posts: 787
Blog Entries: 6

Rep: Reputation: 75
hehe

if said comment i always figure out it is #

bare.i root=/dev/hda1 noinitrd ro <- u do this mean u Read Only

bare.i root=/dev/hda1 noinitrd rw <- do this mean Read Write

then u cannn edit the fstab file


comment / close # the line where is the posibility have a problem for system to detect via startup
need to close otherwise system stillllllllllllllllllll want to read that

so give a try close the line md0 which u expected got some problem then once u can login there then u can do trouble shooting to what is the real matter

give a try ,... dont gip up
 
Old 10-15-2005, 06:44 AM   #5
Sushy
Member
 
Registered: Sep 2005
Distribution: FreeBSD
Posts: 84

Original Poster
Rep: Reputation: 15
Quote:
Originally posted by routers
hehe

if said comment i always figure out it is #

bare.i root=/dev/hda1 noinitrd ro <- u do this mean u Read Only

bare.i root=/dev/hda1 noinitrd rw <- do this mean Read Write

then u cannn edit the fstab file


comment / close # the line where is the posibility have a problem for system to detect via startup
need to close otherwise system stillllllllllllllllllll want to read that

so give a try close the line md0 which u expected got some problem then once u can login there then u can do trouble shooting to what is the real matter

give a try ,... dont gip up

I think I did`n explain my problem quite well.
I can boot up Linux but till root file system!!
LILO is booting the system till root file system.
It stops with telling me that something is corrupted, that there is need to run --rebuild-tree
After that I can log in as root@(none) single user
I can edit any file so I have rw
Most important is that if I take a look in /proc/mdstat file - md0 2 out of 2 mirrors are running, also the third partotions which are md1
So I think because of running bare.i root=/dev/hda1 noinitrd ro there is some missmach in md0 and it affects the root file system.

But I don`t understand why?
So it means I can run no more bare.i root=/dev/hda1 noinitrd ro in the future because it affects the file system?

I would like to understand why it happened so, only beacause of running bare.i root=/dev/hda1 noinitrd ro
So how should I manage mirroring in future, most of all I`m interested in monitoring my mirrors so that if there is some error I would know it immediately with some promt or sound
 
  


Reply



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 Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
root filesystem ewt3y Linux - General 7 08-16-2005 01:12 AM
problems with root filesystem ramzai Linux - Newbie 2 02-11-2005 01:04 PM
Encrypted Root Filesystem HOWTO and /dev filesystem tmillard Linux From Scratch 0 10-18-2004 03:58 PM
Problems with console login on newly created root filesystem (for PXEboot) holandes777 Linux - General 1 08-05-2004 05:11 PM
What *has* to be in the root filesystem? fedetxf Linux - General 2 01-05-2004 07:21 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:39 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