partition mount point name change

[redmk2]

I'm actually not completely comfortable with my terminal skills so I mix resources. I copy the terminal output, paste/save it in a text editor. I get the error from this forum when I try to upload the attachment. Maybe it's because I didn't append txt to the filename.

Just cut command (right click>>copy) and paste in the open terminal at the prompt (Use shift-insert to past the command). Then hit enter. The file will be created in you home directory. Try and upload that file.

[redmk2]

i've had this happen to me with an external fat32 usb drive. not sure why it happens but when I notice it upon a computer restart, i'll unmount the one with the underscore and unplug it (usb plug or turn the power off), check the contents of the folder without the underscore, it's always empty, then i'll delete that folder, then i'll just either plug it back in or flip the power switch and it gets mounted to a automatically created folder without the underscore.

I dont know why it happens but it does randomly

Nautilus creates a mount point for all the USB connected drives that are not mounted via fstab. If the drive is not cleanly unmounted (power cut, unplugged, etc.) it leaves the mount point. If you label the partition then Nautilus uses that label as the name of the directory created and used as the mount point. If not it should use the UUID.

[unibroker]

Just cut command (right click>>copy) and paste in the open terminal at the prompt (Use shift-insert to past the command). Then hit enter. The file will be created in you home directory. Try and upload that file.

I appended ".txt" and it uploaded. I edited that response.

[redmk2]

I appended ".txt" and it uploaded. I edited that response.

Attached to ??? I don't see any attachment. Possibly somewhere else?

Edit: I see it now.

[unibroker]

Attached to ??? I don't see any attachment. Possibly somewhere else?

The original post where I asked for suggestions. The resulting text file still gives me headaches just looking at it. Data isn't even showing up under the proper column heading.

[oldfred]

Someone else had the same issue with too much white space. I think he never really resolved it but later it worked. Must be some difference in versions?

just run this but it is harder to read. But if you have not labeled anything then it really does not matter. I was just trying to show labels.

sudo blkid

[redmk2]

Someone else had the same issue with too much white space. I think he never really resolved it but later it worked. Must be some difference in versions?

just run this but it is harder to read. But if you have not labeled anything then it really does not matter. I was just trying to show labels.

sudo blkid

I have reformatted the file myself. Not so hard to do.

The 2 partitions are on the device sdf. There is also a swap partition on that device too. The 2 partitions we are talking about are

sdf2   ext4  /media/6e9ac323-45f6-4cb0-acca-8277530a3584_  6e9ac323-45f6-4cb0-acca-8277530a3584

sdf5   ntfs   HP Pocket Media Drive  /media/HP Pocket Media Drive_  08EC8654EC863BC6

The mount points are blue and the UUID is red.

If these are not mounted in fstab then you can unmount the devices and delete the mount points and new ones will be created. I agree with @ oldfred that the label for the HP Pocket Media drive should be shorter and with no spaces. Maybe: hp__usb_drive.

We should check first to make sure these are not mounted via the fstab file. You can provide the output like this

cat /etc/fstab > fstab.txt

Past that output here.

[unibroker]

We should check first to make sure these are not mounted via the fstab file. You can provide the output like this

cat /etc/fstab > fstab.txt

Past that output here.

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda6 during installation
UUID=a9320513-c32b-4ce2-b66f-f83f083cedd5 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda7 during installation
UUID=d4ec1efb-06cd-4472-b540-e5d797f76846 /home ext4 defaults 0 2
# swap was on /dev/sda5 during installation
UUID=d2acd6bd-8ba2-4f5b-bfa8-f268071a6b9a none swap sw 0 0
# swap was on /dev/sdf6 during installation
UUID=bdf866d0-4891-4bc7-9595-94069089e763 none swap sw 0 0

[redmk2]

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda6 during installation
UUID=a9320513-c32b-4ce2-b66f-f83f083cedd5 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda7 during installation
UUID=d4ec1efb-06cd-4472-b540-e5d797f76846 /home ext4 defaults 0 2
# swap was on /dev/sda5 during installation
UUID=d2acd6bd-8ba2-4f5b-bfa8-f268071a6b9a none swap sw 0 0
# swap was on /dev/sdf6 during installation
UUID=bdf866d0-4891-4bc7-9595-94069089e763 none swap sw 0 0

You are not mounting the 2 partitions with fstab. This means you can unmount the partition in question and delete the mount point safely. The mountpoint will be recreated when you either: enter this command

mount -a

...or you reboot the OS.

I see there is a 2nd swap partition on this removable disk. Did you do this on purpose? I have highlighted it in red above.

[unibroker]

You are not mounting the 2 partitions with fstab. This means you can unmount the partition in question and delete the mount point safely. The mountpoint will be recreated when you either: enter this command

mount -a

...or you reboot the OS.

I see there is a 2nd swap partition on this removable disk. Did you do this on purpose? I have highlighted it in red above.

I did not. The only thing I've done purposely with the external drive is shrink the Windows partion to create the linux partition. I've never used nor intended to use the external drive to boot from so I was surprised when a swap partition was present. I'll recapture it when I need the space.

By the way, what does

errors=remount-ro 0 1

in reference to the root partition of the main hard drive mean? Thanks for your input today.