From: Andreas Unterkircher <unki@netshadow.at>
To: Richard Nairn <Richard@nairnconsulting.ca>
Cc: Thomas Callahan <callahant@tessco.com>,
linux-admin <linux-admin@vger.kernel.org>
Subject: Re: Figureing out which device
Date: Thu, 15 Jun 2006 18:30:16 +0200 [thread overview]
Message-ID: <44918B18.2030308@netshadow.at> (raw)
In-Reply-To: <op.ta6z70t8izdgzp@w5-cal-h014058.nrn.nrcan.gc.ca>
Probably 08:21 is hex... So it would be 8:33 in dec.
Richard Nairn schrieb:
> None of my devices match up like major/minor. I checked that first..
>
>
> # cat partitions
> major minor #blocks name rio rmerge rsect ruse wio wmerge wsect
> wuse running use aveq
>
> 8 0 35843686 sda 9649 31576 329458 67170 3475 5379 71368
> 192970 0 42440 260130
> 8 1 33736500 sda1 9634 31529 329274 67130 3475 5379 71368
> 192970 0 42400 260090
> 8 2 2104483 sda2 13 41 168 30 0 0 0 0 0 30 30
> 8 16 35843686 sdb 2757 9896 100648 391070 1442 1142 21768
> 13410 0 9970 404480
> 8 17 35840983 sdb1 2756 9893 100640 391070 1442 1142 21768
> 13410 0 9970 404480
> 8 32 35843686 sdc 2291 10014 97978 11340 2377 1734 34128 16280
> 0 8650 27620
> 8 33 35840983 sdc1 2290 10011 97970 11330 2377 1734 34128
> 16280 0 8640 27610
> 9 0 71681792 md0 0 0 0 0 0 0 0 0 0 0 0
>
>
> On Thu, 15 Jun 2006 08:59:29 -0600, Thomas Callahan
> <callahant@tessco.com> wrote:
>
>> Looks like a major/minor number for device /dev/sda.....
>>
>> Check your /dev/sd* entries.
>>
>> Also "cat /proc/partitions" will show major/minor numbers. Then you
>> can correlate that to a device.
>>
>>
>> Tom Callahan
>> TESSCO Technologies
>> Desk: (410)-229-1361
>> Cell: (410)-588-7605
>> Email: callahant@tessco.com
>>
>> A real engineer only resorts to documentation when the keyboard dents on
>> the forehead get too noticeable.
>>
>>
>>
>> On Jun 15, 2006, at 10:56 AM, Richard Nairn wrote:
>>
>>> Hi,
>>>
>>> I have a drive which is getting I/O errors. It is telling me that
>>> it is
>>>
>>> dev 08:21.
>>>
>>> How does this translate into which scsi device is having the problem?
>>>
>>> Thanks
>>>
>>>
>>> --| Richard Nairn Specializing in Linux
>>> | Nairn Consulting Web / Database Solutions
>>> | Calgary, AB
>>> | Richard@NairnConsulting.ca
>>> -
>>> To unsubscribe from this list: send the line "unsubscribe linux-admin"
>>> in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
> --| Richard Nairn Specializing in Linux
> | Nairn Consulting Web / Database Solutions
> | Calgary, AB
> | Richard@NairnConsulting.ca
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2006-06-15 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 14:56 Figureing out which device Richard Nairn
2006-06-15 14:59 ` Thomas Callahan
2006-06-15 15:05 ` Richard Nairn
2006-06-15 16:30 ` Andreas Unterkircher [this message]
2006-06-15 17:03 ` Richard Nairn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44918B18.2030308@netshadow.at \
--to=unki@netshadow.at \
--cc=Richard@nairnconsulting.ca \
--cc=callahant@tessco.com \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).