Suse Linux 8.0 (Raid 5 SCSI)
is crashed periodically (it doesn't react to the mouse or keyboard and can't
be accessible throw network)
/var/log/boot.msg is missing
/var/log/messages doesn't consist date for last 10 hours

If I ran init 1 or press 1 during boot
I can see the following after command mount

/dev/sda1 on / type reiserfs (rw)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/data/lv0 on /data type reiserfs (rw)
/dev/data/lv1 on /ddd type reiserfs (rw)
/dev/data/lv2 on /lbp type reiserfs (rw)
/dev/sdc1 on /other type ext3 (rw)
shmfs on /dev/shm type shm (rw)
usbdevfs on /proc/bus/usb type usbdevfs (rw)

If I run umount / I didn't get error message but nothing change in mount
If I try boot from fdd or cdrom and run init1 the situation is the same (May
be I should do anithing else for boot from floppy and don't mount /?).

If I run fsck / I get the following message
"block 84369 has wrong order of items ..Fatal corruption were found,
Semantic pass skipped ..There were found 2 corrupions which can be fixed
only during --rebuild-tree check_and_tree_buffer_mem:dirty buffer (3 16)
found fsck.reiserfs /dev/sda1 failed (status ox2) Run manually"

If I run reiserfsck --rebuild-tree /
I get message "can not rebuild tree of mounted filesystem"

Please give me advice how I can umount /

[ Post a follow-up to this message ]

Evgeniy Petrov wrote:
> Suse Linux 8.0 (Raid 5 SCSI)
> is crashed periodically (it doesn't react to the mouse or keyboard and can
't
> be accessible throw network)
> /var/log/boot.msg is missing
> /var/log/messages doesn't consist date for last 10 hours
>
> If I ran init 1 or press 1 during boot
> I can see the following after command mount
>
> /dev/sda1 on / type reiserfs (rw)
> proc on /proc type proc (rw)
> devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
> /dev/data/lv0 on /data type reiserfs (rw)
> /dev/data/lv1 on /ddd type reiserfs (rw)
> /dev/data/lv2 on /lbp type reiserfs (rw)
> /dev/sdc1 on /other type ext3 (rw)
> shmfs on /dev/shm type shm (rw)
> usbdevfs on /proc/bus/usb type usbdevfs (rw)
>
> If I run umount / I didn't get error message but nothing change in mount
> If I try boot from fdd or cdrom and run init1 the situation is the same (M
ay
> be I should do anithing else for boot from floppy and don't mount /?).
>
> If I run fsck / I get the following message
> "block 84369 has wrong order of items ..Fatal corruption were found,
> Semantic pass skipped ..There were found 2 corrupions which can be fixed
> only during --rebuild-tree check_and_tree_buffer_mem:dirty buffer (3 16)
> found fsck.reiserfs /dev/sda1 failed (status ox2) Run manually"
>
> If I run reiserfsck --rebuild-tree /
> I get message "can not rebuild tree of mounted filesystem"
>
> Please give me advice how I can umount /
>
>

When you boot from the floppy or cdrom that SuSE provides you are
mounting the root from that device rather than /dev/sda1. Try
reiserfsck --rebuild-tree /dev/sda1.

Mike Forsman

[ Post a follow-up to this message ]

> > Please give me advice how I can umount /
> When you boot from the floppy or cdrom that SuSE provides you are
> mounting the root from that device rather than /dev/sda1. Try
> reiserfsck --rebuild-tree /dev/sda1.
Thank's for you answer!

When I boot fom SuSE cdrom I can't see my /dev/sda1 .
Reiserfsck doesn't see it.
reiserfsck --rebuild-tree /dev/sda1   (for sda2..5 situation the same)
Is it possible that I need do something for load my SCSI RAID controller aic
7899 ?
What I can do for it?

[ Post a follow-up to this message ]

On Fri, 2 Jul 2004 15:36:54 +0400, Evgeniy Petrov <evg@mail.wurth.ru> poured
into the usenet group comp.unix.admin:
> When I boot fom SuSE cdrom I can't see my /dev/sda1 .
> Reiserfsck doesn't see it.
> reiserfsck --rebuild-tree /dev/sda1   (for sda2..5 situation the same)
> Is it possible that I need do something for load my SCSI RAID controller a
ic
> 7899 ?
> What I can do for it?
modprobe aic7xxx

Devdas Bhagat

[ Post a follow-up to this message ]

 
aic[vbcol=seagreen] 
> modprobe aic7xxx
>
> Devdas Bhagat
Thank's a lot for answer! But
SuSE wrote "driver  needed to access the root file system should be compiled
directly into the kernel.
Do not configure scsi driver as modules."
Does anyone know how make boot disk with scsi support in kernel?
I can't find documentation about it in detail.

[ Post a follow-up to this message ]