You are not logged in.

Pages: 1

#1 2009-02-16 09:43:47

Army
Member
Registered: 2007-12-07
Posts: 1,784

HAL doesn't recognize my ext. drive with 1500GB, the 500GB one works

Hi there

Some days ago I bought a 1500GB external harddrive, but after plugin it in via USB, it doesn't appear in my file manager. I tested it with thunar and pcmanfm, with both it didn't work. I don't think, that it's their fault, I think HAL doesn't like my new drive. My older one with 500GB is automounted as it should be. And I also don't think, that its a hardware issue, because in an ubuntu live-session it works with both harddrives.

This is how the two drives are partitioned

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0008941c

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       60801   488384001   83  Linux

Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0004aa3c

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1      182401  1465136001   83  Linux

As you can see, no difference here. The drive with 1500GB has xfs as filesystem, the 500GB has jfs, but that isn't the reason, I tried many filesystems on the 1500GB one and it didn't work with all of them

In the AUR, there appeared a new packaged called devicekit and I thought, that this might spit out some helpful informations. I used the command "devkit -m"

1500GB:

----------------------------------------------------------------------
action=add @ 10:14:29.876418
device:           /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1
  subsystem:      usb
  device file:    /dev/bus/usb/001/007
    symlink:      /dev/char/189:6
  properties:
    TYPE=0/0/0
    DEVNAME=/dev/bus/usb/001/007
    DEVLINKS=/dev/char/189:6
    BUSNUM=001
    UDEV_LOG=0
    MINOR=6
    ACTION=add
    PRODUCT=152d/2336/100
    DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-1
    DEVICE=/proc/bus/usb/001/007
    MAJOR=189
    SUBSYSTEM=usb
    DEVTYPE=usb_device
    DEVNUM=007
    SEQNUM=1668

----------------------------------------------------------------------
action=add @ 10:14:29.945265
device:           /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0
  subsystem:      usb
  device file:    (none)
  properties:
    TYPE=0/0/0
    INTERFACE=8/6/80
    UDEV_LOG=0
    ACTION=add
    PRODUCT=152d/2336/100
    DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0
    DEVICE=/proc/bus/usb/001/007
    SUBSYSTEM=usb
    DEVTYPE=usb_interface
    MODALIAS=usb:v152Dp2336d0100dc00dsc00dp00ic08isc06ip50
    SEQNUM=1669

----------------------------------------------------------------------
action=add @ 10:14:29.947723
device:           /sys/class/scsi_host/host4
  subsystem:      scsi_host
  device file:    (none)
  properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/class/scsi_host/host4
    SUBSYSTEM=scsi_host
    SEQNUM=1670

----------------------------------------------------------------------
action=add @ 10:14:29.952727
device:           /sys/class/usb_endpoint/usbdev1.7_ep81
  subsystem:      usb_endpoint
  device file:    /dev/usbdev1.7_ep81
    symlink:      /dev/char/251:24
  properties:
    DEVNAME=/dev/usbdev1.7_ep81
    DEVLINKS=/dev/char/251:24
    UDEV_LOG=0
    MINOR=24
    ACTION=add
    DEVPATH=/class/usb_endpoint/usbdev1.7_ep81
    MAJOR=251
    SUBSYSTEM=usb_endpoint
    SEQNUM=1671

----------------------------------------------------------------------
action=add @ 10:14:29.978530
device:           /sys/class/usb_endpoint/usbdev1.7_ep02
  subsystem:      usb_endpoint
  device file:    /dev/usbdev1.7_ep02
    symlink:      /dev/char/251:25
  properties:
    DEVNAME=/dev/usbdev1.7_ep02
    DEVLINKS=/dev/char/251:25
    UDEV_LOG=0
    MINOR=25
    ACTION=add
    DEVPATH=/class/usb_endpoint/usbdev1.7_ep02
    MAJOR=251
    SUBSYSTEM=usb_endpoint
    SEQNUM=1672

----------------------------------------------------------------------
action=add @ 10:14:29.986978
device:           /sys/class/usb_endpoint/usbdev1.7_ep00
  subsystem:      usb_endpoint
  device file:    /dev/usbdev1.7_ep00
    symlink:      /dev/char/251:26
  properties:
    DEVNAME=/dev/usbdev1.7_ep00
    DEVLINKS=/dev/char/251:26
    UDEV_LOG=0
    MINOR=26
    ACTION=add
    DEVPATH=/class/usb_endpoint/usbdev1.7_ep00
    MAJOR=251
    SUBSYSTEM=usb_endpoint
    SEQNUM=1674

----------------------------------------------------------------------
action=add @ 10:14:29.992531
device:           /sys/class/usb_device/usbdev1.7
  subsystem:      usb_device
  device file:    /dev/usbdev1.7
    symlink:      /dev/char/189:6
  properties:
    DEVNAME=/dev/usbdev1.7
    DEVLINKS=/dev/char/189:6
    UDEV_LOG=0
    MINOR=6
    ACTION=add
    DEVPATH=/class/usb_device/usbdev1.7
    MAJOR=189
    SUBSYSTEM=usb_device
    SEQNUM=1673

----------------------------------------------------------------------
action=add @ 10:14:34.967982
device:           /sys/class/bdi/8:32
  subsystem:      bdi
  device file:    (none)
  properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/class/bdi/8:32
    SUBSYSTEM=bdi
    SEQNUM=1679

----------------------------------------------------------------------
action=add @ 10:14:35.048659
device:           /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/host4/target4:0:0/4:0:0:0
  subsystem:      scsi
  device file:    (none)
  properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/host4/target4:0:0/4:0:0:0
    SUBSYSTEM=scsi
    DEVTYPE=scsi_device
    MODALIAS=scsi:t-0x00
    SEQNUM=1675

----------------------------------------------------------------------
action=add @ 10:14:35.049786
device:           /sys/class/scsi_disk/4:0:0:0
  subsystem:      scsi_disk
  device file:    (none)
  properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/class/scsi_disk/4:0:0:0
    SUBSYSTEM=scsi_disk
    SEQNUM=1676

----------------------------------------------------------------------
action=add @ 10:14:35.051976
device:           /sys/class/scsi_device/4:0:0:0
  subsystem:      scsi_device
  device file:    (none)
  properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/class/scsi_device/4:0:0:0
    SUBSYSTEM=scsi_device
    SEQNUM=1680

----------------------------------------------------------------------
action=add @ 10:14:35.060884
device:           /sys/class/scsi_generic/sg3
  subsystem:      scsi_generic
  device file:    /dev/sg3
    symlink:      /dev/char/21:3
  properties:
    DEVNAME=/dev/sg3
    DEVLINKS=/dev/char/21:3
    UDEV_LOG=0
    MINOR=3
    ACTION=add
    DEVPATH=/class/scsi_generic/sg3
    MAJOR=21
    SUBSYSTEM=scsi_generic
    SEQNUM=1681

----------------------------------------------------------------------
action=add @ 10:14:35.067457
device:           /sys/class/bsg/4:0:0:0
  subsystem:      bsg
  device file:    /dev/bsg/4:0:0:0
    symlink:      /dev/char/254:3
  properties:
    DEVNAME=/dev/bsg/4:0:0:0
    DEVLINKS=/dev/char/254:3
    UDEV_LOG=0
    MINOR=3
    ACTION=add
    DEVPATH=/class/bsg/4:0:0:0
    MAJOR=254
    SUBSYSTEM=bsg
    SEQNUM=1682

----------------------------------------------------------------------
action=add @ 10:14:35.105877
device:           /sys/block/sdc
  subsystem:      block
  device file:    /dev/sdc
    symlink:      /dev/block/8:32
    symlink:      /dev/disk/by-id/usb-ST315003_41AS_908888888888-0:0
    symlink:      /dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
  properties:
    ID_SERIAL_SHORT=908888888888
    DEVNAME=/dev/sdc
    DEVLINKS=/dev/block/8:32 /dev/disk/by-id/usb-ST315003_41AS_908888888888-0:0 /dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
    ID_MODEL=41AS
    ID_SERIAL=ST315003_41AS_908888888888-0:0
    ID_INSTANCE=0:0
    UDEV_LOG=0
    ID_PATH=pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
    MINOR=32
    ACTION=add
    ID_VENDOR=ST315003
    ID_BUS=usb
    DEVPATH=/block/sdc
    ID_TYPE=disk
    ID_REVISION=0100
    MAJOR=8
    SUBSYSTEM=block
    DEVTYPE=disk
    SEQNUM=1677

----------------------------------------------------------------------
action=add @ 10:14:35.144133
device:           /sys/block/sdc/sdc1
  subsystem:      block
  device file:    /dev/sdc1
    symlink:      /dev/block/8:33
    symlink:      /dev/disk/by-id/usb-ST315003_41AS_908888888888-0:0-part1
    symlink:      /dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0-part1
    symlink:      /dev/disk/by-uuid/8a60b3b7-50bc-48a7-b3ba-aa0f13f32156
    symlink:      /dev/disk/by-label/1500GB
  properties:
    ID_SERIAL_SHORT=908888888888
    ID_FS_LABEL=1500GB
    ID_FS_LABEL_ENC=1500GB
    DEVNAME=/dev/sdc1
    DEVLINKS=/dev/block/8:33 /dev/disk/by-id/usb-ST315003_41AS_908888888888-0:0-part1 /dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0-part1 /dev/disk/by-uuid/8a60b3b7-50bc-48a7-b3ba-aa0f13f32156 /dev/disk/by-label/1500GB
    ID_MODEL=41AS
    ID_SERIAL=ST315003_41AS_908888888888-0:0
    ID_INSTANCE=0:0
    UDEV_LOG=0
    ID_PATH=pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
    MINOR=33
    ACTION=add
    ID_VENDOR=ST315003
    ID_BUS=usb
    DEVPATH=/block/sdc/sdc1
    ID_TYPE=disk
    ID_REVISION=0100
    ID_FS_USAGE=filesystem
    MAJOR=8
    SUBSYSTEM=block
    ID_FS_TYPE=xfs
    ID_FS_UUID=8a60b3b7-50bc-48a7-b3ba-aa0f13f32156
    DEVTYPE=partition
    SEQNUM=1678
    ID_FS_UUID_ENC=8a60b3b7-50bc-48a7-b3ba-aa0f13f32156

500GB:

----------------------------------------------------------------------
action=add @ 10:13:40.628381
device:           /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-2
  subsystem:      usb
  device file:    /dev/bus/usb/001/006
    symlink:      /dev/char/189:5
  properties:
    TYPE=0/0/0
    DEVNAME=/dev/bus/usb/001/006
    DEVLINKS=/dev/char/189:5
    BUSNUM=001
    UDEV_LOG=0
    MINOR=5
    ACTION=add
    PRODUCT=1058/910/106
    DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2
    DEVICE=/proc/bus/usb/001/006
    MAJOR=189
    SUBSYSTEM=usb
    DEVTYPE=usb_device
    DEVNUM=006
    SEQNUM=1653

----------------------------------------------------------------------
action=add @ 10:13:40.700691
device:           /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0
  subsystem:      usb
  device file:    (none)
  properties:
    TYPE=0/0/0
    INTERFACE=8/6/80
    UDEV_LOG=0
    ACTION=add
    PRODUCT=1058/910/106
    DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0
    DEVICE=/proc/bus/usb/001/006
    SUBSYSTEM=usb
    DEVTYPE=usb_interface
    MODALIAS=usb:v1058p0910d0106dc00dsc00dp00ic08isc06ip50
    SEQNUM=1654

----------------------------------------------------------------------
action=add @ 10:13:40.701744
device:           /sys/class/scsi_host/host3
  subsystem:      scsi_host
  device file:    (none)
  properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/class/scsi_host/host3
    SUBSYSTEM=scsi_host
    SEQNUM=1655

----------------------------------------------------------------------
action=add @ 10:13:40.702982
device:           /sys/class/usb_endpoint/usbdev1.6_ep81
  subsystem:      usb_endpoint
  device file:    /dev/usbdev1.6_ep81
    symlink:      /dev/char/251:21
  properties:
    DEVNAME=/dev/usbdev1.6_ep81
    DEVLINKS=/dev/char/251:21
    UDEV_LOG=0
    MINOR=21
    ACTION=add
    DEVPATH=/class/usb_endpoint/usbdev1.6_ep81
    MAJOR=251
    SUBSYSTEM=usb_endpoint
    SEQNUM=1656

----------------------------------------------------------------------
action=add @ 10:13:40.705026
device:           /sys/class/usb_endpoint/usbdev1.6_ep02
  subsystem:      usb_endpoint
  device file:    /dev/usbdev1.6_ep02
    symlink:      /dev/char/251:22
  properties:
    DEVNAME=/dev/usbdev1.6_ep02
    DEVLINKS=/dev/char/251:22
    UDEV_LOG=0
    MINOR=22
    ACTION=add
    DEVPATH=/class/usb_endpoint/usbdev1.6_ep02
    MAJOR=251
    SUBSYSTEM=usb_endpoint
    SEQNUM=1657

----------------------------------------------------------------------
action=add @ 10:13:40.709720
device:           /sys/class/usb_endpoint/usbdev1.6_ep00
  subsystem:      usb_endpoint
  device file:    /dev/usbdev1.6_ep00
    symlink:      /dev/char/251:23
  properties:
    DEVNAME=/dev/usbdev1.6_ep00
    DEVLINKS=/dev/char/251:23
    UDEV_LOG=0
    MINOR=23
    ACTION=add
    DEVPATH=/class/usb_endpoint/usbdev1.6_ep00
    MAJOR=251
    SUBSYSTEM=usb_endpoint
    SEQNUM=1659

----------------------------------------------------------------------
action=add @ 10:13:40.719258
device:           /sys/class/usb_device/usbdev1.6
  subsystem:      usb_device
  device file:    /dev/usbdev1.6
    symlink:      /dev/char/189:5
  properties:
    DEVNAME=/dev/usbdev1.6
    DEVLINKS=/dev/char/189:5
    UDEV_LOG=0
    MINOR=5
    ACTION=add
    DEVPATH=/class/usb_device/usbdev1.6
    MAJOR=189
    SUBSYSTEM=usb_device
    SEQNUM=1658

----------------------------------------------------------------------
action=add @ 10:13:45.659241
device:           /sys/class/bdi/8:16
  subsystem:      bdi
  device file:    (none)
  properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/class/bdi/8:16
    SUBSYSTEM=bdi
    SEQNUM=1664

----------------------------------------------------------------------
action=add @ 10:13:45.680716
device:           /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/host3/target3:0:0/3:0:0:0
  subsystem:      scsi
  device file:    (none)
  properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/host3/target3:0:0/3:0:0:0
    SUBSYSTEM=scsi
    DEVTYPE=scsi_device
    MODALIAS=scsi:t-0x00
    SEQNUM=1660

----------------------------------------------------------------------
action=add @ 10:13:45.681808
device:           /sys/class/scsi_disk/3:0:0:0
  subsystem:      scsi_disk
  device file:    (none)
  properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/class/scsi_disk/3:0:0:0
    SUBSYSTEM=scsi_disk
    SEQNUM=1661

----------------------------------------------------------------------
action=add @ 10:13:45.695199
device:           /sys/class/scsi_device/3:0:0:0
  subsystem:      scsi_device
  device file:    (none)
  properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/class/scsi_device/3:0:0:0
    SUBSYSTEM=scsi_device
    SEQNUM=1665

----------------------------------------------------------------------
action=add @ 10:13:45.703093
device:           /sys/class/scsi_generic/sg2
  subsystem:      scsi_generic
  device file:    /dev/sg2
    symlink:      /dev/char/21:2
  properties:
    DEVNAME=/dev/sg2
    DEVLINKS=/dev/char/21:2
    UDEV_LOG=0
    MINOR=2
    ACTION=add
    DEVPATH=/class/scsi_generic/sg2
    MAJOR=21
    SUBSYSTEM=scsi_generic
    SEQNUM=1666

----------------------------------------------------------------------
action=add @ 10:13:45.709314
device:           /sys/class/bsg/3:0:0:0
  subsystem:      bsg
  device file:    /dev/bsg/3:0:0:0
    symlink:      /dev/char/254:2
  properties:
    DEVNAME=/dev/bsg/3:0:0:0
    DEVLINKS=/dev/char/254:2
    UDEV_LOG=0
    MINOR=2
    ACTION=add
    DEVPATH=/class/bsg/3:0:0:0
    MAJOR=254
    SUBSYSTEM=bsg
    SEQNUM=1667

----------------------------------------------------------------------
action=add @ 10:13:45.773375
device:           /sys/block/sdb
  subsystem:      block
  device file:    /dev/sdb
    symlink:      /dev/block/8:16
    symlink:      /dev/disk/by-id/usb-WD_5000AAK_External_574341505730373832303839-0:0
    symlink:      /dev/disk/by-path/pci-0000:00:1d.7-usb-0:2:1.0-scsi-0:0:0:0
  properties:
    ID_SERIAL_SHORT=574341505730373832303839
    DEVNAME=/dev/sdb
    DEVLINKS=/dev/block/8:16 /dev/disk/by-id/usb-WD_5000AAK_External_574341505730373832303839-0:0 /dev/disk/by-path/pci-0000:00:1d.7-usb-0:2:1.0-scsi-0:0:0:0
    ID_MODEL=5000AAK_External
    ID_SERIAL=WD_5000AAK_External_574341505730373832303839-0:0
    ID_INSTANCE=0:0
    UDEV_LOG=0
    ID_PATH=pci-0000:00:1d.7-usb-0:2:1.0-scsi-0:0:0:0
    MINOR=16
    ACTION=add
    ID_VENDOR=WD
    ID_BUS=usb
    DEVPATH=/block/sdb
    ID_TYPE=disk
    ID_REVISION=1.06
    MAJOR=8
    SUBSYSTEM=block
    DEVTYPE=disk
    SEQNUM=1662

----------------------------------------------------------------------
action=add @ 10:13:45.839326
device:           /sys/block/sdb/sdb1
  subsystem:      block
  device file:    /dev/sdb1
    symlink:      /dev/block/8:17
    symlink:      /dev/disk/by-id/usb-WD_5000AAK_External_574341505730373832303839-0:0-part1
    symlink:      /dev/disk/by-path/pci-0000:00:1d.7-usb-0:2:1.0-scsi-0:0:0:0-part1
    symlink:      /dev/disk/by-uuid/442a9a4c-ffd4-4d7f-b966-8c2935f7928f
    symlink:      /dev/disk/by-label/500GB
  properties:
    ID_SERIAL_SHORT=574341505730373832303839
    ID_FS_LABEL=500GB
    ID_FS_LABEL_ENC=500GB
    DEVNAME=/dev/sdb1
    DEVLINKS=/dev/block/8:17 /dev/disk/by-id/usb-WD_5000AAK_External_574341505730373832303839-0:0-part1 /dev/disk/by-path/pci-0000:00:1d.7-usb-0:2:1.0-scsi-0:0:0:0-part1 /dev/disk/by-uuid/442a9a4c-ffd4-4d7f-b966-8c2935f7928f /dev/disk/by-label/500GB
    ID_MODEL=5000AAK_External
    ID_SERIAL=WD_5000AAK_External_574341505730373832303839-0:0
    ID_INSTANCE=0:0
    UDEV_LOG=0
    ID_PATH=pci-0000:00:1d.7-usb-0:2:1.0-scsi-0:0:0:0
    MINOR=17
    ACTION=add
    ID_VENDOR=WD
    ID_BUS=usb
    DEVPATH=/block/sdb/sdb1
    ID_TYPE=disk
    ID_REVISION=1.06
    ID_FS_USAGE=filesystem
    MAJOR=8
    SUBSYSTEM=block
    ID_FS_TYPE=jfs
    ID_FS_UUID=442a9a4c-ffd4-4d7f-b966-8c2935f7928f
    DEVTYPE=partition
    SEQNUM=1663
    ID_FS_UUID_ENC=442a9a4c-ffd4-4d7f-b966-8c2935f7928f

I hope someone finds some useful informations in these lines!

If you have some other test tools or command lines or whatever I could do to give you more or better informations, please let me know!

p.s.: Right in this moment I was thinking about recompiling HAL with less patches, but even Arch uses many, so I'm not really sure which one or which combination could even be the reason. But I'll try it without any patch now right after posting this thread.

Offline

#2 2009-02-16 23:45:32

Army
Member
Registered: 2007-12-07
Posts: 1,784

Re: HAL doesn't recognize my ext. drive with 1500GB, the 500GB one works

Compiling HAL doesn't want to work, so I'll have to wait for you to bring ideas. Or would filing it in the bugtracker be a better idea than this thread? I mean, the thing is, I'm not sure, what causes this, if it's an Arch related thing or if it's something for upstream

Offline

#3 2009-02-17 05:13:28

Mektub
Member
From: Lisbon /Portugal
Registered: 2008-01-02
Posts: 647

Re: HAL doesn't recognize my ext. drive with 1500GB, the 500GB one works

Army,

Look in the logs if Arch is recognizing your disc when you plug it in.

Boot Arch with the drive unpluged, then on a terminal type:

tail -f /var/log/messages

Now plug the drive and see what messages show up in the log.
You can try it with the 500 gb drive to see how it should look like.

Mektub

Follow me on twitter: https://twitter.com/johnbina

Offline

#4 2009-02-17 15:47:02

Army
Member
Registered: 2007-12-07
Posts: 1,784

Re: HAL doesn't recognize my ext. drive with 1500GB, the 500GB one works

Okay, I tried that out

1500GB

Feb 17 16:49:09 Archlinux usb 1-2: new high speed USB device using ehci_hcd and address 10
Feb 17 16:49:09 Archlinux usb 1-2: configuration #1 chosen from 1 choice
Feb 17 16:49:09 Archlinux scsi6 : SCSI emulation for USB Mass Storage devices
Feb 17 16:49:14 Archlinux scsi 6:0:0:0: Direct-Access     ST315003 41AS                  PQ: 0 ANSI: 2 CCS
Feb 17 16:49:14 Archlinux sd 6:0:0:0: [sdb] 2930277168 512-byte hardware sectors: (1.50 TB/1.36 TiB)
Feb 17 16:49:14 Archlinux sd 6:0:0:0: [sdb] Write Protect is off
Feb 17 16:49:14 Archlinux sd 6:0:0:0: [sdb] 2930277168 512-byte hardware sectors: (1.50 TB/1.36 TiB)
Feb 17 16:49:14 Archlinux sd 6:0:0:0: [sdb] Write Protect is off
Feb 17 16:49:14 Archlinux sdb: sdb1
Feb 17 16:49:14 Archlinux sd 6:0:0:0: [sdb] Attached SCSI disk
Feb 17 16:49:14 Archlinux sd 6:0:0:0: Attached scsi generic sg2 type 0

500GB

Feb 17 16:49:46 Archlinux usb 1-2: new high speed USB device using ehci_hcd and address 11
Feb 17 16:49:47 Archlinux usb 1-2: configuration #1 chosen from 1 choice
Feb 17 16:49:47 Archlinux scsi7 : SCSI emulation for USB Mass Storage devices
Feb 17 16:49:52 Archlinux scsi 7:0:0:0: Direct-Access     WD       5000AAK External 1.06 PQ: 0 ANSI: 0
Feb 17 16:49:52 Archlinux sd 7:0:0:0: [sdb] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
Feb 17 16:49:52 Archlinux sd 7:0:0:0: [sdb] Write Protect is off
Feb 17 16:49:52 Archlinux sd 7:0:0:0: [sdb] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
Feb 17 16:49:52 Archlinux sd 7:0:0:0: [sdb] Write Protect is off
Feb 17 16:49:52 Archlinux sdb: sdb1
Feb 17 16:49:52 Archlinux sd 7:0:0:0: [sdb] Attached SCSI disk
Feb 17 16:49:52 Archlinux sd 7:0:0:0: Attached scsi generic sg2 type 0

Last edited by Army (2009-02-17 15:50:01)

Offline

#5 2009-02-17 16:13:08

Mektub
Member
From: Lisbon /Portugal
Registered: 2008-01-02
Posts: 647

Re: HAL doesn't recognize my ext. drive with 1500GB, the 500GB one works

Army,

Arch is detecting your disk allright. Your problem is at a higher level with automount, kde whatever.

Can't help with that since I dont use automount.

My WM is IceWM and my external disks are mounted either thru /etc/fstab, thru /etc/rc.local or manually.

You can always mount your 1500 gb disk manually just to check, it wlll be:

mount /dev/sdb1 /media/disk1500

or

mount /dev/sdc1 /media/disk1500

depending if the 500 gb disk was detected first or not.

The mount point, in this case /media/disk1500 must exist but the name is up to you.

You can also check your /etc/fstab, and insert a line:

/dev/sdc1   /media/disk1500   auto  defaults   0 2

Mektub

Follow me on twitter: https://twitter.com/johnbina

Offline

#6 2009-02-17 18:16:21

Army
Member
Registered: 2007-12-07
Posts: 1,784

Re: HAL doesn't recognize my ext. drive with 1500GB, the 500GB one works

Hi

Thanks for your answers!

I use LXDE, so there is no KDE stuff or whatever. Right now I mount the 1500GB hard drive with pmount, which works quite well, but of course it would be better, if it was mounted automatically. I also already tested the idea of putting something into the fstab (I did it with uuid's), which works quite well, but for some reason pcmanfm doesn't show it up, so I cannot do the mounting click. If I go into an open-dialog of for example firefox or whatever application, there I see all fstab entries, including the cdrom. So it would be cool to tell pcmanfm to show all fstab-entries. By the way, I also tested it with thunar, doesn't show it up as well.

But all this is just a workaround, I'm of the opinion, that this should work automatically for both drives! You said, the problem is at a higher level. But where exactly could I continue searching and / or testing?

Offline

#7 2009-02-17 18:28:40

iBertus
Member
From: Greenville, NC
Registered: 2004-11-04
Posts: 2,228

Re: HAL doesn't recognize my ext. drive with 1500GB, the 500GB one works

I suppose it's possible that Ubuntu is patching HAL to workaround a bug with these huge drives. I don't suppose you could give another DE a try to see if this issue is related to your current setup or if those are broken too.

Offline

#8 2009-02-17 21:51:32

Army
Member
Registered: 2007-12-07
Posts: 1,784

Re: HAL doesn't recognize my ext. drive with 1500GB, the 500GB one works

Hm, yes I was thinking about trying those patches. Is http://patches.ubuntu.com/h/hal/extracted/ the right adress for their patches? If so, which one would you think might be worth testing?
I ran into this problem, when I was on Xfce, now on LXDE it's the same. Do you think using Gnome for example might make a difference?!

Offline

#9 2009-02-17 23:54:42

sage
Member
Registered: 2008-10-28
Posts: 7

Re: HAL doesn't recognize my ext. drive with 1500GB, the 500GB one works

I'm having a problem kind of like this. I have a 1TB Western Digital MyBook. It has the option of running in RAID0 or RAID1. I have it in RAID0 for more storage. My computer seems to find it, but it doesn't mount and it doesn't show up in /dev/.

Here's what dmesg says when I plug it in

usb 1-2: new high speed USB device using ehci_hcd and address 9
usb 1-2: configuration #1 chosen from 1 choice
input: Western Digital My Book as /class/input/input9
generic-usb 0003:1058:0905.0004: input,hidraw3: USB HID v1.11 Device [Western Digital My Book] on usb-0000:00:1d.7-2/input1
Initializing USB Mass Storage driver...
scsi2 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 9
usb-storage: waiting for device to settle before scanning
scsi 2:0:0:0: Enclosure         WD       My Book Device   104a PQ: 0 ANSI: 4
scsi 2:0:0:0: Attached scsi generic sg2 type 13
usb-storage: device scan complete

tail /var/log/messages.log gives

Feb 17 18:33:57 sage usb 1-2: new high speed USB device using ehci_hcd and address 9
Feb 17 18:33:57 sage usb 1-2: configuration #1 chosen from 1 choice
Feb 17 18:33:57 sage input: Western Digital My Book as /class/input/input9
Feb 17 18:33:57 sage generic-usb 0003:1058:0905.0004: input,hidraw3: USB HID v1.11 Device [Western Digital My Book] on usb-0000:00:1d.7-2/input1
Feb 17 18:33:57 sage Initializing USB Mass Storage driver...
Feb 17 18:33:57 sage scsi2 : SCSI emulation for USB Mass Storage devices
Feb 17 18:33:57 sage usbcore: registered new interface driver usb-storage
Feb 17 18:33:57 sage USB Mass Storage support registered.
Feb 17 18:34:02 sage scsi 2:0:0:0: Enclosure         WD       My Book Device   104a PQ: 0 ANSI: 4
Feb 17 18:34:02 sage scsi 2:0:0:0: Attached scsi generic sg2 type 13
Feb 17 18:34:02 sage load-modules.sh: 'scsi:t-0x0d' is not a valid module or alias name

The last line says that it can't find the "scsi:t-0x0d" module, but I can't find what I would need to enable to get that module. I can't find any related modules in the standard arch modules either. I'm using a custom kernel and I can't boot the standard arch kernel to test because it says something like "/dev/sda5" cannot be found and then it panics (the same startup options work fine on my custom kernel, the standard flips out for some reason).

Offline

#10 2009-02-18 16:33:36

Army
Member
Registered: 2007-12-07
Posts: 1,784

Re: HAL doesn't recognize my ext. drive with 1500GB, the 500GB one works

Hm, in my opinion your problem is quite different, because if it really doesn't even show up in /dev/, it seems to be a much bigger problem. But maybe someone knows it better.


What I forgot to mention:
As can be seen above, on both drives I have just one single partition, which is full size of the drive. Because I was thinking, maybe the largeness of the partition might be the reason (which seems to be the right thought wink ), I put a smaller partition onto the 1500GB drive and left the rest unpartitioned. This way everything worked as it should, automatically mounted etc. I started with a partition of 500GB and then made it bigger and bigger. If I remember right, it stopped working at about 1200GB.

Offline

#11 2009-02-18 17:10:49

perbh
Member
From: Republic of Texas
Registered: 2005-03-04
Posts: 765

Re: HAL doesn't recognize my ext. drive with 1500GB, the 500GB one works

You may want to put a delay in the kernel invocation line - usb-drives take some time to settle which is why they are not properly discovered at boot-time.

If I have usb-drives connected at boot - I mount them in /etc/rc.local - something like this:

dmesg | grep -q 'sdb1$' && mount /dev/sdb1 /media/usbdisk

Of course - if you have more than one usb-disk, you need some more clever scripting - maybe the following can be used as a template:
dev=`dmesg | awk 'BEGIN { flag = 0 }{
  if (index($0, "(1.5 TB") > 0) flag++
  if (!flag) next
  if (match($0, "sd?1$") > 0) { printf "%s\n", substr($0,RSTART,RLENGTH); exit 0; }
}'`
test "x$dev" != x && mount /dev/$dev /media/disk1500

- and then, of course, you could do the same for your 500 Gb one ...
All you need is some unique string from 'dmesg' that you can use a flag and then read on untill you hit something that ends in sd?1   :-)

<edit> sed -e 's/(1.5TB)/(1.5 TB/' </edit>

Last edited by perbh (2009-02-18 18:29:06)

Offline

Pages: 1

Board footer

Powered by FluxBB