Re: "Device 08:11 not ready" - error log

i got it

thank you very much

On 3/7/07, Matthew Galgoci <mgalgoci@xxxxxxxxxx> wrote:

> I am getting the following error log in the /var/log/messages
>
> kernel: Device 08:11 not ready.
> kernel: I/O error: dev 08:01, sector 2
> kernel: Device 08:01 not ready.
> kernel: I/O error: dev 08:01, sector 0
> Is this a hardware problem
>
> I need to know for which hardware, i am not able to find it in the
syslog
> messages

This is for device /dev/sda11 and /dev/sda1. You can pretty much assume it
is for all the partition on the disk.

08 is the scsi major for scsi disks.

01 is the minor for the first partition of the first disk

11 is the minor for the 10th partition on the first disk.

Each disk has a maximum of 16 partitions, 0 through 15.

eg:

[mgalgoci@workstation0 ~]$ ls /dev/sd* -al
brw-r----- 1 root disk 8, 0 2007-01-18 14:03 /dev/sda
brw-r----- 1 root disk 8, 1 2007-01-18 14:03 /dev/sda1
brw-r----- 1 root disk 8, 2 2007-01-18 14:03 /dev/sda2
brw-r----- 1 root disk 8, 16 2007-01-18 14:03 /dev/sdb
brw-r----- 1 root disk 8, 17 2007-01-18 14:03 /dev/sdb1
brw-r----- 1 root disk 8, 18 2007-01-18 14:03 /dev/sdb2

I hope that clears it up for you.

--
Matthew Galgoci
GIS Production Operations
Red Hat, Inc
919.754.3700 x44155

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list




--
Thanks and Regards
------------------------------
N S Vikram,
Mobile : 09486148402
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

Relevant Pages

  • Re: Linux community software-update-anarchy polemic
    ... Remember, I'm just a monkey. ... That implies that if you have one disk per partition, ... Trust the kernel or don't trust the kernel, but either way, both ...
    (comp.os.linux.misc)
  • Re: Flames over -- Re: Which is simpler?
    ... different from testing whether it has changed -- it could have changed while the system was asleep, with the result that hardware is indeed there but it's not the _same_ hardware. ... It is currently my belief that the kernel probes the hardware the same way after a cold boot, resume from s-t-r, and resume from s-t-d. ... This is why you can suspend to disk, and when you resume, your open files are still valid; the disk is found to be still there, so it continues to be accessible. ... the kernel queries the USB controller to see if a disconnect occurred while the system was asleep. ...
    (Linux-Kernel)
  • Re: My boss want to kill debian, please help !
    ... The *hardware* issue with e100 that I know off ... there's something else I should point out: the debian *stable* kernel ... currently sane. ... "One disk to rule them all, ...
    (Debian-User)
  • Re: Partition check considered as error is breaking mounting in 2.6.27
    ... Herton Ronaldo Krzesinski wrote: ... creates a partition with an off by one error". ... It is better for the kernel to warn and to proceed ... disk, and let the kernel create block devices which can not be accessed. ...
    (Linux-Kernel)
  • Re: Partition check considered as error is breaking mounting in 2.6.27
    ... Herton Ronaldo Krzesinski wrote: ... creates a partition with an off by one error". ... It is better for the kernel to warn and to proceed ... disk, and let the kernel create block devices which can not be accessed. ...
    (Linux-Kernel)