F5F Stay Refreshed Software Operating Systems Directory located on a distinct storage device...

Directory located on a distinct storage device...

Directory located on a distinct storage device...

Pages (3): 1 2 3 Next
E
EmmiK
Junior Member
7
01-06-2017, 11:31 AM
#1
To get straight to the point... I've been attempting to configure Kubuntu (version 21.04) with the /home folder on a different storage device. My goal is to keep files on the larger WD Enterprise drives instead of the smaller 120GB SSD that came with the OS and a few programs. The process is proving more complicated than on Windows, and I've faced several challenges along the way. After installing Kubuntu normally, I tried entering specific command lines in the console and modifying fstab, as shown in a video: unfortunately, the system only starts in emergency mode. When I reattempted from a clean install, the same issue persisted. Then I attempted to create the separate /home directory via the installer (I hadn't done this before, as it wasn't listed), following instructions from that video. However, Linux fails to load after logging in. I've tested with both an older ATI Radeon 5770 and a spare RX 580, hoping the graphics problem was the cause. With the 5770, the screen freezes immediately after pressing Enter after entering the password. The 580 either turns black or shows only the cursor. I suspect this stems from missing drivers on the manual installation path used in the video, so I'm unlikely to revisit it. Anyone have suggestions? I'm new to Linux, so any advice would be greatly appreciated!
E
EmmiK
01-06-2017, 11:31 AM #1

To get straight to the point... I've been attempting to configure Kubuntu (version 21.04) with the /home folder on a different storage device. My goal is to keep files on the larger WD Enterprise drives instead of the smaller 120GB SSD that came with the OS and a few programs. The process is proving more complicated than on Windows, and I've faced several challenges along the way. After installing Kubuntu normally, I tried entering specific command lines in the console and modifying fstab, as shown in a video: unfortunately, the system only starts in emergency mode. When I reattempted from a clean install, the same issue persisted. Then I attempted to create the separate /home directory via the installer (I hadn't done this before, as it wasn't listed), following instructions from that video. However, Linux fails to load after logging in. I've tested with both an older ATI Radeon 5770 and a spare RX 580, hoping the graphics problem was the cause. With the 5770, the screen freezes immediately after pressing Enter after entering the password. The 580 either turns black or shows only the cursor. I suspect this stems from missing drivers on the manual installation path used in the video, so I'm unlikely to revisit it. Anyone have suggestions? I'm new to Linux, so any advice would be greatly appreciated!

I
iLwRo
Member
130
01-09-2017, 10:47 AM
#2
Adjusting fstab files is generally the best approach for this task. It can be performed during installation or manually, as you attempted. The second guide you followed seems to have helped you get past the login barrier. If drivers are absent (common in older models like the 5770), you can switch to a terminal by pressing ctrl+alt+f2 and install them.
I
iLwRo
01-09-2017, 10:47 AM #2

Adjusting fstab files is generally the best approach for this task. It can be performed during installation or manually, as you attempted. The second guide you followed seems to have helped you get past the login barrier. If drivers are absent (common in older models like the 5770), you can switch to a terminal by pressing ctrl+alt+f2 and install them.

M
Mr_board
Junior Member
17
01-11-2017, 11:40 PM
#3
During installation, choose an alternative for the disk partitioning area. Wipe the disk and set up a new GPT partition table. Set up a 250MB partition with the mount point at /boot. Configure an 8196MB partition and enable swapping. Divide the rest into two halves, assigning each a mount point (/ for the first half, /home for the second). Save the changes and proceed with the installation.
M
Mr_board
01-11-2017, 11:40 PM #3

During installation, choose an alternative for the disk partitioning area. Wipe the disk and set up a new GPT partition table. Set up a 250MB partition with the mount point at /boot. Configure an 8196MB partition and enable swapping. Divide the rest into two halves, assigning each a mount point (/ for the first half, /home for the second). Save the changes and proceed with the installation.

M
Misli
Member
110
01-21-2017, 12:14 AM
#4
Sauron already explained the proper way to handle this. Now I’ll share my take—this is quite a challenge in practice. Any app that ignores $HOME and relies on something like /home/$USER will act oddly. Ideally, developers should respect environment variables, but real-world issues make it frustrating. To work around it, I set up symlinks for important directories such as ~/Documents, ~/Dropbox, etc., so they point to the actual storage on my main drive. This requires a small initial setup but keeps things working smoothly afterward.

Note: For Dropbox or similar sync tools, the application should understand the real path (e.g., /mnt/internal/bighdd/Dropbox). Symlinks inside them can behave unpredictably. It’s best to link folders outside of them and avoid linking data inside. Updated September 29, 2021 by maplepants Added key details for Dropbox/file sync apps
M
Misli
01-21-2017, 12:14 AM #4

Sauron already explained the proper way to handle this. Now I’ll share my take—this is quite a challenge in practice. Any app that ignores $HOME and relies on something like /home/$USER will act oddly. Ideally, developers should respect environment variables, but real-world issues make it frustrating. To work around it, I set up symlinks for important directories such as ~/Documents, ~/Dropbox, etc., so they point to the actual storage on my main drive. This requires a small initial setup but keeps things working smoothly afterward.

Note: For Dropbox or similar sync tools, the application should understand the real path (e.g., /mnt/internal/bighdd/Dropbox). Symlinks inside them can behave unpredictably. It’s best to link folders outside of them and avoid linking data inside. Updated September 29, 2021 by maplepants Added key details for Dropbox/file sync apps

J
Julie_08
Member
176
01-21-2017, 02:54 AM
#5
I performed the action a second time... This caused the display to freeze once the password was typed on the lock screen.
J
Julie_08
01-21-2017, 02:54 AM #5

I performed the action a second time... This caused the display to freeze once the password was typed on the lock screen.

H
housten15
Member
51
01-27-2017, 12:38 AM
#6
H
housten15
01-27-2017, 12:38 AM #6

E
128
01-27-2017, 01:02 AM
#7
You need to follow the exact steps provided. If you're unsure about any part, let me know so I can clarify. The issue you mentioned involves missing WiFi drivers, which may require checking your device settings or reinstalling them.
E
EnderPearl5678
01-27-2017, 01:02 AM #7

You need to follow the exact steps provided. If you're unsure about any part, let me know so I can clarify. The issue you mentioned involves missing WiFi drivers, which may require checking your device settings or reinstalling them.

L
legamergame
Junior Member
2
01-30-2017, 03:26 AM
#8
Open a terminal, log in as root or use sudo, run lspci -v to view device information. Capture the output and send it here.
L
legamergame
01-30-2017, 03:26 AM #8

Open a terminal, log in as root or use sudo, run lspci -v to view device information. Capture the output and send it here.

R
Rhyn38
Junior Member
1
02-01-2017, 12:59 AM
#9
I was a bit occupied this evening, but I plan to do it again tomorrow. Thank you really for your support!
R
Rhyn38
02-01-2017, 12:59 AM #9

I was a bit occupied this evening, but I plan to do it again tomorrow. Thank you really for your support!

T
TheMightyElf
Member
214
02-01-2017, 09:47 PM
#10
I begin with version 580, as it receives official support from the default Ubuntu drivers. Verify whether nomodeset is active by opening /etc/default/grub, editing it with nano, and removing any line that starts with GRUB_CMDLINE_LINUX_DEFAULT="some flags" if it includes "nomodeset" within quotes. Save the changes and restart the system.
T
TheMightyElf
02-01-2017, 09:47 PM #10

I begin with version 580, as it receives official support from the default Ubuntu drivers. Verify whether nomodeset is active by opening /etc/default/grub, editing it with nano, and removing any line that starts with GRUB_CMDLINE_LINUX_DEFAULT="some flags" if it includes "nomodeset" within quotes. Save the changes and restart the system.

Pages (3): 1 2 3 Next