Communities

The Great Outdoors

Photography & Video

Scientific Speculation

Electrical Engineering

Languages & Linguistics

Software Development

Community Proposals

tag:snake search within a tag

answers:0 unanswered questions

user:xxxx search by author id

score:0.5 posts with 0.5+ score

"snake oil" exact phrase

votes:4 posts with 4+ votes

created:<1w created < 1 week ago

post_type:xxxx type of post

Notifications

Mark all as read See all your notifications »

Q&A

Posts Tags Edits

Comments on Secondary internal disk is mounted as an external disk

Parent

Secondary internal disk is mounted as an external disk

+2

−0

I just installed an SSD into my motherboard's third M.2 slot. After I booted up the computer, the secondary disk is now displayed like an externally connected one. There's an icon for it on the desktop, in the dock, and I can unmount it wherever I find the icon. If I drag files and folders between the disks in Nautilus, they are copied, not moved. I assume the OS should not treat an internal disk like this.

Screenshot of the disk icon on the desktop Screenshot of the disk present in the dock

Screenshot of both the disks in Nautilus, displaying a mounting location and an eject button for the secondary one

Additionally, there's an "unmount" action in the context menu for "Secondary 0", but not "Computer". I'd show a screenshot, but taking a screenshot doesn't work while Nautilus is presenting a context menu.

If this is not how internal disks are supposed to be handled, why is it happening? How do I fix it? If, on the other hand, it is by design, how do I make it not appear like an external one?

The disk already contained data that I need, when I installed it, and that is more data than I can move to the main disk, so any sort of reformatting is out of question.

gnome disk-usage PopOS pop-22.04

posted 3 months ago

CC BY-SA 4.0

3mo ago

Andreas witnessed the end of the world today‭

176 reputation 14 4 34 19

Raw

Markdown

is a duplicate

This question has been asked before and has already been answered. It should be marked as a duplicate.

Please enter the URL of the proposed duplicate in the details field below.

not constructive

This question cannot be answered in a way that is helpful to anyone. It's not possible to learn something from possible answers, except for the solution for the specific problem of the asker.

0 comment threads

Post

+1

−0

Worked for Andreas witnessed the end of the world today‭

The following users marked this post as Works for me:

User	Comment	Date
Andreas witnessed the end of the world today‭	(no comment)	Aug 19, 2024 at 12:13

Open the Disks application. Select the secondary disk and partition, and in the gears menu click on Edit Mount Options...

action menu of a volume in the Disks application

Uncheck User Session Defaults and uncheck Show in user interface.

Mount options of the volume

Optional: select a Mount Point you can find easily. The disk will not only not be shown in the dock, it will also not be shown in the file manager anymore as a separate drive, you will have to navigate to the folder yourself.

You can drag it to the bookmarks for easier navigation:

file manager window showing mount point icon dragged to the bookmark section

posted 3 months ago

CC BY-NC-SA 4.0

3mo ago by Andreas witnessed the end of the world today‭

351 reputation 3 23 40 22

Copy Link

Raw

Markdown

3 comment threads

What does "Identify As" mean or refer to? (6 comments)

Not specifying a mount point (3 comments)

Boot disk (3 comments)

Andreas witnessed the end of the world today‭ wrote 3 months ago

Well, it's the ID of the disk, used by software, I assume. But how is that relevant to me as a user, and what differences do the options have? Why have a specific mounting option directory the user can choose, when the disk already seems to be mounted in /dev, and a symlink can be made?

Besides, your screenshot shows a folder with that same UUID in the /mnt directory. I only have the "Secondary 0" (named it that in the mounting point input field). How come?

matthewsnyder‭ wrote 3 months ago

It's how the OS will find the correct disk. Unless you have a very specific use case, you almost certainly want the UUID option.

It used to be that disks would get names like /dev/sda, /dev/sdb with partitions getting /dev/sda1 and so on. You couldn't predict whether a drive ends up with sda or sdb. So for example you connect a new drive, the IDs get reassigned, and suddenly you can't boot because the disk that used to be at sda is now at sdc and the OS can't figure it out.

But partitions do have a UUID which is written on the disk itself, so it doesn't change when you unplug and replug the drive. So the advice these days is to always use UUID when setting up automounts.

Stuff in /dev is just the virtual file representing the device. It's used by your OS to talk to the drive itself. You can't ls /dev/disk/by-uuid/xyz and see the files in it, because that file is set up before the filesystem driver is active. That only happens after you mount.

matthewsnyder‭ wrote 3 months ago · edited 3 months ago

Besides, your screenshot shows a folder with that same UUID in the /mnt directory. I only have the "Secondary 0" (named it that in the mounting point input field). How come?

It's probably because PopOS is trying to be user friendly, and avoids basing the mount point name on the UUID. I guess normally it would use the disk/partition label, but something in that "pick user friendly name" logic broke, so it defaulted to a generic "Secondary 0".