[SLOVED] Unable to find mount point

[dylan420]

 Device Boot      Start         End      Blocks   Id  System                                                                                              
/dev/sda1   *           1         268     2152678+  83  Linux                                                                                                
/dev/sda2             269         536     2152710   82  Linux swap / Solaris                                                                                
/dev/sda3             537        4105    28667992+  83  Linux                                                                                                
/dev/sda4            4106       30402   211224987+   5  Extended                                                                                            
/dev/sda5            4106       24502   163838871   83  Linux                                                                                                
/dev/sda6           24503       27052    20482843+  83  Linux                                                                                                
/dev/sda7           27053       30402    26903178+  83  Linux
When I boot PCLinuxOS, login as user and open any file manager, the other partitions appear in the side pane on the left of the window. However, when i click on "FILE DRIVE" a message at the bottom appears "The file or folder /media/File Drive does not exist." When I open gparted, right click on the partition "FILE DRIVE" and click "Information" A message at the bottom appears.
 "Warning: Unable to find mount point
Unable to read contents of this file system!. Because of this some operations may be unavailable. The following list of software packages is required for ext4 file system support: e2fsprogs v1.41+."

I have checked in synaptic and e2fsprogs version 1.41 is already installed.
Perhaps I made a mistake when installing the Operating systems. I didnt specify anything as a mount point.
What should the mount point be on the drives used for long term data?

[uncleV]

Hi, dylan420!

Some things to try while waiting for the experts to pop up:

Give your FILE DRIVE partition another label so there's no white space in the name, e.g. FILE_DRIVE or something else.

Find an additional info about static and dynamic mount points respectively in the files /etc/fstab and etc/mtab. My be you'll have to open them with root privileges. Post their content here for the experts to look at

[dylan420]

etc/fstab>
# Entry for /dev/sda3 :
UUID=0b8f7686-51bf-4fbe-b6e2-48c36997889b / ext4 defaults 1 1
# Entry for /dev/sda1 :
UUID=f4e563cf-76bc-46b0-bccc-07318be73403 /boot ext3 defaults 1 2
none /proc proc defaults 0 0
# Entry for /dev/sda2 :
UUID=32fdb8b1-3206-4c71-bbfc-ee3a6c1febbf swap swap defaults 0 0
none /dev/pts devpts defaults 0 0

etc/mtab>
/dev/sda3 / ext4 rw 0 0
none /proc proc rw 0 0
none /dev/pts devpts rw 0 0
/dev/sda1 /boot ext3 rw 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
/dev/sda5 /media/FILE\040DRIVE ext4 rw,nosuid,nodev,uhelper=hal 0 0
/dev/sda6 /media/RECOVERY\040DRIVE ext4 rw,nosuid,nodev,uhelper=hal 0 0
/dev/sda7 /media/BT4 ext3 rw,nosuid,nodev,uhelper=hal 0 0
gvfs-fuse-daemon /home/hollow45/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,user=hollow45 0 0

[uncleV]

Just a thought...
There in mtab labels of sda5 + sda6 combined give the label under question "FILE RECOVERY".
There is a backslash \ in those lines that Linux doesn't use in its file structure.

[dylan420]

Thank-You kindly, the information you provided solved the problem. Great observation, the untrained eye wouldn't have caught that.
I changed the label on one of the partitions. I rebooted and the following line changed in etc/mtab>
/dev/sda6 /media/RECOVERY ext4 rw,nosuid,nodev,uhelper=hal 0 0
The partition editor and the file manager now report no errors on the drive with no blank spaces in the label.

[uncleV]

So no need of experts.

See? Two noobs together give a perfect half of an expert.
Just imagine what it would be if 16 noobs together were solving this problem...

        

[Bald Brick]

Just a thought...
There in mtab labels of sda5 + sda6 combined give the label under question "FILE RECOVERY".
There is a backslash \ in those lines that Linux doesn't use in its file structure.

You are right, of course. I'd just like to add that even if the backslash isn't used as a separator in the Linux file structure, it may be useful as an escape character.

Let's say you have a folder called "my folder" in your home directory. The command

Code: [Select]

ls my folder wont work. The shell will interpret the space between "my" and "folder" as a delimiter and start by looking for a directory called "my". To make it realize that the name of the folder is actually "my folder", you could type the name precisely like that, within quotes:

Code: [Select]

ls "my folder"
Or you could use the escape character "\" before the space instead. The backslash will make the shell interpret the space as just a space and not a delimiter:

Code: [Select]

ls my\ folderwill work correctly.

The \040 in dylan420's mtab is an example of an escape sequence of a different kind. In some programming languages it would also stands for a space (octal 40, decimal 32). This time it didn't work, which makes one suspect that his partitions hadn't been labelled in Linux.

And then the backslash is useful if you want to let the shell know that two consecutive lines should be interpreted as a single line.

Or try entering "echo uncle\" in a terminal, and hit Enter. You'll get the promt ">".

Then enter "V" and hit Enter again:

Code: [Select]

$ echo uncle\                                                                                                                                      
> V                                                                                                                                                                  
uncleV
So sometimes the backslash may have its place in Linux too.

[uncleV]

Thank you, Bald Brick, for the brief tutorial on escape sequences. Long-long ago in DOS times I read about it and was impressed how many tricks one can do with esc. sequences.

And here your example works too but in another manner:

[uncleV@localhost ~]$ echo Bald\
>  Brick
Black Bird
[uncleV@localhost ~]$

[Bald Brick]

Hehehe!