Am 2017-03-02 um 13:41 schrieb Bill Kenworthy:
> try lshw to get that info:
we had that already in the other leg of the thread
doesn't work for me:
# lshw -c disk
*-disk:0
description: SCSI Disk
physical id: 0.0.0
bus info: scsi@1:0.0.0
logical name: /dev/sda
On 02/03/17 18:03, Stefan G. Weichinger wrote:
> Am 2017-03-01 um 23:21 schrieb Bill Kenworthy:
>
>> Is there actually a disk on that interface? - I have a system where one
>> sdx allocated to an unused sata port with nothing attached - it returns
>> similar information to yours above - check the
Am 2017-03-01 um 22:42 schrieb Daniel Frey:
> I'm not sure how the sg? -> sd? mapping is supposed to work. I find it
> odd that there seems to be two nodes reported for each sd? entry.
> However, this could be the way the controller driver reports it to the
> kernel...
>
>> 07:01.0 SCSI storage
Am 2017-03-01 um 23:21 schrieb Bill Kenworthy:
> Is there actually a disk on that interface? - I have a system where one
> sdx allocated to an unused sata port with nothing attached - it returns
> similar information to yours above - check the other entries.
I checked them, sure.
to me it seems
On 01/03/17 23:05, Stefan G. Weichinger wrote:
> Am 2017-03-01 um 15:42 schrieb Neil Bothwick:
>
>> Never hurts to try the low hanging fruit first :)
>>
>> Have you tried lshw?
>
> did so right now:
>
>
>
> *-disk:2
> description: SCSI Disk
>
On 03/01/2017 08:31 AM, Stefan G. Weichinger wrote:
> Am 2017-03-01 um 16:49 schrieb Daniel Frey:
>
>>> Have you tried `lsblk -O`?
>>>
>>> Dan
>>>
>>
>> Well, I forgot how much info that barfs out.
>>
>> Try `lsblk -o name,model,serial` instead.
>
> nice one, thanks.
> But the shown serials
Am 2017-03-01 um 16:49 schrieb Daniel Frey:
>> Have you tried `lsblk -O`?
>>
>> Dan
>>
>
> Well, I forgot how much info that barfs out.
>
> Try `lsblk -o name,model,serial` instead.
nice one, thanks.
But the shown serials don't match the serials on the disk(s) :-(
I also tried "-O" and
On 03/01/2017 07:45 AM, Daniel Frey wrote:
> On 03/01/2017 07:05 AM, Stefan G. Weichinger wrote:
>> Am 2017-03-01 um 15:42 schrieb Neil Bothwick:
>>
>>> Never hurts to try the low hanging fruit first :)
>>>
>>> Have you tried lshw?
>>
>> did so right now:
>>
>>
>>
>> *-disk:2
>>
On 03/01/2017 07:05 AM, Stefan G. Weichinger wrote:
> Am 2017-03-01 um 15:42 schrieb Neil Bothwick:
>
>> Never hurts to try the low hanging fruit first :)
>>
>> Have you tried lshw?
>
> did so right now:
>
>
>
> *-disk:2
> description: SCSI Disk
>
Am 2017-03-01 um 15:42 schrieb Neil Bothwick:
> Never hurts to try the low hanging fruit first :)
>
> Have you tried lshw?
did so right now:
*-disk:2
description: SCSI Disk
physical id: 0.2.0
bus info: scsi@1:0.2.0
On Wed, 1 Mar 2017 14:46:00 +0100, Stefan G. Weichinger wrote:
> >> and I would like to know which hard disk (vendor, serial) each
> >> /dev/sdX is.
> >
> > hdparm -i /dev/sdX
>
>
> # hdparm -i /dev/sdi
>
> /dev/sdi:
> SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00
Am 2017-03-01 um 14:39 schrieb Neil Bothwick:
> On Wed, 1 Mar 2017 14:04:45 +0100, Stefan G. Weichinger wrote:
>
>> and I would like to know which hard disk (vendor, serial) each
>> /dev/sdX is.
>
> hdparm -i /dev/sdX
# hdparm -i /dev/sdi
/dev/sdi:
SG_IO: bad/missing sense data, sb[]: 70 00
On Wed, 1 Mar 2017 14:04:45 +0100, Stefan G. Weichinger wrote:
> and I would like to know which hard disk (vendor, serial) each /dev/sdX
> is.
hdparm -i /dev/sdX
--
Neil Bothwick
Yes, I've heard of "decaf." What's your point?
pgpO4mntXn3qg.pgp
Description: OpenPGP digital signature
could someone help me out?
I have this software-raid:
md3 : active raid6 sdi1[8] sdh1[6] sdg1[4] sdf1[5] sde1[3] sdd1[2] sdc1[0]
4391334912 blocks level 6, 64k chunk, algorithm 2 [8/6] [U_U_]
[>] recovery = 22.8% (167386900/731889152)
finish=196.6min
14 matches
Mail list logo
