Sponsored Content
Full Discussion: Boot Problem
Top Forums UNIX for Advanced & Expert Users Boot Problem Post 62452 by silvaman on Wednesday 16th of February 2005 06:23:46 AM
Old 02-16-2005
..thanks for the suggestion. I looked through the start up messages again and found a line stating that the / filesystem had not been cleanly unmounted (from the freeze I guess). I loaded up the rescue disk and ran the reiserfsck - everything looked clean.

I then ran reiserfsck --check which then moaned about some corruption. I then followed with reiserfsck --fix-fixable which then supposedly fixed the error. I reran with the check option once more - it still complained and now said I would have to run reiserfsck --rebuildtree. I did this and it promptly gave a segmentation fault. I can no longer mount the partition or do anything else with it. I have a feeling I'm looking at a reinstall Smilie I sure am glad I seperate my filesystems onto different partitions else I would have lost everything!

I gotta say I'm a bit disappointed in resierfs - i never had these issues with ext3 even after repeated power outs - could always recover. However my knowledge of th reiser filesystem is limited and I guess the fault could well lie in my hardware - time will tell !

many thanks for help though - guess its reinstall time !
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Dual Boot problem,help!!!!

I had Win98 and Win Xp on a dual boot on my system, I formatted my C: drive to get rid of Win98 and installed Linux Madrake in its Place, it all installed ok but when I boot up I can no longer dual boot and it goes straight into Mandrake Linux. How can I get either a dual boot so I can get to XP... (10 Replies)
Discussion started by: Merv
10 Replies

2. UNIX for Advanced & Expert Users

Boot problem

we have a problem with a server UNIX SUN OS 5.7 : we tried to reboot it and we have the following error message : "boot load failed the file just loaded does not appear to be executable " we booted the server in single user mode with the cdrom we made the mirrored disk bootable we tried... (2 Replies)
Discussion started by: farzolito
2 Replies

3. UNIX for Dummies Questions & Answers

linux boot problem

i have instaled a boot loader and win98 on drive c: and linux on drive d: and when i go to boot with the loader into linux nottin happens.is there some way i should install lilo to let it boot of a loader on drive c: ? (5 Replies)
Discussion started by: perleo
5 Replies

4. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies

5. AIX

Boot problem - 0c33

Hi Guys everyone know this problem on P595??? One of my servers, on boot, sleep 10-15 minute on led 0c33. I know that it's a console problem... but i don't understand how resolve it. Ideas??? P.S. Sorry for my english. Thanks. Zio (0 Replies)
Discussion started by: Zio Bill
0 Replies

6. Solaris

Boot problem

Hi everyone, I have sun fire280R machine before i it is installed with solaris5.9 now i want to upgrade it but it not booting from the cd rom ....OK prompt also not comming i dont have solaris keyboard to press stop-A key...i have a intel supported keyboard ...what may be the problem it is... (1 Reply)
Discussion started by: alakshmanrao
1 Replies

7. UNIX for Dummies Questions & Answers

boot problem

hello i have a sun server V890 and it stops booting after adding 2 CPUs modules and gives me the following error message: Enabling system bus....... Done Initializing CPUs......... Done Initializing boot memory.. RAM-Copy CRC failure!Can't start: No image found FATAL: Can't find/decompress... (0 Replies)
Discussion started by: bahjatm
0 Replies

8. Solaris

boot problem

hello i have a sun server V890 and it stops booting after adding 2 CPUs modules and gives me the following error message: Enabling system bus....... Done Initializing CPUs......... Done Initializing boot memory.. RAM-Copy CRC failure!Can't start: No image found FATAL: Can't find/decompress... (12 Replies)
Discussion started by: bahjatm
12 Replies

9. Solaris

Boot problem

Hi all, I have the the following SCSI diagnostic codes shown in the attached photo I suspect disk drive failure what can I do further to diagnose the disk. and if possible to boot into OS again. (5 Replies)
Discussion started by: h@foorsa.biz
5 Replies

10. Red Hat

Multipath boot problem

Hi, My HP machine is using as boot device a disk defined in the Storage (IBM V5000). The connection is done by fiber connected through fiber switch. No lacal disks are installed. I'm using redhat 6.6. I've installed and configured multipath. Everything seems to work properly, however,... (0 Replies)
Discussion started by: Pazzeo
0 Replies
REISERFSCK(8)						      System Manager's Manual						     REISERFSCK(8)

NAME
reiserfsck - The checking tool for the ReiserFS filesystem. SYNOPSIS
reiserfsck [ -aprVy ] [ --rebuild-sb | --check | --fix-fixable | --rebuild-tree | --clean-attributes ] [ -j | --journal device ] [ -z | --adjust-size ] [ -n | --nolog ] [ -B | --badblocks file ] [ -l | --logfile file ] [ -q | --quiet ] [ -y | --yes ] [ -f | --force ] [ -S | --scan-whole-partition ] [ --no-journal-available ] device DESCRIPTION
Reiserfsck searches for a Reiserfs filesystem on a device, replays any necessary transactions, and either checks or repairs the file sys- tem. device is the special file corresponding to a device or to a partition (e.g /dev/hdXX for an IDE disk partition or /dev/sdXX for a SCSI disk partition). OPTIONS
--rebuild-sb This option recovers the superblock on a Reiserfs partition. Normally you only need this option if mount reports "read_super_block: can't find a reiserfs file system" and you are sure that a Reiserfs file system is there. But remember that if you have used some partition editor program and now you cannot find a filesystem, probably something has gone wrong while repartitioning and the start of the partition has been changed. If so, instead of rebuilding the super block on a wrong place you should find the correct start of the partition first. --check This default action checks filesystem consistency and reports, but does not repair any corruption that it finds. This option may be used on a read-only file system mount. --fix-fixable This option recovers certain kinds of corruption that do not require rebuilding the entire file system tree (--rebuild-tree). Nor- mally you only need this option if the --check option reports "corruption that can be fixed with --fix-fixable". This includes: zeroing invalid data-block pointers, correcting st_size and st_blocks for directories, and deleting invalid directory entries. --rebuild-tree This option rebuilds the entire filesystem tree using leaf nodes found on the device. Normally you only need this option if the reiserfsck --check reports "Running with --rebuild-tree is required". You are strongly encouraged to make a backup copy of the whole partition before attempting the --rebuild-tree option. Once reiserfsck --rebuild-tree is started it must finish its work (and you should not interrupt it), otherwise the filesystem will be left in the unmountable state to avoid subsequent data corruptions. --clean-attributes This option cleans reserved fields of Stat-Data items. There were days when there were no extended attributes in reiserfs. When they were implemented old partitions needed to be cleaned first -- reiserfs code in the kernel did not care about not used fields in its strutures. Thus if you have used one of the old (pre-attrbutes) kernels with a ReiserFS filesystem and you want to use extented attribues there, you should clean the filesystem first. --journal device , -j device This option supplies the device name of the current file system journal. This option is required when the journal resides on a sep- arate device from the main data device (although it can be avoided with the expert option --no-journal-available). --adjust-size, -z This option causes reiserfsck to correct file sizes that are larger than the offset of the last discovered byte. This implies that holes at the end of a file will be removed. File sizes that are smaller than the offset of the last discovered byte are corrected by --fix-fixable. --badblocks file, -B file This option sets the badblock list to be the list of blocks specified in the given `file`. The filesystem badblock list is cleared before the new list is added. It can be used with --fix-fixable to fix the list of badblocks (see debugreiserfs -B). If the device has bad blocks, every time it must be given with the --rebuild-tree option. --logfile file, -l file This option causes reiserfsck to report any corruption it finds to the specified log file rather than to stderr. --nolog, -n This option prevents reiserfsck from reporting any kinds of corruption. --quiet, -q This option prevents reiserfsck from reporting its rate of progress. --yes, -y This option inhibits reiserfsck from asking you for confirmation after telling you what it is going to do. It will assuem you con- firm. For safety, it does not work with the --rebuild-tree option. -a, -p These options are usually passed by fsck -A during the automatic checking of those partitions listed in /etc/fstab. These options cause reiserfsck to print some information about the specified filesystem, to check if error flags in the superblock are set and to do some light-weight checks. If these checks reveal a corruption or the flag indicating a (possibly fixable) corruption is found set in the superblock, then reiserfsck switches to the fix-fixable mode. If the flag indicating a fatal corruption is found set in the superblock, then reiserfsck finishes with an error. --force, -f Force checking even if the file system seems clean. -V This option prints the reiserfsprogs version and then exit. -r This option does nothing at all; it is provided only for backwards compatibility. EXPERT OPTIONS
DO NOT USE THESE OPTIONS UNLESS YOU KNOW WHAT YOU ARE DOING. WE ARE NOT RESPONSIBLE IF YOU LOSE DATA AS A RESULT OF THESE OPTIONS. --no-journal-available This option allows reiserfsck to proceed when the journal device is not available. This option has no effect when the journal is located on the main data device. NOTE: after this operation you must use reiserfstune to specify a new journal device. --scan-whole-partition, -S This option causes --rebuild-tree to scan the whole partition but not only the used space on the partition. AN EXAMPLE OF USING reiserfsck 1. You think something may be wrong with a reiserfs partition on /dev/hda1 or you would just like to perform a periodic disk check. 2. Run reiserfsck --check --logfile check.log /dev/hda1. If reiserfsck --check exits with status 0 it means no errors were discovered. 3. If reiserfsck --check exits with status 1 (and reports about fixable corruptions) it means that you should run reiserfsck --fix-fixable --logfile fixable.log /dev/hda1. 4. If reiserfsck --check exits with status 2 (and reports about fatal corruptions) it means that you need to run reiserfsck --rebuild-tree. If reiserfsck --check fails in some way you should also run reiserfsck --rebuild-tree, but we also encourage you to submit this as a bug report. 5. Before running reiserfsck --rebuild-tree, please make a backup of the whole partition before proceeding. Then run reiserfsck --rebuild- tree --logfile rebuild.log /dev/hda1. 6. If the reiserfsck --rebuild-tree step fails or does not recover what you expected, please submit this as a bug report. Try to provide as much information as possible including your platform and Linux kernel version. We will try to help solve the problem. EXIT CODES
reiserfsck uses the following exit codes: 0 - No errors. 1 - File system errors corrected. 2 - Reboot is needed. 4 - File system fatal errors left uncorrected, reiserfsck --rebuild-tree needs to be launched. 6 - File system fixable errors left uncorrected, reiserfsck --fix-fixable needs to be launched. 8 - Operational error. 16 - Usage or syntax error. AUTHOR
This version of reiserfsck has been written by Vitaly Fertman <vitaly@namesys.com>. BUGS
Please report bugs to the ReiserFS developers <reiserfs-dev@namesys.com>, providing as much information as possible--your hardware, kernel, patches, settings, all printed messages, the logfile; check the syslog file for any related information. TODO
Faster recovering, signal handling. SEE ALSO
mkreiserfs(8), reiserfstune(8) resize_reiserfs(8), debugreiserfs(8), Reiserfsprogs-3.6.21 January 2009 REISERFSCK(8)
All times are GMT -4. The time now is 12:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy