Results 1 to 10 of 10

Thread: Cannot mount USB / doesn't automount after power crashed

  1. #1

    Default Cannot mount USB / doesn't automount after power crashed

    Looking for help with USB removable thumb drive.
    Lost power and the computer went down, when it restarted the USB will not mount.
    Any help is appreciated.

    leap 42.2 -

    Below are the results on my system to:
    Code:
    udisksctl monitor Monitoring the udisks daemon. Press Ctrl+C to exit.
    21:38:11.454: The udisks-daemon is running (name-owner :1.36)
    When I removed the USB thumb drive it added:
    Code:
    21:38:47.449: Removed /org/freedesktop/UDisks2/block_devices/sdd1
    
    21:38:47.482: Removed /org/freedesktop/UDisks2/block_devices/sdd
    I plugged it back in and it did nothing. Unplugged it, and this time nothing changed.

    Code:
    dad@linux-hi7k:~> udisksctl status MODEL                     REVISION  SERIAL               DEVICE
    --------------------------------------------------------------------------
    SAMSUNG HD161GJ           1118      S1V5J9CZ300518       sda     
    CT120BX100SSD1            MU02      1527F009453E         sdb     
    Crucial_CT250MX2          MU03      1614123EE61E         sdc     
    hp        DDVDW TS-H653R  0E00      R0626GCZ23729900     sr0
    The devices shown are my 3 hard drives and the DVD/CD.
    The USB is plugged in, but not detected or showing.

    Tried to mount sdd and sdd1, but nothing.

    Will not mount the usb thumb drive.
    openSUSE Tumbleweed 64-bit / Cinnamon

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,798

    Default Re: Cannot mount USB / doesn't automount after power crashed

    When it is not detected as before, I assume some hardware problem (due to the power outage) in that USB or the device itself. Try another USB mass storage device on that USB and/or try to put the device into another USB if there are more on the system.

    And of course when there is no /dev/sdd1 created, it is rather useless to try to mount a file system on it.
    And /dev/sdd is the whole disk and as it is partitioned (one partition) there is of course no file system on /dev/sdd itself, thus that will never be mountable, created or not.
    Henk van Velden

  3. #3
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,704
    Blog Entries
    1

    Default Re: Cannot mount USB / doesn't automount after power crashed

    With the suspect device plugged in what is reported by the following?
    Code:
    sudo /sbin/fdisk -l
    Code:
    /usr/sbin/blkid

  4. #4

    Default Re: Cannot mount USB / doesn't automount after power crashed

    Quote Originally Posted by deano_ferrari View Post
    With the suspect device plugged in what is reported by the following?
    Code:
    sudo /sbin/fdisk -l
    Code:
    /usr/sbin/blkid
    Code:
    sudo /sbin/fdisk -l
    Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0xb9d6b850
    
    Device     Boot     Start       End   Sectors   Size Id Type
    /dev/sda1            2048 258539095 258537048 123.3G  7 HPFS/NTFS/exFAT
    /dev/sda2  *    258539520 287916031  29376512    14G 83 Linux
    /dev/sda3       308383744 312580095   4196352     2G 82 Linux swap / Solaris
    /dev/sda4       287916032 308383743  20467712   9.8G 83 Linux
    
    Partition table entries are not in disk order.
    
    
    Disk /dev/sdb: 111.8 GiB, 120034123776 bytes, 234441648 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x000e061b
    
    Device     Boot    Start       End   Sectors  Size Id Type
    /dev/sdb1           2048  58595797  58593750   28G 83 Linux
    /dev/sdb2       58595798 234441647 175845850 83.9G  7 HPFS/NTFS/exFAT
    
    
    
    
    Disk /dev/sdc: 232.9 GiB, 250059350016 bytes, 488397168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: dos
    Disk identifier: 0x000c1db5
    
    Device     Boot     Start       End   Sectors   Size Id Type
    /dev/sdc1            2048 446384127 446382080 212.9G  7 HPFS/NTFS/exFAT
    /dev/sdc2       446384128 488396799  42012672    20G 83 Linux
    
    
    Disk /dev/sdd: 58.8 GiB, 63065554944 bytes, 123174912 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x00000000
    
    Device     Boot Start       End   Sectors  Size Id Type
    /dev/sdd1          32 123174911 123174880 58.8G  c W95 FAT32 (LBA)
    Code:
    dad@linux-hi7k:~> /usr/sbin/blkid
    /dev/sda1: UUID="F84ECD3B4ECCF402" TYPE="ntfs" PARTUUID="b9d6b850-01"
    /dev/sda2: UUID="fb05c33c-387e-406e-807a-a207b0b456d9" TYPE="ext4" PTTYPE="dos" PARTUUID="b9d6b850-02"
    /dev/sda3: UUID="95560983-e4b1-42a7-87b3-b2e20c8feb77" TYPE="swap" PARTUUID="b9d6b850-03"
    /dev/sda4: UUID="8cb644ab-cb4b-4b33-a40a-e2435c652c9c" TYPE="ext4" PARTUUID="b9d6b850-04"
    /dev/sdb1: LABEL="home" UUID="b0b0e582-f069-48ac-b09f-4ae5a1e23cea" TYPE="ext4" PARTUUID="000e061b-01"
    /dev/sdb2: LABEL="backups" UUID="8E3827523827391B" TYPE="ntfs" PARTUUID="000e061b-02"
    /dev/sdc1: LABEL="windows-D" UUID="420EFA6B0EFA56FF" TYPE="ntfs" PARTUUID="000c1db5-01"
    /dev/sdc2: UUID="00833188-e95f-4704-87eb-e32da51120c7" TYPE="ext4" PARTUUID="000c1db5-02"
    dad@linux-hi7k:~>
    In fdisk -l (list) above I noticed there is an sdd.
    I created a folder in /mnt named /usb and was able to manually mount that drive sdd1

    So the files are there, but the automount is still not functioning. When I plug in the device it is not registering or loading. Can we still get that fixed?


    thanks for your help.
    openSUSE Tumbleweed 64-bit / Cinnamon

  5. #5
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,704
    Blog Entries
    1

    Default Re: Cannot mount USB / doesn't automount after power crashed

    In fdisk -l (list) above I noticed there is an sdd.
    I created a folder in /mnt named /usb and was able to manually mount that drive sdd1
    That's good to know. Any errors on it?

    Code:
    Device     Boot Start       End   Sectors  Size Id Type
    /dev/sdd1          32 123174911 123174880 58.8G  c W95 FAT32 (LBA)
    So the file system is FAT32.

    So the files are there, but the automount is still not functioning. When I plug in the device it is not registering or loading. Can we still get that fixed?


    thanks for your help.
    Run the following as user
    Code:
    udisksctl monitor
    and plug in the device. Capture the output.

  6. #6

    Default Re: Cannot mount USB / doesn't automount after power crashed

    Quote Originally Posted by deano_ferrari View Post
    That's good to know. Any errors on it?

    Code:
    Device     Boot Start       End   Sectors  Size Id Type
    /dev/sdd1          32 123174911 123174880 58.8G  c W95 FAT32 (LBA)
    So the file system is FAT32.


    Run the following as user
    Code:
    udisksctl monitor
    and plug in the device. Capture the output.
    Code:
    :~> udisksctl monitor
    Monitoring the udisks daemon. Press Ctrl+C to exit.
    20:32:30.078: The udisks-daemon is running (name-owner :1.35).
    20:36:05.702: /org/freedesktop/UDisks2/drives/CT120BX100SSD1_1527F009453E: org.freedesktop.UDisks2.Drive.Ata: Properties Changed
      SmartUpdated:         1508722565
    20:36:05.806: /org/freedesktop/UDisks2/drives/SAMSUNG_HD161GJ_S1V5J9CZ300518: org.freedesktop.UDisks2.Drive.Ata: Properties Changed
      SmartUpdated:         1508722565
    20:36:05.902: /org/freedesktop/UDisks2/drives/Crucial_CT250MX2_1614123EE61E: org.freedesktop.UDisks2.Drive.Ata: Properties Changed
      SmartUpdated:         1508722565
    openSUSE Tumbleweed 64-bit / Cinnamon

  7. #7
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,704
    Blog Entries
    1

    Default Re: Cannot mount USB / doesn't automount after power crashed

    Quote Originally Posted by idee View Post
    Code:
    :~> udisksctl monitor
    Monitoring the udisks daemon. Press Ctrl+C to exit.
    20:32:30.078: The udisks-daemon is running (name-owner :1.35).
    20:36:05.702: /org/freedesktop/UDisks2/drives/CT120BX100SSD1_1527F009453E: org.freedesktop.UDisks2.Drive.Ata: Properties Changed
      SmartUpdated:         1508722565
    20:36:05.806: /org/freedesktop/UDisks2/drives/SAMSUNG_HD161GJ_S1V5J9CZ300518: org.freedesktop.UDisks2.Drive.Ata: Properties Changed
      SmartUpdated:         1508722565
    20:36:05.902: /org/freedesktop/UDisks2/drives/Crucial_CT250MX2_1614123EE61E: org.freedesktop.UDisks2.Drive.Ata: Properties Changed
      SmartUpdated:         1508722565
    1. So, nothing specific to the device reported when you plugged it in? Just to confirm that you did plug it in after the monitoring command?

    2. Run
    Code:
    dmesg --follow
    then report back with the kernel output generated when you plug the device in.

    3. Can you mount the device with udisksctl (as user)?
    Code:
    udisksctl mount -b /dev/sdd1
    Confirm that it is mounted with
    Code:
    mount|grep sdd
    or with
    Code:
    df -h
    4. How is the device seen by udev?
    Code:
    udevadm info -a -p $(udevadm info -q path -n /dev/sdd1)

  8. #8

    Default Re: Cannot mount USB / doesn't automount after power crashed

    Quote Originally Posted by deano_ferrari View Post
    1. So, nothing specific to the device reported when you plugged it in? Just to confirm that you did plug it in after the monitoring command?
    did not understand that, sorry. So when it was removed is showed:
    Code:
    21:26:36.833: Removed /org/freedesktop/UDisks2/block_devices/sdd1
    21:26:36.834: Removed /org/freedesktop/UDisks2/block_devices/sdd
    when I plugged it back in, nothing.

    I am running the other tests now. Will reply in a minute.
    openSUSE Tumbleweed 64-bit / Cinnamon

  9. #9

    Default Re: Cannot mount USB / doesn't automount after power crashed

    Quote Originally Posted by deano_ferrari View Post
    1. So, nothing specific to the device reported when you plugged it in? Just to confirm that you did plug it in after the monitoring command?
    It took awhile, but it looks like it may have shown up:
    Code:
    21:32:47.459: Added /org/freedesktop/UDisks2/block_devices/sde
      org.freedesktop.UDisks2.Block:
        Configuration:              []
        CryptoBackingDevice:        '/'
        Device:                     /dev/sde
        DeviceNumber:               2112
        Drive:                      '/'
        HintAuto:                   false
        HintIconName:               
        HintIgnore:                 false
        HintName:                   
        HintPartitionable:          true
        HintSymbolicIconName:       
        HintSystem:                 true
        Id:                         
        IdLabel:                    
        IdType:                     
        IdUUID:                     
        IdUsage:                    
        IdVersion:                  
        MDRaid:                     '/'
        MDRaidMember:               '/'
        PreferredDevice:            /dev/sde
        ReadOnly:                   false
        Size:                       63065554944
        Symlinks:                   
      org.freedesktop.UDisks2.PartitionTable:
        Type:

    Quote Originally Posted by deano_ferrari View Post
    2. Run
    Code:
    dmesg --follow
    then report back with the kernel output generated when you plug the device in.
    Results below:
    Code:
     new high-speed USB device number 71 using ehci-pci
    [344783.708023] usb 1-6: new high-speed USB device number 72 using ehci-pci
    [344783.840929] usb 1-6: New USB device found, idVendor=0781, idProduct=5530
    [344783.840933] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [344783.840935] usb 1-6: Product: Cruzer
    [344783.840936] usb 1-6: Manufacturer: SanDisk
    [344783.840938] usb 1-6: SerialNumber: 4C530099920808110214
    [344783.841233] usb-storage 1-6:1.0: USB Mass Storage device detected
    [344783.841759] scsi host7: usb-storage 1-6:1.0
    [344784.324023] usb 1-5: new high-speed USB device number 74 using ehci-pci
    [344784.632024] usb 1-5: new high-speed USB device number 75 using ehci-pci
    [344784.841090] scsi 7:0:0:0: Direct-Access     SanDisk  Cruzer           1.00 PQ: 0 ANSI: 6
    [344784.841439] sd 7:0:0:0: Attached scsi generic sg4 type 0
    [344784.842446] sd 7:0:0:0: [sde] 123174912 512-byte logical blocks: (63.1 GB/58.7 GiB)
    [344784.843943] sd 7:0:0:0: [sde] Write Protect is off
    [344784.843947] sd 7:0:0:0: [sde] Mode Sense: 43 00 00 00
    [344784.844966] sd 7:0:0:0: [sde] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    [344784.861839]  sde: sde1
    [344784.865687] sd 7:0:0:0: [sde] Attached SCSI removable disk
    [344784.996021] usb 1-5: new high-speed USB device number 76 using ehci-pci
    Quote Originally Posted by deano_ferrari View Post
    3. Can you mount the device with udisksctl (as user)?
    Code:
    udisksctl mount -b /dev/sdd1
    Confirm that it is mounted with
    Code:
    mount|grep sdd
    or with
    Code:
    df -h
    Results below:
    Code:
    :~> udisksctl mount -b /dev/sde1
    Object /org/freedesktop/UDisks2/block_devices/sde is not a mountable filesystem.
    dad@linux-hi7k:~> udisksctl mount -b /dev/sde1
    Code:
    :~> mount|grep sde
    /dev/sde1 on /run/media/dad/A6E0-9781 type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=100,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)

    Quote Originally Posted by deano_ferrari View Post
    4. How is the device seen by udev?
    Code:
    udevadm info -a -p $(udevadm info -q path -n /dev/sdd1)
    Results below:


    I changed to a different port and is showed up. Figure that?
    openSUSE Tumbleweed 64-bit / Cinnamon

  10. #10
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,704
    Blog Entries
    1

    Default Re: Cannot mount USB / doesn't automount after power crashed

    Quote Originally Posted by idee View Post
    It took awhile, but it looks like it may have shown up:
    Code:
    21:32:47.459: Added /org/freedesktop/UDisks2/block_devices/sde
      org.freedesktop.UDisks2.Block:
        Configuration:              []
        CryptoBackingDevice:        '/'
        Device:                     /dev/sde
        DeviceNumber:               2112
        Drive:                      '/'
        HintAuto:                   false
        HintIconName:               
        HintIgnore:                 false
        HintName:                   
        HintPartitionable:          true
        HintSymbolicIconName:       
        HintSystem:                 true
        Id:                         
        IdLabel:                    
        IdType:                     
        IdUUID:                     
        IdUsage:                    
        IdVersion:                  
        MDRaid:                     '/'
        MDRaidMember:               '/'
        PreferredDevice:            /dev/sde
        ReadOnly:                   false
        Size:                       63065554944
        Symlinks:                   
      org.freedesktop.UDisks2.PartitionTable:
        Type:
    The above output isn't complete.....at least it shows the device was handled by udisks though.

    Results below:
    Code:
    :~> udisksctl mount -b /dev/sde1
    Object /org/freedesktop/UDisks2/block_devices/sde is not a mountable filesystem.
    dad@linux-hi7k:~> udisksctl mount -b /dev/sde1
    Code:
    :~> mount|grep sde
    /dev/sde1 on /run/media/dad/A6E0-9781 type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=100,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)
    It does mount ok... perhaps when you plugged in to a USB 2.0 port?

    I changed to a different port and is showed up. Figure that?
    Do you have a mixture of ISB 2.0 (EHCI) ports and USB 3.0 (XHCI) ports perhaps?

Posting Permissions

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