Locked out of new SSD (SOLVED)

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
Post Reply
Helmut
Level 4
Level 4
Posts: 235
Joined: Tue Nov 28, 2006 1:33 pm
Location: Germany

Locked out of new SSD (SOLVED)

Post by Helmut »

I have added a SSD to the drives of my computer. The SSD was formatted with gparted and partitions created as needed.
Now, If I want to put anything on it or otherwise use it, it will not let me!
Looking at the permissions (File, properties) it says "you are not the owner so you can not change these permissions".
What can be done?
Last edited by Helmut on Fri Oct 26, 2018 10:46 am, edited 1 time in total.

srq2625
Level 4
Level 4
Posts: 420
Joined: Tue Jan 08, 2013 11:35 am
Location: State: Constant Confusion, Country: D'oh

Re: Locked out of new SSD

Post by srq2625 »

Need some more information; please run the following commands and post back the results inside a code block (the fifth button from the left above the text entry window - clicking the button will generate the string [code][/code] ):

Code: Select all

$ lsblk
$ sudo blkid
$ cat /etc/fstab
$ inxi -Fxxz

Helmut
Level 4
Level 4
Posts: 235
Joined: Tue Nov 28, 2006 1:33 pm
Location: Germany

Re: Locked out of new SSD

Post by Helmut »

Here is the output. sdc is my new SSD.

Code: Select all

helmut@helmuts ~ $ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0  74,5G  0 disk 
├─sda1   8:1    0  19,8G  0 part 
├─sda2   8:2    0     1K  0 part 
└─sda5   8:5    0  54,7G  0 part /media/helmut/SHARE
sdb      8:16   0 232,9G  0 disk 
├─sdb1   8:17   0  12,5G  0 part /
├─sdb2   8:18   0     1G  0 part [SWAP]
├─sdb3   8:19   0     1K  0 part 
├─sdb5   8:21   0  35,8G  0 part /usr
└─sdb6   8:22   0 107,2G  0 part 
sdc      8:32   0 111,8G  0 disk 
├─sdc1   8:33   0  20,1G  0 part 
├─sdc2   8:34   0   3,7G  0 part 
├─sdc3   8:35   0     1K  0 part 
├─sdc5   8:37   0  14,8G  0 part 
└─sdc6   8:38   0  73,2G  0 part 
sdd      8:48   1  29,1G  0 disk 
└─sdd1   8:49   1  29,1G  0 part /media/helmut/TOSHIBA USB
sr0     11:0    1  1024M  0 rom  
helmut@helmuts ~ $ sudo blkid
[sudo] password for helmut: 
/dev/sda1: UUID="2A8E20DE11698C6E" TYPE="ntfs" 
/dev/sda5: LABEL="SHARE" UUID="67f6a46d-0be0-46d3-a161-1302bdf3e422" TYPE="ext4" 
/dev/sdb1: UUID="cb370d46-39ae-47ae-83ed-cf2bdb9453a6" TYPE="ext4" 
/dev/sdb2: UUID="bfdd282b-97b1-4243-888e-6cc3fb3ccff9" TYPE="swap" 
/dev/sdb5: LABEL="HOME" UUID="fd692b4f-7315-4f8f-a510-c1119cf74415" TYPE="ext3" 
/dev/sdb6: LABEL="BACKUP" UUID="f8cae603-ad13-4031-9946-b105e2039a29" TYPE="ext4" 
/dev/sdc1: LABEL="/" UUID="96443a44-b3dd-4599-98a8-62a35f546073" TYPE="ext4" 
/dev/sdc2: UUID="ff96cdf1-58c6-407d-9f13-66c555d87a6f" TYPE="swap" 
/dev/sdc5: LABEL="SSD HOME" UUID="f9ab9521-eea8-4414-8237-7edd76e19cd4" TYPE="ext4" 
/dev/sdc6: LABEL="SSD MYSTUFF" UUID="27c5ad2b-577e-482e-9829-2eedb99d69f3" TYPE="ext4" 
/dev/sdd1: LABEL="TOSHIBA USB" UUID="D55D-8258" TYPE="vfat" 
helmut@helmuts ~ $  cat /etc/fstab
# /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>
# / was on /dev/sdb1 during installation
UUID=cb370d46-39ae-47ae-83ed-cf2bdb9453a6 /               ext4    errors=remount-ro 0       1
# /usr was on /dev/sdb5 during installation
UUID=fd692b4f-7315-4f8f-a510-c1119cf74415 /usr            ext3    defaults        0       2
# swap was on /dev/sdb2 during installation
UUID=bfdd282b-97b1-4243-888e-6cc3fb3ccff9 none            swap    sw              0       0
helmut@helmuts ~ $ inxi -Fxxz
System:    Host: helmuts Kernel: 3.16.0-38-generic x86_64 (64 bit, gcc: 4.8.2) 
           Desktop: MATE 1.10.2  dm: mdm Distro: Linux Mint 17.2 Rafaela
Machine:   System: Dell product: OptiPlex 760 Chassis: type: 6
           Mobo: Dell model: 0G214D version: A00 Bios: Dell version: A16 date: 08/06/2013
CPU:       Dual core Intel Core2 Duo CPU E8400 (-MCP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 11969 
           Clock Speeds: 1: 3000.00 MHz 2: 2000.00 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] bus-ID: 01:00.0 chip-ID: 1002:6779 
           X.Org: 1.15.1 drivers: ati,radeon (unloaded: fbdev,vesa) Resolution: 1920x1080@60.0hz 
           GLX Renderer: Gallium 0.4 on AMD CAICOS GLX Version: 3.0 Mesa 10.1.3 Direct Rendering: Yes
Audio:     Card-1: Advanced Micro Devices [AMD/ATI] Caicos HDMI Audio [Radeon HD 6400 Series] 
           driver: snd_hda_intel bus-ID: 01:00.1 chip-ID: 1002:aa98 
           Card-2: Intel 82801JD/DO (ICH10 Family) HD Audio Controller 
           driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:3a6e 
           Sound: Advanced Linux Sound Architecture ver: k3.16.0-38-generic
Network:   Card-1: Ralink RT2561/RT61 802.11g PCI driver: rt61pci ver: 2.3.0 bus-ID: 04:02.0 chip-ID: 1814:0301
           IF: wlan0 state: up mac: <filter>
           Card-2: Intel 82567LM-3 Gigabit Network Connection 
           driver: e1000e ver: 2.3.2-k port: ece0 bus-ID: 00:19.0 chip-ID: 8086:10de
           IF: eth0 state: down mac: <filter>
Drives:    HDD Total Size: 481.3GB (8.2% used)
           1: id: /dev/sda model: ST380815AS size: 80.0GB serial: 9RW4SMH1 temp: 33C 
           2: id: /dev/sdb model: ST3250310AS size: 250.1GB serial: 6RY91TVV temp: 33C 
           3: id: /dev/sdc model: Intenso_SSD size: 120.0GB serial: 3813430-531803036 temp: 42C 
           4: USB id: /dev/sdd model: TransMemory size: 31.2GB serial: 001CC0C83B3CECC0E3150155-0:0 temp: 0C 
Partition: ID: / size: 13G used: 7.9G (68%) fs: ext4 ID: /usr size: 36G used: 5.1G (16%) fs: ext3 
           ID: swap-1 size: 1.12GB used: 0.00GB (0%) fs: swap 
RAID:      System: supported: N/A
           No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
           Unused Devices: none
Sensors:   System Temperatures: cpu: 42.0C mobo: N/A 
           Fan Speeds (in rpm): cpu: N/A 
Info:      Processes: 203 Uptime: 1:09 Memory: 1002.1/3824.5MB Runlevel: 2 Gcc sys: 4.8.4 
           Client: Shell (bash 4.3.11 running in mate-terminal) inxi: 1.9.17 
helmut@helmuts ~ $
Last edited by Moem on Thu Oct 25, 2018 9:18 am, edited 1 time in total.
Reason: Adding [code] tags. They retain some formatting that makes your output easier to read.

Helmut
Level 4
Level 4
Posts: 235
Joined: Tue Nov 28, 2006 1:33 pm
Location: Germany

Re: Locked out of new SSD

Post by Helmut »

Bump?!

User avatar
vansloneker
Level 5
Level 5
Posts: 556
Joined: Sat Mar 17, 2018 6:10 am

Re: Locked out of new SSD

Post by vansloneker »

In the file manager -at least, in Thunar it works that way- right click on a partition, open as root. Right click again, properties, tab permissions, then allow yourself permissions.
Unless stated otherwise Mint 18.3-64 XFCE

User avatar
Lord Boltar
Level 5
Level 5
Posts: 688
Joined: Mon Jan 09, 2017 7:24 pm
Location: Sunny Florida

Re: Locked out of new SSD

Post by Lord Boltar »

You have to take ownership of the drive

sudo chown -R youname:yourname /media/drivename

This will give you permission to the drive. If you wish to change it back:

sudo chown -R root:root /media/drivename

or as "vansloneker" suggested
IF your problem has been solved, please edit your original post and add [SOLVED] to the beginning of the Subject Line. It helps other members

The only way for evil to prosper is for good men to do nothing

Helmut
Level 4
Level 4
Posts: 235
Joined: Tue Nov 28, 2006 1:33 pm
Location: Germany

Re: Locked out of new SSD

Post by Helmut »

vansloneker suggested:
In the file manager -at least, in Thunar it works that way- right click on a partition, open as root. Right click again, properties, tab permissions, then allow yourself permissions.
That did not work with the file management tool.



Then I tried with the panel and got this outcome:

helmut@helmuts ~ $ sudo chown -R helmut /media/sdc
chown: cannot access ‘/media/sdc’: No such file or directory

In gparted the SSD is listed as /media/sdc
Last edited by Helmut on Thu Oct 25, 2018 2:57 pm, edited 1 time in total.

User avatar
Flemur
Level 18
Level 18
Posts: 8458
Joined: Mon Aug 20, 2012 9:41 pm
Location: Potemkin Village

Re: Locked out of new SSD

Post by Flemur »

Code: Select all

/dev/sdc1: LABEL="/" UUID="96443a44-b3dd-4599-98a8-62a35f546073" TYPE="ext4" 
You probably want to change that LABEL!
In gparted the SSD is listed as /media/sdc
That partitions will mount to /media/helmut/LABEL or /media/helmut/UUID if you don't say otherwise.
(LABEL and UUID being the actual values, like "BACKUP").

That's one reason why you don't want the LABEL to be "/".
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?

Helmut
Level 4
Level 4
Posts: 235
Joined: Tue Nov 28, 2006 1:33 pm
Location: Germany

Re: Locked out of new SSD

Post by Helmut »

On all partitions of the sdc, I erased the labels with gparted.

Input: sudo chown -R helmut /dev/sdc

now seemingly responds with no result.

If I try to copy something into a mounted partition of the /sdc this is the result:

There was an error copying the file into /media/helmut/f9ab9521-eea8-4414-8237-7edd76e19cd4

There is a tab under that saying "show more details" and after opening that tab it reads:

Error opening file '/media/helmut/f9ab9521-eea8-4414-8237-7edd76e19cd4/springs.PDF': Permission denied
Last edited by Helmut on Thu Oct 25, 2018 3:12 pm, edited 1 time in total.

User avatar
Flemur
Level 18
Level 18
Posts: 8458
Joined: Mon Aug 20, 2012 9:41 pm
Location: Potemkin Village

Re: Locked out of new SSD

Post by Flemur »

Helmut wrote:
Thu Oct 25, 2018 3:02 pm
On all partitions of the sdc, I erased the labels with gparted.
But chown still responds with the same result.
What do the commands

Code: Select all

mount | grep sdc

Code: Select all

df
return?
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?

Helmut
Level 4
Level 4
Posts: 235
Joined: Tue Nov 28, 2006 1:33 pm
Location: Germany

Re: Locked out of new SSD

Post by Helmut »

mount | grep sdc
gives response:
/dev/sdc5 on /media/helmut/f9ab9521-eea8-4414-8237-7edd76e19cd4 type ext4 (rw,nosuid,nodev,uhelper=udisks2)
/dev/sdc6 on /media/helmut/27c5ad2b-577e-482e-9829-2eedb99d69f3 type ext4 (rw,nosuid,nodev,uhelper=udisks2)


df
gives response:
Filesystem 1K-blocks Used Available Use% Mounted on
udev 1942272 12 1942260 1% /dev
tmpfs 391632 1400 390232 1% /run
/dev/sdb1 12779224 8221340 3885684 68% /
none 4 0 4 0% /sys/fs/cgroup
none 5120 0 5120 0% /run/lock
none 1958156 50452 1907704 3% /run/shm
none 102400 48 102352 1% /run/user
/dev/sdb5 36789956 5263476 29650976 16% /usr
/dev/sdc5 15127948 37864 14298584 1% /media/helmut/f9ab9521-eea8-4414-8237-7edd76e19cd4
/dev/sdc6 75434104 53012 71526196 1% /media/helmut/27c5ad2b-577e-482e-9829-2eedb99d69f3

Helmut
Level 4
Level 4
Posts: 235
Joined: Tue Nov 28, 2006 1:33 pm
Location: Germany

Re: Locked out of new SSD

Post by Helmut »

In gparted, I erased all partitions on sdc. Then I recreated them, and tried if that helped. Nothing changed.

Now
mount | grep sdc
responds:
/dev/sdc1 on /media/helmut/b0ab27b2-4b1d-4da5-b403-e3a022d7a9be type ext4 (rw,nosuid,nodev,uhelper=udisks2)

and

df
reponds:
Filesystem 1K-blocks Used Available Use% Mounted on
udev 1942272 12 1942260 1% /dev
tmpfs 391632 1400 390232 1% /run
/dev/sdb1 12779224 8221920 3885104 68% /
none 4 0 4 0% /sys/fs/cgroup
none 5120 0 5120 0% /run/lock
none 1958156 63532 1894624 4% /run/shm
none 102400 56 102344 1% /run/user
/dev/sdb5 36789956 5263476 29650976 16% /usr
/dev/sdc1 20637300 44992 19520948 1% /media/helmut/b0ab27b2-4b1d-4da5-b403-e3a022d7a9be
Last edited by Helmut on Thu Oct 25, 2018 4:39 pm, edited 1 time in total.

User avatar
Flemur
Level 18
Level 18
Posts: 8458
Joined: Mon Aug 20, 2012 9:41 pm
Location: Potemkin Village

Re: Locked out of new SSD

Post by Flemur »

Helmut wrote:
Thu Oct 25, 2018 3:56 pm
In gparted, I erased all partitions on sdc. Then I recreated them, and tried if that helped. Nothing changed.
Now
mount | grep sdc
responds:
/dev/sdc1 on /media/helmut/b0ab27b2-4b1d-4da5-b403-e3a022d7a9be type ext4 (rw,nosuid,nodev,uhelper=udisks2)
This should make you the owner of it, and everything underneath:

Code: Select all

sudo chown -R $USER:$USER /media/helmut/b0ab27b2-4b1d-4da5-b403-e3a022d7a9be
Then try

Code: Select all

ls -al /media/helmut/b0ab27b2-4b1d-4da5-b403-e3a022d7a9be
to see what's there.

And you might want to give it a LABEL, so it'll mount to /media/helmut/LABEL-VALUE
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?

Helmut
Level 4
Level 4
Posts: 235
Joined: Tue Nov 28, 2006 1:33 pm
Location: Germany

Re: Locked out of new SSD

Post by Helmut »

This is what it did:

Code: Select all

helmut@helmuts ~ $ sudo chown -R $USER:$USER /media/helmut/b0ab27b2-4b1d-4da5-b403-e3a022d7a9be
[sudo] password for helmut: 
chown: cannot access ‘/media/helmut/b0ab27b2-4b1d-4da5-b403-e3a022d7a9be’: No such file or directory

Code: Select all

helmut@helmuts ~ $ ls -al /media/helmut/b0ab27b2-4b1d-4da5-b403-e3a022d7a9be
ls: cannot access /media/helmut/b0ab27b2-4b1d-4da5-b403-e3a022d7a9be: No such file or directory
helmut@helmuts ~ $
I put following code into the terminal again, and the result was:

Code: Select all

CODE:  lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0  74,5G  0 disk 
├─sda1   8:1    0  19,8G  0 part 
├─sda2   8:2    0     1K  0 part 
└─sda5   8:5    0  54,7G  0 part 
sdb      8:16   0 232,9G  0 disk 
├─sdb1   8:17   0  12,5G  0 part /
├─sdb2   8:18   0     1G  0 part [SWAP]
├─sdb3   8:19   0     1K  0 part 
├─sdb5   8:21   0  35,8G  0 part /usr
└─sdb6   8:22   0 107,2G  0 part 
sdc      8:32   0 111,8G  0 disk 
├─sdc1   8:33   0  19,9G  0 part 
├─sdc2   8:34   0   3,9G  0 part 
├─sdc3   8:35   0     1K  0 part 
├─sdc5   8:37   0    25G  0 part 
└─sdc6   8:38   0    63G  0 part 
sr0     11:0    1  1024M  0 rom

Code: Select all

CODE: sudo blkid
[sudo] password for helmut: 
/dev/sda1: UUID="2A8E20DE11698C6E" TYPE="ntfs" 
/dev/sda5: LABEL="SHARE" UUID="67f6a46d-0be0-46d3-a161-1302bdf3e422" TYPE="ext4" 
/dev/sdb1: UUID="cb370d46-39ae-47ae-83ed-cf2bdb9453a6" TYPE="ext4" 
/dev/sdb2: UUID="bfdd282b-97b1-4243-888e-6cc3fb3ccff9" TYPE="swap" 
/dev/sdb5: LABEL="HOME" UUID="fd692b4f-7315-4f8f-a510-c1119cf74415" TYPE="ext3" 
/dev/sdb6: LABEL="BACKUP" UUID="f8cae603-ad13-4031-9946-b105e2039a29" TYPE="ext4" 
/dev/sdc1: UUID="bee6046f-89ac-4ffe-bbd4-510c5a3660c6" TYPE="ext4" 
/dev/sdc2: UUID="9aa6d1d5-9731-4f98-ae02-ae9058067852" TYPE="swap" 
/dev/sdc5: UUID="a6947a79-ec9e-4f45-b6e0-b5a2c056faa2" TYPE="ext4" 
/dev/sdc6: UUID="33f9fb1c-440d-4f6a-8d63-03ae07bfa719" TYPE="ext4"

Code: Select all

CODE:cat /etc/fstab
# /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>
# / was on /dev/sdb1 during installation
UUID=cb370d46-39ae-47ae-83ed-cf2bdb9453a6 /               ext4    errors=remount-ro 0       1
# /usr was on /dev/sdb5 during installation
UUID=fd692b4f-7315-4f8f-a510-c1119cf74415 /usr            ext3    defaults        0       2
# swap was on /dev/sdb2 during installation
UUID=bfdd282b-97b1-4243-888e-6cc3fb3ccff9 none            swap    sw   

Code: Select all

Code: inxi -Fxxz
System:    Host: helmuts Kernel: 3.16.0-38-generic x86_64 (64 bit, gcc: 4.8.2) 
           Desktop: MATE 1.10.2  dm: mdm Distro: Linux Mint 17.2 Rafaela
Machine:   System: Dell product: OptiPlex 760 Chassis: type: 6
           Mobo: Dell model: 0G214D version: A00 Bios: Dell version: A16 date: 08/06/2013
CPU:       Dual core Intel Core2 Duo CPU E8400 (-MCP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 11970 
           Clock Speeds: 1: 2000.00 MHz 2: 2000.00 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] bus-ID: 01:00.0 chip-ID: 1002:6779 
           X.Org: 1.15.1 drivers: ati,radeon (unloaded: fbdev,vesa) Resolution: 1920x1080@60.0hz 
           GLX Renderer: Gallium 0.4 on AMD CAICOS GLX Version: 3.0 Mesa 10.1.3 Direct Rendering: Yes
Audio:     Card-1: Advanced Micro Devices [AMD/ATI] Caicos HDMI Audio [Radeon HD 6400 Series] 
           driver: snd_hda_intel bus-ID: 01:00.1 chip-ID: 1002:aa98 
           Card-2: Intel 82801JD/DO (ICH10 Family) HD Audio Controller 
           driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:3a6e 
           Sound: Advanced Linux Sound Architecture ver: k3.16.0-38-generic
Network:   Card-1: Ralink RT2561/RT61 802.11g PCI driver: rt61pci ver: 2.3.0 bus-ID: 04:02.0 chip-ID: 1814:0301
           IF: wlan0 state: up mac: <filter>
           Card-2: Intel 82567LM-3 Gigabit Network Connection 
           driver: e1000e ver: 2.3.2-k port: ece0 bus-ID: 00:19.0 chip-ID: 8086:10de
           IF: eth0 state: down mac: <filter>
Drives:    HDD Total Size: 450.1GB (3.1% used)
           1: id: /dev/sda model: ST380815AS size: 80.0GB serial: 9RW4SMH1 
           2: id: /dev/sdb model: ST3250310AS size: 250.1GB serial: 6RY91TVV 
           3: id: /dev/sdc model: Intenso_SSD size: 120.0GB serial: 3813430-531803036 
Partition: ID: / size: 13G used: 7.9G (68%) fs: ext4 ID: /usr size: 36G used: 5.1G (16%) fs: ext3 
           ID: swap-1 size: 1.12GB used: 0.00GB (0%) fs: swap 
RAID:      System: supported: N/A
           No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
           Unused Devices: none
Sensors:   System Temperatures: cpu: 42.0C mobo: N/A 
           Fan Speeds (in rpm): cpu: N/A 
Info:      Processes: 198 Uptime: 17 min Memory: 696.6/3824.5MB Runlevel: 2 Gcc sys: 4.8.4 
           Client: Shell (bash 4.3.11 running in mate-terminal) inxi: 1.9.17 

Code: Select all

# 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>
# / was on /dev/sdb1 during installation
UUID=cb370d46-39ae-47ae-83ed-cf2bdb9453a6 /               ext4    errors=remount-ro 0       1
# /usr was on /dev/sdb5 during installation
UUID=fd692b4f-7315-4f8f-a510-c1119cf74415 /usr            ext3    defaults        0       2
# swap was on /dev/sdb2 during installation
UUID=bfdd282b-97b1-4243-888e-6cc3fb3ccff9 none            swap    sw              0       0

srq2625
Level 4
Level 4
Posts: 420
Joined: Tue Jan 08, 2013 11:35 am
Location: State: Constant Confusion, Country: D'oh

Re: Locked out of new SSD

Post by srq2625 »

The following should work .... assuming you haven't changed anything since your last post:
  1. Run the following commands - these commands, in turn, do the following: (1) create a place to mount the "non-swap" partitions, (2) mount the partitions, (3) change the ownership of the partitions, and (4) un-mount the partitions. The -R is included just to be pendantic - you probably don't have any folders on these partitions, but this will cover that base in the event you do.

    Code: Select all

    $ mkdir /mnt/ssd1
    $ mkdir /mnt/ssd3
    $ mkdir /mnt/ssd4
    $ sudo mount /dev/sdc1 /mnt/ssd1
    $ sudo mount /dev/sdc3 /mnt/ssd3
    $ sudo mount /dev/sdc4 /mnt/ssd4
    $ sudo chown -R $(USER):$(USER) /mnt/ssd1
    $ sudo chown -R $(USER):$(USER) /mnt/ssd3
    $ sudo chown -R $(USER):$(USER) /mnt/ssd4
    $ sudo umount /dev/ssd1
    $ sudo umount /dev/ssd3
    $ sudo umount /dev/ssd4
    
  2. Add the following code to the end of your /etc/fstab file (you'll need to open the editor with elevated permissions). Doing this will cause these partitions to be automatically mounted each time your reboot your computer. Please note, these will get the partitions mounted but you may want to re-visit the mounting parameters. This Arch Wiki page will be a big help in deciding what, if anything, you want to change.

    Code: Select all

    UUID=bee6046f-89ac-4ffe-bbd4-510c5a3660c6 /mnt/ssd1 ext4 errors=remount-ro 0 2
    UUID=a6947a79-ec9e-4f45-b6e0-b5a2c056faa2 /mnt/ssd3 ext4 errors=remount-ro 0 2
    UUID=33f9fb1c-440d-4f6a-8d63-03ae07bfa719 /mnt/ssd4 ext4 errors=remount-ro 0 2
    
  3. Now, run the following command to re-mount the partitions without having to re-boot your computer

    Code: Select all

    $ sudo mount -a
As a final note here, I'm not sure why you (1) created so many partitions, and (2) why you created a swap partition.

Helmut
Level 4
Level 4
Posts: 235
Joined: Tue Nov 28, 2006 1:33 pm
Location: Germany

Re: Locked out of new SSD

Post by Helmut »

Quote: "As a final note here, I'm not sure why you (1) created so many partitions, and (2) why you created a swap partition."

I wanted to use the SSD as the new drive for the Mint OS, including a seperate partition on it for my own files.
The other two HDD's had one Windoze and one (old) Mint OS on each, plus either all of my own files in a seperate partition, or a backup of all my own files on another partition of the other HDD. That way it was a dual boot system, with a common partition for my own files, plus a backup of my own files on a different partition of the other HDD.
Since the HDD with mint on it is very old (2003 or so), I wanted to replace it with the SSD.

In the mean time, since else nothing helped, I removed all HDD except for the SSD and did a fresh Mint install. Then I added the HDD containg my backups to the PC. Then copied all the backed up files on the HDD to the separate "my stuff" partition of the SSD.
That worked as forseen. Thank you all for your help!

User avatar
Flemur
Level 18
Level 18
Posts: 8458
Joined: Mon Aug 20, 2012 9:41 pm
Location: Potemkin Village

Re: Locked out of new SSD

Post by Flemur »

Helmut wrote:
Thu Oct 25, 2018 4:39 pm
ls: cannot access /media/helmut/b0ab27b2-4b1d-4da5-b403-e3a022d7a9be: No such file or directory
You unmounted it. Your first outputs showed it was mounted, then your later outputs show that it's no longer mounted.

If you want to use a partition, it has to be mounted. If you want to change it (size, label) it has to unmounted.
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?

Post Reply

Return to “Newbie Questions”