como montar automaticamente um disco rígido externo para o nautilus?

Question

Depois de usar unetbootin para instalar uma imagem iso em um portátil hdd recinto de disco não consigo visualizar ou montar a unidade através do nautilus.

Como posso tornar a unidade visível no nautilus? Ele mostra em fdisk as sdb1 :

thufir@doge:~$ 
thufir@doge:~$ sudo fdisk -l
Disk /dev/sda: 74.5 GiB, 80026361856 bytes, 156301488 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: 0x3b9b7b5e

Device     Boot Start       End   Sectors  Size Id Type
/dev/sda1  *     2048 156301311 156299264 74.5G 83 Linux


Disk /dev/sdb: 55.9 GiB, 60011642880 bytes, 117210240 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: 0xe833c75e

Device     Boot Start       End   Sectors  Size Id Type
/dev/sdb1        2048 117210239 117208192 55.9G 83 Linux
thufir@doge:~$ 

não há nada de valor no disco. Anteriormente, apenas mostrava no nautilus. Executando nautilus com sudo mostra:

nãotenhocertezaseéodiscorígidoexternoounão.Ocomandotailmostra:

thufir@doge:~$thufir@doge:~$sudotail-f/var/log/syslogAug1720:51:23dogecompiz[1919]:console.error:Aug1720:51:23dogecompiz[1919]:Message:TypeError:can'taccessdeadobjectAug1720:51:23dogecompiz[1919]:Stack:Aug1720:51:23dogecompiz[1919]:load_into_window@resource://gre/modules/commonjs/toolkit/loader.js->resource://jid1-qofqdk4qzufgwq-at-jetpack/lib/process-script.js:82:1Aug1720:51:23dogecompiz[1919]:load_into_window/<@resource://gre/modules/commonjs/toolkit/loader.js->resource://jid1-qofqdk4qzufgwq-at-jetpack/lib/process-script.js:107:28Aug1720:51:23dogecompiz[1919]:notify@resource://gre/modules/commonjs/toolkit/loader.js->resource://gre/modules/commonjs/sdk/timers.js:40:9Aug1720:51:54dogeevolution-sourc[1733]:secret_service_search_sync:mustspecifyatleastoneattributetomatchAug1720:54:31dogekernel:[3978.343635]usb2-4:USBdisconnect,devicenumber3Aug1720:54:44dogegnome-terminal-[2145]:AllocatingsizetoGtkBox0x55f9dac41cc0withoutcallinggtk_widget_get_preferred_width/height().Howdoesthecodeknowthesizetoallocate?Aug1720:54:53dogesudo:pam_ecryptfs:pam_sm_authenticate:/home/thufirisalreadymountedAug1720:55:18dogekernel:[4025.412231]usb2-4:newhigh-speedUSBdevicenumber4usingehci-pciAug1720:55:18dogekernel:[4025.561533]usb2-4:NewUSBdevicefound,idVendor=13fd,idProduct=1040Aug1720:55:18dogekernel:[4025.561538]usb2-4:NewUSBdevicestrings:Mfr=1,Product=2,SerialNumber=3Aug1720:55:18dogekernel:[4025.561542]usb2-4:Product:MHT2060ATAug1720:55:18dogekernel:[4025.561545]usb2-4:Manufacturer:InitioAug1720:55:18dogekernel:[4025.561548]usb2-4:SerialNumber:0000000000000000WAug1720:55:18dogekernel:[4025.562007]usb-storage2-4:1.0:USBMassStoragedevicedetectedAug1720:55:18dogekernel:[4025.562545]scsihost5:usb-storage2-4:1.0Aug1720:55:18dogemtp-probe:checkingbus2,device4:"/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-4"
Aug 17 20:55:18 doge mtp-probe: bus: 2, device: 4 was not an MTP device
Aug 17 20:55:19 doge kernel: [ 4026.593256] scsi 5:0:0:0: Direct-Access     Initio   MHT2060AT        1.06 PQ: 0 ANSI: 0
Aug 17 20:55:19 doge kernel: [ 4026.594950] sd 5:0:0:0: Attached scsi generic sg2 type 0
Aug 17 20:55:19 doge kernel: [ 4026.595731] sd 5:0:0:0: [sdb] 117210240 512-byte logical blocks: (60.0 GB/55.9 GiB)
Aug 17 20:55:19 doge kernel: [ 4026.596800] sd 5:0:0:0: [sdb] Write Protect is off
Aug 17 20:55:19 doge kernel: [ 4026.596806] sd 5:0:0:0: [sdb] Mode Sense: 23 00 00 00
Aug 17 20:55:19 doge kernel: [ 4026.597906] sd 5:0:0:0: [sdb] No Caching mode page found
Aug 17 20:55:19 doge kernel: [ 4026.597917] sd 5:0:0:0: [sdb] Assuming drive cache: write through
Aug 17 20:55:19 doge kernel: [ 4026.611118]  sdb: sdb1
Aug 17 20:55:19 doge kernel: [ 4026.616302] sd 5:0:0:0: [sdb] Attached SCSI disk

não é possível montar explicitamente:

thufir@doge:~$ 
thufir@doge:~$ sudo mount -t ext3 /dev/sdb1 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
thufir@doge:~$ 
thufir@doge:~$ dmesg | tail
[38425.298930]  entry_SYSCALL_64_fastpath+0x1e/0xad
[38425.298932] RIP: 0033:0x7f32d242e987
[38425.298934] RSP: 002b:00007fffd3152ed8 EFLAGS: 00003246 ORIG_RAX: 0000000000000010
[38425.298936] RAX: ffffffffffffffda RBX: 000055ce5c648670 RCX: 00007f32d242e987
[38425.298938] RDX: 00007fffd3152f10 RSI: 00000000c05064a7 RDI: 000000000000000e
[38425.298939] RBP: 00007fffd3152f10 R08: 000055ce5c648720 R09: 0000000000000000
[38425.298941] R10: 0000000000000000 R11: 0000000000003246 R12: 00000000c05064a7
[38425.298942] R13: 000000000000000e R14: 00007fffd3152f10 R15: 000000000000000e
[38425.298944] ---[ end trace 71aae897cab69e2e ]---
[38737.380862] EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
thufir@doge:~$ 

embora mostre com fdisk -l ...