Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 14
Resolved so skip to the last part for a quick recap . [RESOLVED] Xubuntu can't find esata disk Every time I need to do something other then just boot up ...
  1. #1
    Just Joined!
    Join Date
    Jan 2011
    Posts
    93

    [SOLVED] (xubuntu) Can't use esata disk

    Resolved so skip to the last part for a quick recap.

    [RESOLVED] Xubuntu can't find esata disk


    Every time I need to do something other then just boot up and use allready installed apps I run into trouble. Today a simpe task of connecting an esata drive was not at all possbile to handle. What ever i tried I got error msg. I tried to turn on the drive before boot. Still error. I tried to reconnect it while xubuntu was running and all I got was this error message:


    Code:
    Failed to mount "2T Volume".
    
    org.freedesktop.hal.storage.mount-fixed
    auth_admin_keep_always <--(action, result).

    Here is my fstab output:



    Code:
    # /etc/fstab: static file system information.
    #
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    proc            /proc           proc    defaults        0       0
    # /dev/sda4
    UUID=c0f5951b-eb72-438e-bff8-6f2093002e3d /               ext3    relatime,errors=remount-ro 0       1
    # /dev/sda1
    UUID=d52db645-175c-4d86-ac0c-c211b1663a38 /boot           ext3    relatime        0       2
    # /dev/md0
    UUID=20c07563-baa9-4e23-873e-c16518566dda /home           ext3    relatime        0       2
    # /dev/sdb1
    UUID=b5dbf8a1-912c-4705-8f40-52142b52bc81 /tmp            ext3    relatime        0       2
    # /dev/sda3
    UUID=5b61fd1b-ac4a-4dac-b024-7e3c1ee484a1 /usr            ext3    relatime        0       2
    # /dev/sda2
    UUID=1e69c93d-5259-420e-ba51-ff617e18a9db /var            ext3    relatime        0       2
    # /dev/sdb2
    UUID=45ac14e9-f9a8-4e2d-a1f4-c4fa5f47fdd3 none            swap    sw              0       0
    /dev/scd0       /media/cdrom0   udf,iso9660 user,noauto,exec,utf8 0       0


    Why will not this esata drive work in xubuntu?

    OS: Xubuntu 8.04 LTS x 64
    Mobo: Asus P5n SLI
    4 x sata drives in software raid using all 4 sata sockets
    Last edited by piergen; 02-08-2011 at 04:15 PM.

  2. #2
    Just Joined! rafatmb's Avatar
    Join Date
    Feb 2011
    Location
    Brazil
    Posts
    25
    With the system on, what messages appear on /var/log/messages when you plug the disk?

    I suggest : tail -f /var/log/messages

    then plug the disk and check it out, and paste here.

  3. #3
    Just Joined!
    Join Date
    Jan 2011
    Posts
    93
    Quote Originally Posted by rafatmb View Post
    With the system on, what messages appear on /var/log/messages when you plug the disk?

    I suggest : tail -f /var/log/messages

    then plug the disk and check it out, and paste here.

    Ok, here is /var/log/messages before connectiing e-sata disk:

    Code:
    tail -f /var/log/messages
    Feb  8 14:39:25 quadcore kernel: [12466.044395] usb 1-4: configuration #1 chosen from 1 choice
    Feb  8 14:39:25 quadcore kernel: [12466.191306] eth1: register 'rndis_host' at usb-0000:00:0b.1-4, RNDIS device, 80:00:60:0f:e8:00
    Feb  8 14:39:26 quadcore kernel: [12467.295100] eth1: unregister 'rndis_host' usb-0000:00:0b.1-4, RNDIS device
    Feb  8 14:39:26 quadcore kernel: [12467.652221] usb 1-4: reset high speed USB device using ehci_hcd and address 9
    Feb  8 14:39:27 quadcore kernel: [12468.646603] usb 1-4: reset high speed USB device using ehci_hcd and address 9
    Feb  8 14:39:31 quadcore kernel: [12472.783824] usb 1-4: USB disconnect, address 9
    Feb  8 14:39:35 quadcore kernel: [12476.042534] usb 1-4: new high speed USB device using ehci_hcd and address 10
    Feb  8 14:39:35 quadcore kernel: [12476.183187] usb 1-4: configuration #1 chosen from 1 choice
    Feb  8 14:39:37 quadcore kernel: [12477.979375] usb 1-4: reset high speed USB device using ehci_hcd and address 10
    Feb  8 14:39:37 quadcore kernel: [12478.782059] usb 1-4: reset high speed USB device using ehci_hcd and address 10

    Then when I switch on esata disk:

    Code:
    Feb  8 14:43:23 quadcore kernel: [12703.958817] ata1: hard resetting link
    Feb  8 14:43:33 quadcore kernel: [12713.955412] ata1: hard resetting link
    Feb  8 14:43:39 quadcore kernel: [12719.466423] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Feb  8 14:43:39 quadcore kernel: [12719.501833] ata1.00: HPA unlocked: 3907029168 -> 3907029168, native 18446744073321613488
    Feb  8 14:43:39 quadcore kernel: [12719.501843] ata1.00: ATA-8: WDC WD20EADS-00S2B0, 01.00A01, max UDMA/133
    Feb  8 14:43:39 quadcore kernel: [12719.501847] ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
    Feb  8 14:43:39 quadcore kernel: [12719.508508] ata1.00: configured for UDMA/133
    Feb  8 14:43:39 quadcore kernel: [12719.508521] ata1: EH complete
    Feb  8 14:43:39 quadcore kernel: [12719.508652] scsi 0:0:0:0: Direct-Access     ATA      WDC WD20EADS-00S 01.0 PQ: 0 ANSI: 5
    Feb  8 14:43:39 quadcore kernel: [12719.508755] sd 0:0:0:0: [sde] 3907029168 512-byte hardware sectors (2000399 MB)
    Feb  8 14:43:39 quadcore kernel: [12719.508768] sd 0:0:0:0: [sde] Write Protect is off
    Feb  8 14:43:39 quadcore kernel: [12719.508790] sd 0:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Feb  8 14:43:39 quadcore kernel: [12719.508843] sd 0:0:0:0: [sde] 3907029168 512-byte hardware sectors (2000399 MB)
    Feb  8 14:43:39 quadcore kernel: [12719.508854] sd 0:0:0:0: [sde] Write Protect is off
    Feb  8 14:43:39 quadcore kernel: [12719.508875] sd 0:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Feb  8 14:43:39 quadcore kernel: [12719.508880]  sde: sde1
    Feb  8 14:43:39 quadcore kernel: [12719.514672] sd 0:0:0:0: [sde] Attached SCSI disk
    Feb  8 14:43:39 quadcore kernel: [12719.514717] sd 0:0:0:0: Attached scsi generic sg5 type 0


    And finally I also disconnected the esata disk, which gave me this:



    Code:
    Feb  8 14:43:23 quadcore kernel: [12703.958817] ata1: hard resetting link
    Feb  8 14:43:33 quadcore kernel: [12713.955412] ata1: hard resetting link
    Feb  8 14:43:39 quadcore kernel: [12719.466423] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Feb  8 14:43:39 quadcore kernel: [12719.501833] ata1.00: HPA unlocked: 3907029168 -> 3907029168, native 18446744073321613488
    Feb  8 14:43:39 quadcore kernel: [12719.501843] ata1.00: ATA-8: WDC WD20EADS-00S2B0, 01.00A01, max UDMA/133
    Feb  8 14:43:39 quadcore kernel: [12719.501847] ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
    Feb  8 14:43:39 quadcore kernel: [12719.508508] ata1.00: configured for UDMA/133
    Feb  8 14:43:39 quadcore kernel: [12719.508521] ata1: EH complete
    Feb  8 14:43:39 quadcore kernel: [12719.508652] scsi 0:0:0:0: Direct-Access     ATA      WDC WD20EADS-00S 01.0 PQ: 0 ANSI: 5
    Feb  8 14:43:39 quadcore kernel: [12719.508755] sd 0:0:0:0: [sde] 3907029168 512-byte hardware sectors (2000399 MB)
    Feb  8 14:43:39 quadcore kernel: [12719.508768] sd 0:0:0:0: [sde] Write Protect is off
    Feb  8 14:43:39 quadcore kernel: [12719.508790] sd 0:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Feb  8 14:43:39 quadcore kernel: [12719.508843] sd 0:0:0:0: [sde] 3907029168 512-byte hardware sectors (2000399 MB)
    Feb  8 14:43:39 quadcore kernel: [12719.508854] sd 0:0:0:0: [sde] Write Protect is off
    Feb  8 14:43:39 quadcore kernel: [12719.508875] sd 0:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Feb  8 14:43:39 quadcore kernel: [12719.508880]  sde: sde1
    Feb  8 14:43:39 quadcore kernel: [12719.514672] sd 0:0:0:0: [sde] Attached SCSI disk
    Feb  8 14:43:39 quadcore kernel: [12719.514717] sd 0:0:0:0: Attached scsi generic sg5 type 0

    Well it seems disk is seen, right? System even sees the disk name.
    How can I make system automount this disk? I mean esata should not need to be connected at boot, one should be able to connect/disconnect at will without problems. But here I can't even read/write to the disk no matter what I do.

  4. #4
    Just Joined! rafatmb's Avatar
    Join Date
    Feb 2011
    Location
    Brazil
    Posts
    25
    Appears that's all right.

    You tried to create/format a partition using fdisk/mkfs?

    Print the following command:

    fdisk -l /dev/sde

  5. #5
    Just Joined!
    Join Date
    Jan 2011
    Posts
    93
    Formatted the drive on another computer using Gparted so the disk is formatted and should be fine.

    Here is my fdisk:

    Code:
    ~$ fdisk -l /dev/sde
    
    Cannot open /dev/sde
    So that didnt work for me. I have browsed other forums as well and I
    stumbled over one that have similar problem and he got a quickfix for that problem:

    Quick & Dirty solution:

    in /etc/PolicyKit/PolicyKit.conf insert into section <config> permission for all users to mount all disks
    Code:
    <match action="org.freedesktop.hal.storage.*">
    <return result="yes"/>
    </match>

    And here is my PolicyKit.conf I have not edited this in any way yet:

    Code:
    <?xml version="1.0" encoding="UTF-8"?> <!-- -*- XML -*- -->
    
    <!DOCTYPE pkconfig PUBLIC "-//freedesktop//DTD PolicyKit Configuration 1.0//EN"
    "http://hal.freedesktop.org/releases/PolicyKit/1.0/config.dtd">
    
    <!-- See the manual page PolicyKit.conf(5) for file format -->
    
    <config version="0.1">
        <match user="root">
            <return result="yes"/>
        </match>
        <define_admin_auth group="admin"/>
    </config>
    This Quick and Dirty Fix I do not understand. Where would I make the changes?

    Should I replace this part here:

    Code:
    <match user="root">
            <return result="yes"/>
        </match>
    with the one suggested:

    Code:
    <match action="org.freedesktop.hal.storage.*">
        <return result="yes"/>
    </match>
    Or should I just add it in between the <config></config> part?
    And will it even work with two sets of <match></match> tags?

    I am confused, and also little afraid to brake anything cause I have no idea what it is I am doing here so little help pls.
    Last edited by piergen; 02-08-2011 at 02:12 PM.

  6. #6
    Just Joined!
    Join Date
    Jan 2011
    Posts
    93
    Ok remember/close tag is importent
    Well I added <match action> and seems I get more info from disk now. Running tail -f /var/log/messages gives me this output now:
    Code:
    Feb  8 16:24:52 quadcore kernel: [18783.080600] ata1: hard resetting link
    Feb  8 16:25:02 quadcore kernel: [18793.069032] ata1: hard resetting link
    Feb  8 16:25:08 quadcore kernel: [18798.659912] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Feb  8 16:25:08 quadcore kernel: [18798.696998] ata1.00: HPA unlocked: 3907029168 -> 3907029168, native 18446744073321613488
    Feb  8 16:25:08 quadcore kernel: [18798.697006] ata1.00: ATA-8: WDC WD20EADS-00S2B0, 01.00A01, max UDMA/133
    Feb  8 16:25:08 quadcore kernel: [18798.697011] ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
    Feb  8 16:25:08 quadcore kernel: [18798.704161] ata1.00: configured for UDMA/133
    Feb  8 16:25:08 quadcore kernel: [18798.704170] ata1: EH complete
    Feb  8 16:25:08 quadcore kernel: [18798.704264] scsi 0:0:0:0: Direct-Access     ATA      WDC WD20EADS-00S 01.0 PQ: 0 ANSI: 5
    Feb  8 16:25:08 quadcore kernel: [18798.704383] sd 0:0:0:0: [sde] 3907029168 512-byte hardware sectors (2000399 MB)
    Feb  8 16:25:08 quadcore kernel: [18798.704398] sd 0:0:0:0: [sde] Write Protect is off
    Feb  8 16:25:08 quadcore kernel: [18798.704417] sd 0:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Feb  8 16:25:08 quadcore kernel: [18798.704472] sd 0:0:0:0: [sde] 3907029168 512-byte hardware sectors (2000399 MB)
    Feb  8 16:25:08 quadcore kernel: [18798.704482] sd 0:0:0:0: [sde] Write Protect is off
    Feb  8 16:25:08 quadcore kernel: [18798.704503] sd 0:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Feb  8 16:25:08 quadcore kernel: [18798.704509]  sde: sde1
    Feb  8 16:25:08 quadcore kernel: [18798.709853] sd 0:0:0:0: [sde] Attached SCSI disk
    Feb  8 16:25:08 quadcore kernel: [18798.709899] sd 0:0:0:0: Attached scsi generic sg5 type 0
    Feb  8 16:25:11 quadcore kernel: [18802.308301] kjournald starting.  Commit interval 5 seconds
    Feb  8 16:25:11 quadcore kernel: [18802.313011] EXT3 FS on sde1, internal journal
    Feb  8 16:25:11 quadcore kernel: [18802.313017] EXT3-fs: mounted filesystem with ordered data mode.
    If you see from 16:24:52 there is where I reconnected esata disk. Now we can see filesystem -ext 3 also.

    I had to comment out the original <match></match> tags. Think we are one step closer now.

  7. #7
    Just Joined! rafatmb's Avatar
    Join Date
    Feb 2011
    Location
    Brazil
    Posts
    25
    The message says that the device sde1 was mounted.

    Paste the return os the following commands, please:

    fdisk -l
    mount

  8. #8
    Just Joined!
    Join Date
    Jan 2011
    Posts
    93
    Well now I can see the disk so I will try to mount and see what happends.

    Still get the same from fdisk:

    Code:
    ~$ fdisk -l /dev/sde
    Cannot open /dev/sde
    mount:
    Code:
    mount
    /dev/sda4 on / type ext3 (rw,relatime,errors=remount-ro)
    proc on /proc type proc (rw,noexec,nosuid,nodev)
    /sys on /sys type sysfs (rw,noexec,nosuid,nodev)
    varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
    varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
    udev on /dev type tmpfs (rw,mode=0755)
    devshm on /dev/shm type tmpfs (rw)
    devpts on /dev/pts type devpts (rw,gid=5,mode=620)
    lrm on /lib/modules/2.6.24-26-generic/volatile type tmpfs (rw)
    /dev/sda1 on /boot type ext3 (rw,relatime)
    /dev/md0 on /home type ext3 (rw,relatime)
    /dev/sdb1 on /tmp type ext3 (rw,relatime)
    /dev/sda3 on /usr type ext3 (rw,relatime)
    /dev/sda2 on /var type ext3 (rw,relatime)
    securityfs on /sys/kernel/security type securityfs (rw)
    none on /proc/fs/vmblock/mountPoint type vmblock (rw)
    binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
    /dev/sde1 on /media/disk type ext3 (rw,nosuid,nodev,uhelper=hal)

  9. #9
    Linux Guru
    Join Date
    Nov 2007
    Posts
    1,695
    You're in Ubuntu - if you're not root, you must prefix admin commands with SUDO.

    Code:
    sudo fdisk -l /dev/sde

  10. #10
    Just Joined!
    Join Date
    Jan 2011
    Posts
    93
    Tks HROAdmin

    Now we got an output:

    Code:
    WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.
    
    
    Disk /dev/sde: 2000.3 GB, 2000398934016 bytes
    255 heads, 63 sectors/track, 243201 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00000000
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sde1               1      243202  1953514583+  ee  EFI GPT

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...