Re: Mixed disk drive types problem

From: N. Curt Bean (cbean_at_raytheon.com)
Date: 10/30/03


Date: Thu, 30 Oct 2003 10:11:05 -0500

Thanks Vic,

    1) I have fixed the boot problem in the BIOS.

     2) The exact command is "fdisk /dev/sda".
          The exact error is: "Unable to open /dev/sda".
            (The SCSI disk drive is set to SCSI-ID=0)

    I have noticed in the messages file at the tail end is lines saying:
    -------------------------------------------------------------
Oct 30 04:59:26 ws39 kernel: Device not ready. Make sure there is a disc in
the drive.

Oct 30 04:59:26 ws39 kernel: sda : READ CAPACITY failed.

Oct 30 04:59:26 ws39 kernel: sda : status = 0, message = 00, host = 0,
driver = 28

Oct 30 04:59:26 ws39 kernel: Current sd00:00: sense key Not Ready

Oct 30 04:59:26 ws39 kernel: Additional sense indicates Medium not present

Oct 30 04:59:26 ws39 kernel: sda : block size assumed to be 512 bytes, disk
size 1GB.

Oct 30 04:59:26 ws39 kernel: sda: I/O error: dev 08:00, sector 0

Oct 30 04:59:26 ws39 kernel: I/O error: dev 08:00, sector 0

Oct 30 04:59:26 ws39 kernel: unable to read partition table

Oct 30 04:59:27 ws39 kernel: cdrom: This disc doesn't have any tracks I
recognize!

Oct 30 04:59:29 ws39 automount[746]: attempting to mount entry
/export/home/cbean

Oct 30 04:59:40 ws39 kernel: Device not ready. Make sure there is a disc in
the drive.

Oct 30 04:59:40 ws39 kernel: sda : READ CAPACITY failed.

Oct 30 04:59:40 ws39 kernel: sda : status = 0, message = 00, host = 0,
driver = 28

Oct 30 04:59:40 ws39 kernel: Current sd00:00: sense key Not Ready

Oct 30 04:59:40 ws39 kernel: Additional sense indicates Medium not present

Oct 30 04:59:40 ws39 kernel: sda : block size assumed to be 512 bytes, disk
size 1GB.

Oct 30 04:59:40 ws39 kernel: sda: I/O error: dev 08:00, sector 0

Oct 30 04:59:40 ws39 kernel: I/O error: dev 08:00, sector 0

Oct 30 04:59:40 ws39 kernel: unable to read partition table

Oct 30 04:59:40 ws39 kernel: Device not ready. Make sure there is a disc in
the drive.

Oct 30 04:59:40 ws39 kernel: sda : READ CAPACITY failed.

Oct 30 04:59:40 ws39 kernel: sda : status = 0, message = 00, host = 0,
driver = 28

Oct 30 04:59:40 ws39 kernel: Current sd00:00: sense key Not Ready

Oct 30 04:59:40 ws39 kernel: Additional sense indicates Medium not present

Oct 30 04:59:40 ws39 kernel: sda : block size assumed to be 512 bytes, disk
size 1GB.

Oct 30 04:59:40 ws39 kernel: sda: I/O error: dev 08:00, sector 0

Oct 30 04:59:40 ws39 kernel: I/O error: dev 08:00, sector 0

Oct 30 04:59:40 ws39 kernel: unable to read partition table

Oct 30 04:59:49 ws39 kernel: hdc : bad access: block=0, count=8

Oct 30 04:59:49 ws39 kernel: end_request: I/O error, dev 16:00 (hdc), sector
0

Oct 30 04:59:49 ws39 kernel: hdc : bad access: block=2, count=6

Oct 30 04:59:49 ws39 kernel: end_request: I/O error, dev 16:00 (hdc), sector
2

Oct 30 04:59:49 ws39 kernel: hdc : bad access: block=4, count=4

Oct 30 04:59:49 ws39 kernel: end_request: I/O error, dev 16:00 (hdc), sector
4

Oct 30 04:59:49 ws39 kernel: hdc : bad access: block=6, count=2

Oct 30 04:59:49 ws39 kernel: end_request: I/O error, dev 16:00 (hdc), sector
6

----------------------------------------------------------------------------
-----------------------------

Thanks again

Curt

"Vic" <vic@innocent.com> wrote in message
news:25971f29dfb60aba1ae6a1dc376b036f.60200@mygate.mailgate.org...
> "N. Curt Bean" <cbean@raytheon.com> wrote in message
> news:HD7ob.111$K6.112@bos-service2.ext.raytheon.com
>
> > 1) The system want to boot the SCSI disk drive instead of the IDE disk
> > /dev/hda. I must use the boot floppy to boot from the IDE disk drive.
>
> Boot order is defined in the BIOS - this has nothing whatsoever to do
> with linux...
>
> > 2) After booting from the IDE disk drive, I cannot fdisk the SCSI disk
> > drive. Says disk doesn't exist.
>
> What *exact* command are you typing?
>
> Vic.
>
>
> --
> Posted via Mailgate.ORG Server - http://www.Mailgate.ORG



Relevant Pages

  • Re: The usage of dvd-writers a pain rather than a gain?
    ... driver really resolve the possible problems caused by ... disc, first ... folder (with Window 2000 Prof. OS). ... The damage cycle has reduced ...
    (microsoft.public.windowsxp.general)
  • Re: DVD drive problem
    ... Pioneer don't list a driver for my drive, they don't seem to list drivers ... One thing I notice from device manager, ... with the icon saying DVD-RW as per disc, ...
    (microsoft.public.windowsxp.hardware)
  • Re: DVD drive problem
    ... Pioneer drivers: ... One thing I notice from device manager, it says that the driver I ... > disc or a disc with photos on they are accessible and can play or> upload. ...
    (microsoft.public.windowsxp.hardware)
  • RE: DVD burns but cant read in normal mode
    ... Running only in Safe Mode implies that it is some driver ... Edit menu, click Permissions. ... It could be a disc drive on this computer or a network drive. ... This means I can not read any discs from this drive - except in safe mode, ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Disc driver is module, software suspend fails
    ... > For reference I recite the original issue: the driver for my primary ... > disc is in the initrd, ... > complaining on the web that software suspend has stopped working after ... systems resumed after unsafe initrd is ran. ...
    (Linux-Kernel)