second drive starts unmonted

I'm using Bazzite Deck Edition on my desktop installed on my SSD, I also have a HDD for storage. Every time my pc power on se second drive (HDD) starts unmonted, so i have change to desktop and manually mont it. Is this a expected behavior? Can I mark the disk to mount automatically on boot? I also tried to install bazzite using both disk as one storage, but the system either takes long to boot, or stuck on a black screen so I need to manualy start the session on terminal. Any help?
18 Replies
termdisc
termdisc13mo ago
use KDE Partition Manager to set it up so that it is mounted on boot this will edit /etc/fstab
I also tried to install bazzite using both disk as one storage
can you clarify what you're doing here?
Iran Nunes (IzzyN0okami)
Hi thks for reply. I already tried using KDE Partition Manager, but it gives an error when trying to write a partition, it works in the end, but the partition is marked to root access only, that's why i need to manually mount it every time. Maybe the HDD is bad? As for your question above, when I chose both drives on the fedora installation, it merge then into one single drive, similar when we format sd cards as internal memory on android phones
termdisc
termdisc13mo ago
you need to change mount settings to make it not mount as root only
Iran Nunes (IzzyN0okami)
I did these steps
No description
No description
No description
Iran Nunes (IzzyN0okami)
KDE Partition Manager: SMART Status Report Date: 05/12/2023 19:18 Program version: 23.08.3 Backend: pmsfdiskbackendplugin (1) KDE Frameworks version: 5.111.0 Machine: Linux fedora 6.6.2-201.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Nov 22 21:31:42 UTC 2023 x86_64 Delete partition ‘/dev/sdb1’ (465,76 GiB, btrfs) Job: Delete file system on ‘/dev/sdb1’ Command: wipefs --all /dev/sdb1 Delete file system on ‘/dev/sdb1’: Success Job: Delete the partition ‘/dev/sdb1’ Command: sfdisk --force --delete /dev/sdb 1 Delete the partition ‘/dev/sdb1’: Success Delete partition ‘/dev/sdb1’ (465,76 GiB, btrfs): Success Create a new partition (465,76 GiB, btrfs) on ‘/dev/sdb’ Job: Create new partition on device ‘/dev/sdb’ Command: sfdisk --force --append /dev/sdb Command: sfdisk --list --output Device,UUID /dev/sdb Create new partition ‘/dev/sdb1’: Success Job: Create file system ‘btrfs’ on partition ‘/dev/sdb1’ Command: mkfs.btrfs --force /dev/sdb1 Command: sfdisk --part-type /dev/sdb 1 0FC63DAF-8483-4772-8E79-3D69D8477DE4 Create file system ‘btrfs’ on partition ‘/dev/sdb1’: Success Job: Set the file system label on partition ‘/dev/sdb1’ to "" Command: btrfs filesystem label /dev/sdb1 Set the file system label on partition ‘/dev/sdb1’ to "": Error Create a new partition (465,76 GiB, btrfs) on ‘/dev/sdb’: Error this is the log that it gives me. the partition end up functional, but only on root access
Dude
Dude13mo ago
Did you ever solve this?
HikariKnight
HikariKnight13mo ago
No description
HikariKnight
HikariKnight13mo ago
No description
HikariKnight
HikariKnight13mo ago
available options change depending on what the filesystem is, this one was meant as an example and is not one i use with this system forgot which ones to select for ext4 and btrfs, but i know you shouldnt set it to "let everyone mount" as that for some reason last time i tried this method made it it not mount automatically (i tend to just write my mounts directly to /etc/fstab myself without going through a gui)
barrettloganj13
barrettloganj1312mo ago
I have the same issue on my laptop but when i edit the fstab the install got borked☹️
HikariKnight
HikariKnight12mo ago
i helped @Krauzer with this in the Bazzite VC https://discord.com/channels/1072614816579063828/1156769501841465406/1195388937133359195 if the filesystem is btrfs then that should work (just change the device path to match your disk and the mount point) @barrettloganj13
Krauzer
Krauzer12mo ago
hello felow Linuxers I got what you need brother 1. Find name on KDE Partition Manager; 2. Find the unique device's ID:
ls -la /dev/disk/by-id | grep sda
ls -la /dev/disk/by-id | grep sda
3. Add it to the fstab file:
sudo mkdir /mnt/$CUSTOM_DEVICE_NAME
sudo sh -c 'echo -e "\n# Automount Hard Drive (hard_drive)\n/dev/disk/by-id/$UNIQUE_DEVICE_ID /mnt/hard_drive btrfs subvol=/,noatime,lazytime,commit=120,discard=async,compress-force=zstd:3,space_cache=v2,nofail 0 0" >> /etc/fstab'
sudo systemctl daemon-reload
sudo mount -a
sudo mkdir /mnt/$CUSTOM_DEVICE_NAME
sudo sh -c 'echo -e "\n# Automount Hard Drive (hard_drive)\n/dev/disk/by-id/$UNIQUE_DEVICE_ID /mnt/hard_drive btrfs subvol=/,noatime,lazytime,commit=120,discard=async,compress-force=zstd:3,space_cache=v2,nofail 0 0" >> /etc/fstab'
sudo systemctl daemon-reload
sudo mount -a
the $CUSTOM_DEVICE_NAME is freestyle, choose whatever you want
though I suggest something very simple and no spaces
you just need to figure out your $UNIQUE_DEVICE_ID and replace it
Krauzer
Krauzer12mo ago
it should look something like this
No description
Krauzer
Krauzer12mo ago
in my case, my $UNIQUE_DEVICE_ID is ata-TOSHIBA_HDWD110_48DWBPRNS-part1
HikariKnight
HikariKnight12mo ago
you forgot to make the folder where it will be mounted
Krauzer
Krauzer12mo ago
oh, right
HikariKnight
HikariKnight12mo ago
other than that its all good for ext4 filesystem you replace subvol=/,noatime,lazytime,commit=120,discard=async,compress-force=zstd:3,space_cache=v2,nofail with defaults,noatime,errors=remount-ro,nofail i also see an error here ,nofail0 0 ---> ,nofail 0 0
Krauzer
Krauzer12mo ago
nooo edited
Want results from more Discord servers?
Add your server