Can not access my second drive

Support & Help Requests
#1

0

I have a second drive, sdb with 3 partitions.

Here is what my desktop looks like. SDB1,SDB2,and SDB5 are not there?

Which means I can not access anything on that drive.

SDB_Not_Mounted
SDB_Not_Mounted.png1920×1080 213 KB

Fstab
Fstab.png1920×1080 94.5 KB

#2

Hallo fixit7

You might want to try and see if the tool "nmon" can see the drive:

If you post what you are able to see with nmon one of the wise (i.e. not me) may be better able to localise your problem. :thinking:

#3

/etc/fstab doesn't list your second drive...

What does sudo fdisk -l or sudo lsblk give?

#4

You won't find them in your home directory. It looks like fstab attempts to mount the 3 partitions at:

/SDB1_Mountpoint
/SDB2_Mountpoint
/SDB5_Mountpoint

Or I'm missing something. There's many reasons they may not mount properly. Those last 3 fstab lines look manually added to mount this (or some) specific drive with 3 partitions.

And look for these mount points in Caja's "File System".

EDIT: Oooops, the 'noauto' option complicates things a bit. Comment out those last 3 fstab lines so this drive can be mounted by Caja.

1 Like
#5

Disk /dev/loop0: 86.9 MiB, 91099136 bytes, 177928 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

Disk /dev/loop1: 91 MiB, 95416320 bytes, 186360 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

Disk /dev/loop2: 87.3 MiB, 91504640 bytes, 178720 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

Disk /dev/loop3: 34.8 MiB, 36503552 bytes, 71296 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

Disk /dev/loop4: 7.9 MiB, 8294400 bytes, 16200 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

Disk /dev/loop5: 53.7 MiB, 56287232 bytes, 109936 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

Disk /dev/loop6: 143.2 MiB, 150179840 bytes, 293320 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

Disk /dev/loop7: 71.7 MiB, 75120640 bytes, 146720 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

Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 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: 0x87fb6afb

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 3907028991 3907026944 1.8T 83 Linux

Disk /dev/sdb: 298.1 GiB, 320072933376 bytes, 625142448 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: 0x000f0791

Device Boot Start End Sectors Size Id Type
/dev/sdb1 418846720 625141759 206295040 98.4G 83 Linux
/dev/sdb2 2048 211812351 211810304 101G 83 Linux
/dev/sdb3 211814398 418846719 207032322 98.7G 5 Extended
/dev/sdb5 216240128 418846719 202606592 96.6G 83 Linux

Partition table entries are not in disk order.

Disk /dev/loop8: 86.7 MiB, 90923008 bytes, 177584 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

#6 
/SDB1_Mountpoint
/SDB2_Mountpoint
/SDB5_Mountpoint

Those 3 are folders I made for the mountpoint.

#7

After commenting out the last 3 lines, the drives show up in Caja.

Caja shows sdb1 as

   /media/andy/MAXTOR_SDB1
#8

If you reinstate those 3 fstab lines and remove the 'noauto' option, those drives should be mounted in those folders.

Those fstab lines take care of those drives which is why Caja won't handle them until those lines are commented out.

#9

Thanks Bill. I made those changes.

The drive does mount even if they do not show up in desktop, thunar, or caja.

I use this to access them.

   thunar /SDB1_Mountpoint/Ubuntu_Mate_18.04/
#10

They are behaving as expected. File managers like Caja only list them when Caja mounts them. When mounted via fstab, they simply blend in with the file system.

Under the hood, the mounts are quite different. Caja and Thunar use FUSE (File system in User Space or something like that) while fstab is system wide and arranged by root.

1 Like