Re: Boot/install problem on H50

From: John Jolet (john.jolet_at_FXFN.COM)
Date: 12/29/03

  • Next message: Leyden, Joseph: "Re: Boot/install problem on H50" 
    Date:         Mon, 29 Dec 2003 15:23:11 -0600
To: aix-l@Princeton.EDU

    sounds like the cdrom drive doesn't work. If this is a brand-new machine, it's possible that the data cable to the cdrom has worked loose in shipping or something. does the system have a tape drive to boot from?

    -----Original Message-----
    From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU]On Behalf Of
    Lieberg, Patrick
    Sent: Monday, December 29, 2003 2:58 PM
    To: aix-l@Princeton.EDU
    Subject: Re: Boot/install problem on H50

    Removing everything but the cd from the bootlist gives the same results. This system is new to us and so the drives we installed have no working OS installed, so I cannot boot the machine normally. I've tried updating the firmware using the SMS menu, but it keeps complaining there is no diskette in the drive.

    This machine has me completely baffled. I'm thinking of taking the hard drives from my test system and putting them in this system to see if it will boot properly.

    -----Original Message-----
    From: John Jolet [mailto:john.jolet@FXFN.COM]
    Sent: Monday, December 29, 2003 11:41 AM
    To: aix-l@Princeton.EDU
    Subject: Re: Boot/install problem on H50

    what code do you get when you use sms to remove ALL but the cd from the bootlist? have you tried booting in maintenance mode? can you use the cdrom normally when booting from hdisk?

    -----Original Message-----
    From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU]On Behalf Of
    Lieberg, Patrick
    Sent: Monday, December 29, 2003 11:17 AM
    To: aix-l@Princeton.EDU
    Subject: Boot/install problem on H50

    I have an H50 here that I am trying to load AIX 4.3.3 on for testing the migration to 5.2 of our production DB. I cannot seem to get the system to boot/install from the AIX CD. I've double-checked the boot sequence in SMS and even done the install option from the SMS menus, but the system stops booting on a 0518 code on the LCD panel. Looking this code up, it suggests a problem was encountered doing a network boot, which is odd since I'm not doing a network boot.

    Any suggestions from the list would be helpful.

    thanks,
    Patrick Lieberg
    Systems Administrator
    ev3 Inc.

    _____________________________________________________________________
    This message has been checked for all known viruses

    _____________________________________________________________________
    Message scanned for viruses

    _____________________________________________________________________
    This message has been checked for all known viruses

  • Next message: Leyden, Joseph: "Re: Boot/install problem on H50"

    Relevant Pages

    • Pls help me SCSI-ize my IDE CDROM so K3b can see it
      ... I want both my CD drives to be visible under K3b. ... CDROM and my CDRW to be accessed with the ide-scsi kernel driver. ...
      (comp.os.linux.setup)
    • Pls help me SCSI-ize my IDE CDROM so K3b can use it
      ... I want both my CD drives to be visible under K3b. ... CDROM and my CDRW to be accessed with the ide-scsi kernel driver. ...
      (comp.os.linux.hardware)
    • Re: SUCCESS AT LAST
      ... >> "If the game wants to run from the CD, then your problem is that you ... >> not mount the CDROM drive in the .conf file or manually. ... guess you have to do two separate lines for the two drives.. ...
      (comp.sys.ibm.pc.games.adventure)
    • Re: Disappointed with version 6.0
      ... On Saturday 11 March 2006 18:48, Peter wrote: ... I removed the cdrom and the problem remains. ... If the message for ad0 has changed, and it is now detected as an ata100 ... could use all three drives. ...
      (freebsd-questions)
    • System hangs trying to mount CD
      ... I have two cdrom drives, one of which is 52x normal cd-drive and ... problem but trying to mount writable cd drive hangs my system. ... Jan 18 19:28:37 localhost kernel: cdrom: open failed. ...
      (comp.os.linux.hardware)