>>> On 10/10/2008 at 11:59 AM, in message <[EMAIL PROTECTED]>, "Jones, Russell" <[EMAIL PROTECTED]> wrote: > I seem to have messed up my system pretty good. After I built and > installed the ldap client package the system quit responding. I ipl'ed > and it took forever (about 45 min) for the system to come up. I didn't > see any errors on the console, but the system still would not respond > when it came up.
Do you mean you could not logon from the console? If so, did you see a login prompt? Did the system accept the userid and password, and then not finish signing you on? > I cannot get to it by ssh or ftp. The good news is that > it is a test system. The bad news is that I have some files on it that I > would really like to recover. > > I tried bringing the dasd of the broken system online to another linux > system so I could at least recover my files. I get the following > message: > > [EMAIL PROTECTED]:/mnt/cloneVol# mount /dev/dasdb1 /mnt/cloneVol > mount: wrong fs type, bad option, bad superblock on /dev/dasdb1, > missing codepage or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > > syslog says: > > dasd: waiting for responses... > dasd(eckd): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: (4kB blks): 7212240kB at > 48kB/trk compatible disk layout > dasdb:VOL1/ LNXRS3: dasdb1 dasdb2 > EXT2-fs: dasd(94,5): couldn't mount because of unsupported optional > features (4000000). > VFS: Can't find ext3 filesystem on dev dasd(94,4). I would try to IPL the system from the installation kernel and ramdisk. You should be able to get the volume mounted and the network started from there without interference from the openLDAP stuff (if that is what is causing the issue). Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
