Thank you Nate, Sean, and Jason. I remembered that I could get a shell prompt from the Install script by hitting the old Alt-F2, so I booted from my install CD and poked around, and finally deduced I was having scsi bus errors.
All I had changed today was I put the cover back on. So I took the cover off, removed the not-working DAT drive, tidied up some cables, booted back into the CD, got a shell, ran e2fsck, fixed a few inode errors, and voila I'm back in business . . . . Now, anybody want to trade me a working DAT drive for 3 I know that don't and 3 more that probably don't? BTW - did I mention that I love unix, and Debian in particular????? This same problem in the Windoze world would have been a MUCH bigger headache to survive . . . . Plus, I love those Linux coders . . . . Once, when booting, it was having problems getting a status on a device on the scsi bus and the error messages were . . . error . . . trying again error . . . trying harder this time I was laughing out loud. You'd never see that out of a MicroSloth coder .. . . . Again, thanks all for your help. madmac On 11 Nov 2002, 17:40:15, nate wrote: > > 08:01: rw=0, wnat=2, limit=1 > > EXT3-fs: unable to read superblock > > attempt to access beyond end of device > > 08:01: rw=0, wnat=2, limit=1 > > EXT2-fs: unable to read superblock > > Kernel Panic: VFS: Unable to mount root fs on 08:01 > > > maybe the drive is dieing, I think you need to boot from > a floppy or CD and run fsck on the partition and hope data > is still there. > > but it sounds like the drive may be physically damaged. > another option is to go to your SCSI bios and see if it > has any low level analysis tools(adaptec BIOSs have this), > if you can't get fsck working. > > first thing is boot to a floppy or CD though. > > nate > > > > -- Doug MacFarlane [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
