I have a 7.65 CS1000 running CPDC SIG Servers and my SS0 has crash and burned. Fortunately all my IP phone are up on SS1, but I was hoping to revive SS0 if possible. Watching SS0 bootup it goes until it asks for the root password for maint. After enetering the root password, it shows.... "(Repair Filesystem) 1 #" From this point I have no idea. Again I don't want to reload if I don't have to, which is why im here. Any help would be appreciated. Thanks
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
CPDC failed
- Thread starter motox2
- Start date
Firebird Scrambler
Systems Engineer
I've found this report that might apply?
Problem
Linux Co Res wont boot up. Or goes in reboot loop. After power fail
Answer
System fails to boot properly following a power fail. When connected to TTY it eventualy gives this message
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):
If you put in Control-D it just cames back to the same place.
Entering the root password will allow you to get to the next stage
--------------------------
(Repair filesystem) 1 #
Type in fsck then return.
(Repair filesystem) 1 # fsck
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
/: clean, 49542/524288 files, 343372/524112 blocks
e2fsck 1.39 (29-May-2006)
ext3 recovery flag is clear, but journal has data.
-------- System then responded with this ------
Run journal anyway<y>? yes
/home: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/home: 830/2097152 files (0.1% non-contiguous), 103907/2096474 blocks
e2fsck 1.39 (29-May-2006)
/opt: clean, 14301/4100544 files, 507784/4096567 blocks
.........etc etc etc ....
e2fsck 1.39 (29-May-2006)
/boot: clean, 42/24480 files, 55370/97656 blocks
(Repair filesystem) 2 # reboot -f (This will reboot the server)
--- Extra info -----
When reviewing the logs on the first boot up. The following was found
/home: ext3 recovery flag is clear, but journal has data.
/home: Run journal anyway
/home: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
Looks like on the normal boot up, the system encountered this journal problem and needed manual intervention.
Firebird Scrambler
Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer
Website = linkedin
Problem
Linux Co Res wont boot up. Or goes in reboot loop. After power fail
Answer
System fails to boot properly following a power fail. When connected to TTY it eventualy gives this message
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):
If you put in Control-D it just cames back to the same place.
Entering the root password will allow you to get to the next stage
--------------------------
(Repair filesystem) 1 #
Type in fsck then return.
(Repair filesystem) 1 # fsck
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
/: clean, 49542/524288 files, 343372/524112 blocks
e2fsck 1.39 (29-May-2006)
ext3 recovery flag is clear, but journal has data.
-------- System then responded with this ------
Run journal anyway<y>? yes
/home: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/home: 830/2097152 files (0.1% non-contiguous), 103907/2096474 blocks
e2fsck 1.39 (29-May-2006)
/opt: clean, 14301/4100544 files, 507784/4096567 blocks
.........etc etc etc ....
e2fsck 1.39 (29-May-2006)
/boot: clean, 42/24480 files, 55370/97656 blocks
(Repair filesystem) 2 # reboot -f (This will reboot the server)
--- Extra info -----
When reviewing the logs on the first boot up. The following was found
/home: ext3 recovery flag is clear, but journal has data.
/home: Run journal anyway
/home: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
Looks like on the normal boot up, the system encountered this journal problem and needed manual intervention.
Firebird Scrambler
Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer
Website = linkedin
- Status
Similar threads
- Locked
- Question
- Locked
- Question