Hi,
On 10/11/2006 10:05 PM, Richard White wrote:
> In a scaled-back disaster recovery drill, I backed up a SLES 10 server
> (a web server that will replace our active RH 9 web server), then
> restore some files to another SLES 10 server. The restore ran fine; when
> it was finished, the files were there on the test server. When I reboot
> the test server, it hangs before it finishes.
>
> So I decided to try restoring just one directory at a time, beginning
> with /novell. I thought this would be innocuous enough since it doesn't
> have device drivers or anything else that the OS needs or references.
> After re-installing the OS and restoring this directory, I re-booted the
> test server. Same thing happened. I won't try to reproduce the entire
> screen, but here are some of the last lines:
>
> Filesystem is clean
> Replaying journal . .
> Reiserfs journal '/dev/hda2/' in blocks [18 . .8211]: 0 transactions
> replayed
> Checking internal tree . . finished
> fsck succeeded. Mounting root device read-write
> Mounting root /dev/hda2
> .
> .
> .
> More routine messages
> .
> .
> .
> hda: task_out_intr: status=0x50 { DriveReady SeekComplete }
> ide: failed opcode was: unknown
> hda: task_out_intr: status=0x50 { DriveReady SeekComplete }
> ide: failed opcode was: unknown
> hda: task_out_intr: status=0x50 { DriveReady SeekComplete }
> ide: failed opcode was: unknown
This looks like a possible hardware problem. Typically, this is when you
contact your system supplier.
> And this is where it stays. I can press reset and select Failsafe on
> bootup. Then I get a shell login. If I next try a standard boot, it
> hangs trying to configure the network interface. I can still do a
> Failsafe boot and get a shell login at this point and startx
> successfully, but clearly something fundamental got changed that we
> didn't expect.
If you don't have the support options to have other people fix your
sever you might use the smartmontools to check your hard disk state, and
probably run memtest (should be on the SuSE disk and / or the hard disk,
available at boot time). But this is beyond the Bacula mailing list, I
suppose...
> P.S. - The project of putting Bacula 1.38 on the SLES 10 box is on
> hold, but not retired. In the last attempt I encountered the dependency
> chase. Also, YaST's behavior in SLES 10 is very different from SLES 9,
> at least where installing software from RPMs is concerned, and I still
> haven't got that figured out
Well, there are a number of people who prefer smart above Yast or zen. I
have no especially good or bad experiences with SLES 10, so I can't give
a rwadl advice, but at least I'm sure that you're not the only one who
is, erm, only partly satisfied with SuSEs way of managing software
installation.
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
