Re: Newbie Install Question on Umax S900 -- addendum
Quick follow-up to my previous message. On reboot after the initial boot failure (see previous message below) I get the error message that "/dev/sdb4 was not cleanly unmounted, check forced."
At this point, I get a huge number of SCSI errors, as follows:
scsi1: MEDIUM ERROR on channel 0, id 3, lun 0, CDB: Read (10) 00 00 67 1d 07 00 00 80 00
Info fld=0x671d24, Current sd08:14: sense key Medium Error
Additional sense indicates Unrecovered read error
scsidisk I/O error: dev 08:14, sector 6033200
this is repeated several times on the screen and is followed by:
Error reading block 754150 (attempt to read block from filesystem resulted in short read) while doing inode scan.
/dev/sdb4: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck failed. Please repair manually and reboot. Please note that the root file system is currently mounted read-only. To emount is read-write:
#mount -n -o remount,rw /
Finally, this is followed by the message:
Control-D will exit from this shell and reboot the system. Give root password for maintenance (or type control-D for normal startup):
Is this normal? Is my hard disk hosed? This disk is an older external scsi disk running off the onboard external scsi that has worked faithfully for me for the past couple of years.
Any help or information is greatly appreciated!
Ted Swinyar, swinte@wwc.edu
http://www.randomworks.com/
>>> "Ted Swinyar" <swinte@wwc.edu> - 1/28/01 12:26 AM >>>
Thank you to everyone who responded to my initial question about getting Debian going on the S900.
I've gotten BootX going and pointing to sdb4 where I've installed the / partition in the initial configuration. On first boot into Debian I get the following error message:
Starting PCMCIA services: modules/lib/modules/2.2.17/pcmcia/i82365.o: init_module: Device or resource busy
Hint: this error may be caused by incorrect module parameters, including invalid IO or IRQ parameters
ds: no socket drivers loaded!
/lib/modules/2.2.17/pcmcia/ds.0: init_module: device or resource busy
Hint: this error can caused by incorrect module parameters, including invalid IO or IRQ parameters
cardmgr.
Starting internet superserver: inetd.
/bin/sh: /sbin/termwrap: No such file or directory
/bin/sh: exec: /sbin/termwrap: cannot execute: No such file or directory
<<< a bunch of the above lines repeated numerous times >>>
INIT: Id "1" respawning too fast: disabled for 5 minutes
After this point, the system waits for a couple of minutes before displaying the same: "/bin/sh: /sbin/termwrap: No such file or directory
/bin/sh: exec: /sbin/termwrap: cannot execute: No such file or directory"
error a gazillion times more.
Was there something I should have done differently on the initial configuration of debian? Should I use a different kernel than the default kernel that came with the Debian CDs from CheapBytes? Has anyone run into this error message before?
Thanks!
Ted Swinyar, swinte@wwc.edu
http://www.randomworks.com/
>>> Ethan Benson <erbenson@alaska.net> - 1/17/01 4:38 PM >>>
On Wed, Jan 17, 2001 at 02:36:57PM -0800, Ted Swinyar wrote:
> Hello,
> I am interested in getting Debian PPC going on an old Umax S900
> I've got sitting around. I got the CheapBytes CDs of Debian PPC and
> was able to successfully boot into the initial installer and was
> able to proceed through the installation until the part of the
> install process where I was supposed to create a boot disk. At that
> point I received an error message that this procedure was not
> supported yet and have been unable to continue the process beyond
> this point. Upon reboot Debian fails to boot and I'm kicked back to
> square 1.
boot floppy creation is not supported on powerpc so that part is
normal. bootloader installation only works [partially] on oldworld
macs such as yours. however the bootloader setup does not configure
OpenFirmware to boot quik. you can try the following step to set the
OF variable yourself:
nvsetenv boot-device "$(ofpath /dev/hda)0"
assuming its an ide disk, use /dev/sda if its scsi (and the first scsi
disk).
the other option is bootx but that requires macos which is quite
ugly.
> I have been surfing around the net and have read through the Debian
> install guide, the FAQ-o-matic and penguinppc.net's guides. Has
> anyone run into this type of problem previously? Is there anything
> special I need to do to get the S900 going?
the install docs mention the bootloader stuff. quik is not as well
documented online though. (its simple really, but OpenFirmware is
black art)
> If this isn't the appropriate place to post questions like these, I
> apologize in advance and would appreciate any guidance as to other
> locations where I could find assistance on this.
no this list is fine.
--
Ethan Benson
http://www.alaska.net/~erbenson/
--
To UNSUBSCRIBE, email to debian-powerpc-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: