Can't access second drive

M_Mynaardt · 2011-08-07 02:29:15

Hi there!

I've installed #! Xfce on my desktop machine. So far so good. Except I can't seem to access my second drive. If I use the disk manager, I can find it, format it and all the rest of it. But for some reason, I can't seem to access it through the file manager (either Thunar or Nautilus).

Anyone know of a fix up for that? Preferably an easy one, of course!

Thanks!

anonymous · 2011-08-07 02:37:52

Im guessing this second drive is internal? First you have to mount it then you just use the file manager to access its mount point (like /media/MYDISK or whatever).

To have the disk automount on boot, you can add it to your fstab. An easy way to do this is install and run disk-manager:

sudo apt-get install disk-manager
gksudo disk-manager

It will ask to configure your drive, just answer Yes or OK.

M_Mynaardt · 2011-08-07 22:46:05

anonymous wrote:

Im guessing this second drive is internal? First you have to mount it then you just use the file manager to access its mount point (like /media/MYDISK or whatever).
To have the disk automount on boot, you can add it to your fstab. An easy way to do this is install and run disk-manager:
sudo apt-get install disk-manager
gksudo disk-manager
It will ask to configure your drive, just answer Yes or OK.

Yes, sorry, the second drive is internal.

I tried what you said; configuring the drive and all that. However, still no auto detect. But I noticed that in disk-manager when I select my second drive, in the advanced configuration options, there is the following text:

defaults,nosuid,nodev,uhelper=udisks

and the option to check the device every 30 boots is not checked.

Should I change any of that? Or should I edit something in that fstab business?

Thanks!

psyco430404 · 2011-08-07 22:49:06

Thunar doesn't handle internal drive mounting, what anonymous said to do was mount it with disk manager then go to its mount point in media and bookmark it so you'll have easy access.

And no you wont have to change anything just use disk manager to mount it then click file save and it will auto mount from that point on when you boot big_smile .

Last edited by psyco430404 (2011-08-07 22:49:48)

munchen800 · 2011-08-08 01:40:41

If it is internal just add it to the fstab

make a mount point

sudo mkdir /mnt/drive2(you can name whatever you want)

then open fstab

sudo nano /etc/fstab

then add at the bottom

/dev/(device)    /mnt/(your mount point here)    ext3    defaults    0    2

to find the device just

ls /dev

internal hdd are normally sd(letter)(number) or hd(letter)(number) example..... sda1 hdb2
the primary hdd prol has the swap on it
if it does you will see like sda1 sda2 sda3
the second hdd will prol only have one like sdb1

once you do that just restart and it will automount on boot so just open /mnt/(your mount point name)

hope it helped

M_Mynaardt · 2011-08-09 01:27:18

munchen800 wrote:

If it is internal just add it to the fstab
make a mount point
sudo mkdir /mnt/drive2(you can name whatever you want)
then open fstab
sudo nano /etc/fstab
then add at the bottom
/dev/(device)    /mnt/(your mount point here)    ext3    defaults    0    2
to find the device just
ls /dev
internal hdd are normally sd(letter)(number) or hd(letter)(number) example..... sda1 hdb2
the primary hdd prol has the swap on it
if it does you will see like sda1 sda2 sda3
the second hdd will prol only have one like sdb1
once you do that just restart and it will automount on boot so just open /mnt/(your mount point name)
hope it helped

Still no joy! sad

I tried all that and all I got was an ability to see /dev/mydrive . And even then, I couldn't actually do anything with it, like save files.

Anything else that might work?

anonymous · 2011-08-09 01:45:07

Did you edit your fstab file either manually or using disk-manager? If so what did you use as the mount point?

The mount point is usually something like /media/disk or /mnt/disk. The mount is where you can access your files and whatnot.

M_Mynaardt · 2011-11-09 05:32:37

anonymous wrote:

Did you edit your fstab file either manually or using disk-manager? If so what did you use as the mount point?
The mount point is usually something like /media/disk or /mnt/disk. The mount is where you can access your files and whatnot.

Sorry it's been ages since I looked at this thread; but working nights is my excuse...

Just today I found out about and installed disk-manager to see if that could auto mount my secondary internal drive. It sort of did. It did all the changed the contents of /etc/fstab and when I restarted #!, the secondary drive was mounted as /media/driveX. Unfortunately it was read only status requiring root access.

So, it's almost there. How should I change its /etc/fstab entry to allow normal user permission access to that drive once mounted as /media/driveX? Just so I can read/write as if it were a normal folder. I just want to be able to use that directory as a back up for data sort of thing...

Thanks...

anonymous · 2011-11-09 05:37:13

If your drive is NTFS, make sure you have ntfs-3g installed.

M_Mynaardt · 2011-11-09 05:45:49

anonymous wrote:

If your drive is NTFS, make sure you have ntfs-3g installed.

Actually, it's formatted as ext4. That much shows up when I look at disk-manager or GParted.

There's probably a (relatively) simple fix to this, that's easy to overlook...

It just seems strange that There's no problem accessing USB hard drives with #! Xfce, but this extra internal drive does seem to be a bit of a poser...
sad

anonymous · 2011-11-09 05:47:27

Did you check folder/file permissions for your ext4 drive?

M_Mynaardt · 2011-11-09 05:49:31

anonymous wrote:

Did you check folder/file permissions for your ext4 drive?

I checked the permissions in Thunar and it indicated "read only". Do I need to tinker with something else in GParted?

Or should I reformat that drive, perhaps? There's virtually nothing on it anyway...

machinebacon · 2011-11-09 06:01:48

Hi,

first use sudo blkid to find the device names (UUID)
then add the it to /etc/fstab

UUID=THE_NUMBER_WITHOUT_"    /mnt/the_other_drive      ext4    defaults      0    0

then do a sudo mount -a and everything is fine.

Edit: Ah sorry, misread big_smile

Last edited by machinebacon (2011-11-09 06:02:43)

M_Mynaardt · 2011-11-09 16:27:57

machinebacon wrote:

Hi,
first use sudo blkid to find the device names (UUID)
then add the it to /etc/fstab
UUID=THE_NUMBER_WITHOUT_"    /mnt/the_other_drive      ext4    defaults      0    0
then do a sudo mount -a and everything is fine.
Edit: Ah sorry, misread

Well! I think I see what might be a problem. I ran blkid as you suggested. And the following was the result:

:~$ blkid
/dev/sdb1: LABEL="driveX" UUID="NUMBERS_ONE"TYPE="ext4" 
/dev/sda1: LABEL="driveX" UUID="NUMBERS_TWO"TYPE="ext4"

But the thing is, both drives are showing with the same label! They shouldn't both have the same label, should they?

I remember doing something long ago to assign the label "driveX" to the extra drive (I forgot how I did it now), but I don't know how they could have both been given the same label.

At least I know the OS can find both drives! Now all I have to do something right to access the extra one.
hmm

anonymous · 2011-11-10 04:08:57

You can use GParted to change the label of one of the drives/partitions.

The Core · 2012-07-09 22:45:41

I know this thread is a bit dated but this issue is almost identical to my situation. I encountered the same problem as M_Mynaardt and have followed the steps outlined but no joy... yet.

'anonymous' gave a really good help thread but I just can't write to my new drive. I'm missing something. Here is my fstab file content after adding the last line for my new drive and commenting out the line before it which was automatically generated for the new drive:
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sde1 during installation
UUID=8f7cb7fa-6daa-429c-aa8c-d913e03824d1 / ext4 errors=remount-ro 0 1
# swap was on /dev/sde2 during installation
UUID=08487a46-eafd-4c0d-88ef-5c52fc681c2e none swap sw 0 0
# /dev/sdf1 /media/LinuxUBNT1 ext4 users,user,owner 0 0
UUID=472d170c-4c57-4528-8bad-04cc4c8cdeca /media/LinuxUBNT1/Ubuntu1204A ext4 defaults 0 0

I created a new folder and set it as mount point called Ubuntu1204A. I created it with command line and I can see it using:
~$ ls /media/LinuxUBNT1
Ubuntu1204A

When I open the drive called LinuxUBNT1 I can only see the lost+found folder.

My goal is to install Ubuntu in a VMPlayer virtual machine. When I try to browse to the new drive in VMPlayer and select it, I get an error message that I do not have permission.

I've been reading many forum posts for the last 4 days and have tried all sorts of suggestions. This thread is the clearest (I am a novice) that I have found and feel like I am close to success, but close only counts in horse shoes and grenades.

I'm hoping someone will see this post and also see what I am doing wrong.

Last edited by The Core (2012-07-11 00:59:24)

CBizgreat! · 2012-07-11 15:47:39

Sounds like chown could be what you're after. ( CH-ange OWN-er)

Either as root ( #) or w sudo ... ie: sudo chown -R yourusername /media/LinuxUBNT1

Babble Link related.

The Core · 2012-07-12 01:55:43

Thank you CBizgreat. I can see the drive and the folder I created to use as mount point but when I browse to that folder in VMPlayer it is not displayed. Here is what I did:

corevm001@corevm001-System-Product-Name:/media/LinuxUBNT1$ sudo umount /media/LinuxUBNT1/Ubuntu1204A
corevm001@corevm001-System-Product-Name:/media/LinuxUBNT1$ sudo chown -R corevm001 /media/LinuxUBNT1/Ubuntu1204A
corevm001@corevm001-System-Product-Name:/media/LinuxUBNT1$ sudo mount /media/LinuxUBNT1/Ubuntu1204A
corevm001@corevm001-System-Product-Name:/media/LinuxUBNT1$ dir
Ubuntu1204A
corevm001@corevm001-System-Product-Name:/media/LinuxUBNT1$ sudo ls -l
total 4
drwxr-xr-x 3 corevm001 root 4096 Jul 9 14:11 Ubuntu1204A

UPDATE:

I just got some advice to enter the following and it worked:
mkdir -p /media/LinuxUBNT1/Ubuntu1204A

Last edited by The Core (2012-07-12 03:12:20)

CrunchBang Linux

SEARCH

#1 2011-08-07 02:29:15

Can't access second drive

#2 2011-08-07 02:37:52

Re: Can't access second drive

#3 2011-08-07 22:46:05

Re: Can't access second drive

#4 2011-08-07 22:49:06

Re: Can't access second drive

#5 2011-08-08 01:40:41

Re: Can't access second drive

#6 2011-08-09 01:27:18

Re: Can't access second drive

#7 2011-08-09 01:45:07

Re: Can't access second drive

#8 2011-11-09 05:32:37

Re: Can't access second drive

#9 2011-11-09 05:37:13

Re: Can't access second drive

#10 2011-11-09 05:45:49

Re: Can't access second drive

#11 2011-11-09 05:47:27

Re: Can't access second drive

#12 2011-11-09 05:49:31

Re: Can't access second drive

#13 2011-11-09 06:01:48

Re: Can't access second drive

#14 2011-11-09 16:27:57

Re: Can't access second drive

#15 2011-11-10 04:08:57

Re: Can't access second drive

#16 2012-07-09 22:45:41

Re: Can't access second drive

#17 2012-07-11 15:47:39

Re: Can't access second drive

#18 2012-07-12 01:55:43

Re: Can't access second drive

Board footer