[Cialug] Trying to label 2TB USB drive from Redhat 5.7

[Tom Pohl]

If you have parted installed, does partprobe make it show up?

-Tom


On Mar 21, 2014, at 10:32 AM, John Lengeling <john.lengeling at gmail.com> wrote:

>> What type of disklabel is the drive using?
> 
> No clue.  Can't access the drive to read the label using Linux tools.  It
> is a brand new drive so my guess it is GPT or MBR with NTFS partition.
> The kernel says the device is "sdd1" yet /dev/sdd and /dev/sdd1 do not
> exist for me to run fdisk or parted.
> 
>> What does the output of the following:
>> ls -l /dev/sg*
>> cat /proc/partitions
>> fdisk -l
> 
> Here you go:
> 
> sh-3.2# ls -l /dev/sg*
> crw------- 1 root root 21, 0 Jan 20  2013 /dev/sg0
> crw------- 1 root root 21, 1 Jan 20  2013 /dev/sg1
> crw------- 1 root root 21, 2 Jan 20  2013 /dev/sg2
> crw------- 1 root root 21, 3 Jan 20  2013 /dev/sg3
> 
> sh-3.2# cat /proc/partitions
> major minor  #blocks  name
> 
>   8     0  292968750 sda
>   8     1     104391 sda1
>   8     2  292856917 sda2
> 253     0  282624000 dm-0
> 253     1   10223616 dm-1
>   8    48 1953514580 sdd
>   8    49 1953410048 sdd1
> 
> sh-3.2# /sbin/fdisk -l
> 
> Disk /dev/sda: 300.0 GB, 300000000000 bytes
> 255 heads, 63 sectors/track, 36472 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> 
>   Device Boot      Start         End      Blocks   Id  System
> /dev/sda1   *           1          13      104391   83  Linux
> /dev/sda2              14       36472   292856917+  8e  Linux LVM
> sh-3.2#
> 
> 
> 
> I see the major/minor device numbers for sdd and sdd1...I guess I can try
> to just mknod the devices.  Will give that a try...
> 
> j
> 
> 
> On Thu, Mar 20, 2014 at 7:09 PM, Tom Pohl <tom at tcpconsulting.com> wrote:
> 
>> What does the output of the following:
>> ls -l /dev/sg*
>> cat /proc/partitions
>> fdisk -l
>> 
>> -Tom
>> 
>> 
>>> On Mar 20, 2014, at 5:25 PM, John Lengeling <john.lengeling at gmail.com>
>> wrote:
>>> 
>>> Trying access and label a 2TB portable USB drive under Redhat 5.7.
>>> 
>>> Normally this just "works" but in this case, the kernel says it is going
>> to
>>> use sdd1, but none of the device entries exists.
>>> 
>>> Output from dmesg:
>>> 
>>> usb 2-1.1: new high speed USB device using ehci_hcd and address 9
>>> usb 2-1.1: configuration #1 chosen from 1 choice
>>> scsi25 : SCSI emulation for USB Mass Storage devices
>>> usb-storage: device found at 9
>>> usb-storage: waiting for device to settle before scanning
>>> Vendor: TOSHIBA   Model: External USB 3.0  Rev: 0201
>>> Type:   Direct-Access                      ANSI SCSI revision: 06
>>> SCSI device sdd: 3907029160 512-byte hdwr sectors (2000399 MB)
>>> sdd: Write Protect is off
>>> sdd: Mode Sense: 2b 00 00 00
>>> sdd: assuming drive cache: write through
>>> SCSI device sdd: 3907029160 512-byte hdwr sectors (2000399 MB)
>>> sdd: Write Protect is off
>>> sdd: Mode Sense: 2b 00 00 00
>>> sdd: assuming drive cache: write through
>>> sdd: sdd1
>>> sd 25:0:0:0: Attached scsi disk sdd
>>> sd 25:0:0:0: Attached scsi generic sg4 type 0
>>> 
>>> /dev entries:
>>> 
>>> sh-3.2# ls -l /dev/sd*
>>> brw-r----- 1 root disk 8,  0 Jan 20  2013 /dev/sda
>>> brw-r----- 1 root disk 8,  1 Jan 20  2013 /dev/sda1
>>> brw-r----- 1 root disk 8,  2 Jan 20  2013 /dev/sda2
>>> brw-r----- 1 root disk 8, 16 Jan 20  2013 /dev/sdb
>>> brw-r----- 1 root disk 8, 32 Jan 20  2013 /dev/sdc
>>> 
>>> So why isn't udev creating the device entries?
>>> _______________________________________________
>>> Cialug mailing list
>>> Cialug at cialug.org
>>> http://cialug.org/mailman/listinfo/cialug
>> _______________________________________________
>> Cialug mailing list
>> Cialug at cialug.org
>> http://cialug.org/mailman/listinfo/cialug
>> 
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug