Hi Stuart, I don't mind the redundancy. Sometimes things are tried twice (or more) in order to get them right once. :-)
Machine B will not boot from the CD at all. hal91 on floppy will boot every time from the floppy. hal91 files on a CD will not boot from the CD drive. Here is someone with a similar problem http://www.mail-archive.com/debian-u...@lists.debian.org/msg44513.html. I've been trying to install grub on my hard drive (which is /dev/hdc in Linux-land), and not having any success. I've booted into the Hurd, and run "grub-install", but that just gives me a usage summary. So I've tried "grub-install /dev/hdc", which reports that /dev/hdc is not found or not a block device. So I've tried "grub-install /dev/hd0 which complains about hd0 having a tray open or drive not ready, and that /dev/hd0 does not have any corresponding BIOS drive. So I cd'd into /dev, and ran "./MAKEDEV hd0", which does not generate any errors, but then when I do a "ls -l hd*" I get: hd0 : tray open or drive not ready hd0 : tray open or drive not ready hd0 : tray open or drive not ready hd0 : tray open or drive not ready brw-r----- 1 root root 0, 0 Jun 17 08:07 hd0 brw-r----- 1 root root 0, 0 Jun 17 08:07 hd1 brw-r----- 1 root root 0, 0 Jun 17 08:06 hd2 brw-r----- 1 root root 0, 0 May 29 09:07 hd2s1 brw-r----- 1 root root 0, 0 Jun 18 06:50 hd2s3 brw-r----- 1 root root 0, 0 Jun 17 08:08 hd3 Can anyone shed any light on why I'm getting these "tray open..." messages, or why grub doesn't seem to want to install? I've also tried installing grub from the grub boot floppy by typing, at the grub> prompt: root (hd0,0) setup (hd) which generates four or five lines of output, and it _looks_ to me like it installed properly, but when I try to boot off the hard drive, it just hangs before ever getting to a "Loading stage1" or similar message, usually forcing me to cycle the power to reset the computer. Just for kicks, I booted off a MS-DOS 6.22 floppy and ran "fdisk /mbr", and then tried to install grub again from the grub floppy, but the same thing happened. Thanks! -- Kent On (23/06/03 16:11), Kent West wrote: > > Thanks for the response, Clive. Turns out I was doing things the proper > way; it's just that something was screwy with the MBR I reckon. (hd0 > refers to the first hard drive that the BIOS lists, not to the first > hard drive on the first IDE port -- go figure). > > Anyway, I finally got tired of fighting it, and wiped the partitions and > repartitioned (using slightly different sizes to make sure I didn't just > resurrect the old setup) and reinstalled the Hurd, and this time grub > installed to the hard drive like it was supposed to. I have no > explanation. > > I'm going to wipe it once more and do it again, just for experimentation > purposes, before continuing on into Hurd-land. I do like GRUB (I use LILO on two servers) for dual boot systems - but I can't say I really understand it yet ;) Good luck with Hurd Clive I have read this post several times and still do not understand what is being discussed. I think there may be some clues here to my problem. I found the above by doing a Google search for: hdc : tray open or drive not ready. I also found this (http://mulinux.dotsrc.org/mu/relnotes/RELNOTES.11r3): Kernel log during probing ------------------------- Usually, when muLinux try to scan the hard-disk and any other block devices, a lot of kernel messages are printed. They can confuse or impression the user. Unfortunately, the stderr redirection do not work. If the CD in not in the driver, and I will try to read a simple byte from the CD-ROM with a command like: # dd if=/dev/cdrom bs=1c count=1 a lot of message like these: ==================================================== hdc: media changed hdc : tray open or drive not ready hdc : tray open or drive not ready hdc : tray open end_request: I/O error, dev 16:00, sector 0 dd: /dev/cdrom: I/O error 0+0 records in 0+0 records out ==================================================== normally are printed on the screen. I discovered a little program called "setlevel", developed by the only big Linux guru we have in Italy: Alessandro Rubini, author of the book "Linux Device Driver", O'Reilly (ehm, I think a kind of fractured english, but much better of mine). The command is able to change temporarily the console-level for kernel logging (two C statements). So, I put "setlevel 1" and "setlevel 5" around the "dd" command, and messages disappears. Nice to have in muLinux. I am using hal91 instead of muLinux but will the commands work the same? Thanks for your interest and help. Have a good day, Jim ----- Original Message ----- From: "Stuart Stevenson" <stus...@gmail.com> To: "Enhanced Machine Controller (EMC)" <emc-users@lists.sourceforge.net> Sent: Tuesday, April 21, 2009 11:37 PM Subject: Re: [Emc-users] Linux installation problem CD's are bootable Harddrive partitioned with hal91 fdisk -l and dmesg | grep hdc messages > Jim, > MachineA - machine the CD will boot on > MachineB - machine you are trying to load the software on > > This may seem redundant but since the CD will boot MachineA and you > can see the hard drive on MachineB you are trying to load the software > on you should be able to boot MachineB from the CD and run Ubuntu/EMC. > The install is usually simple from there. > Will MachineB boot (any operating system) from the CD? > Stuart > > On Tue, Apr 21, 2009 at 9:32 PM, Jim Fleig - CNC Services > <j...@cncservices.ws> wrote: >> Hi Stuart, >> >> All of the CD's that have been burned with my Windows desktop using >> InfraRecorder will boot the desktop tower and run fine. Per one >> suggestion I burned CD's at different speeds but this did not make a >> difference. >> >> With help from Przemek, using hal91 the hard drive was partitioned. Now >> >> fdisk -l Enter displays: >> >> The number of cylinders for this disk is set to 1027. >> This is larger than 1024, and may cause problems with: >> 1) software that runs at boot time (e.g., LILO) >> 2) booting and partitioning software form other OSs >> (e.g., DOS FDISK, OS/2 FDISK) >> >> Disk /dev/hda: 255 heads, 63 sectors, 1027 cylinders >> Units = cylinders of 16065 * 512 bytes >> >> Device Boot Begin Start End Blocks Id >> System >> /dev/hda1 1 1 1027 8249346 83 >> Linux native >> hdc : tray open or drive not ready >> hdc : tray open or drive not ready >> hdc : tray open >> end request: I/O error, dev 16:00, sector 0 >> [hal91 -=- /] _ >> >> and dmesg | grep hdc Enter displays: >> >> hdc: ATAPI CD ROM DRIVE 50X MAX, ATAPI CDROM drive >> hdc : tray open or drive not ready >> hdc : tray open or drive not ready >> hdc : tray open >> [hal91 -=- /] _ >> >> Are there other commands that would provide useful information? >> >> Thanks for your questions and advice. >> >> Hopefully this is closer to working. >> >> Have a good night, >> >> Jim >> >> ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
