More > JRiver Media Center 33 for Linux
MC 33 with Ubuntu 24.04.2 LTS - intermittent file not found error on playback
sg27:
MCWillems, thanks for the detailed instructions.
So if this is my result from my blkid:
/dev/sdb1: LABEL="Data" UUID="57521c67-3776-45c7-ae16-8b038b18cbb4" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Basic data partition" PARTUUID="00009cf1-ead0-6342-c96b-db01e2390100"
Is this line correct to add to my fstab?
UUID="57521c67-3776-45c7-ae16-8b038b18cbb4 /mnt/media ext4 defaults 0 1
bob:
--- Quote from: mwillems on April 04, 2025, 11:15:45 am ---Type the command "sudo blkid" That will return a series of lines one for each device and partition. You want to find the line that starts with "/dev/sdb1" and then copy the long alphanumeric value following "UUID" on that line. Also make a note of what the "TYPE" value is for that line.
Then open your /etc/fstab for editing by typing "sudo nano /etc/fstab"
Add a new line at the bottom being careful not to change any of the previous lines. On that new line you need to add something like the below, but replacing the placeholders below with the correct information for your system:
--- Code: ---UUID=placeholder-for-your-UUID-from-blkid /placeholder/for/desired/mount/path/ placeholder-for-TYPE-from-BLKID defaults 0 1
--- End code ---
As an example, a line from my fstab looks like this (do not copy and paste this you need to use the correct data for your system instead of what I have below!):
--- Code: ---UUID=a18c7092-a223-40dd-a4c3-4ced0ac1fdfe /mnt/media ext4 defaults 0 1
--- End code ---
Once you have added the correct line for your system, make sure everything is correct and then press CTRL+S and then CTRL+X. Then test the mount by typing the following and making sure to enter the path you put in the fstab as the place to mount the drive:
--- Code: ---sudo systemctl daemon-reload
sudo mount /placeholder/for/desired/mount/path
--- End code ---
If it mounts correctly and you can see the files, you should be safe to reboot. If not, go back and check your fstab to make sure it's correct.
Assuming it's all correct, on your next boot, the drive at /dev/sdb1 should be mounted automatically at the path you included in the fstab.
--- End quote ---
Shouldn't he specify the uid and gid on mount so it's writable by the user?
or use the user option added to defaults?
Awesome Donkey:
If you need a GUI and you're using Ubuntu, you can open GNOME's Disks app and manage it from there too so it's automounts on boot.
mwillems:
--- Quote from: sg27 on April 04, 2025, 11:50:56 am ---MCWillems, thanks for the detailed instructions.
So if this is my result from my blkid:
/dev/sdb1: LABEL="Data" UUID="57521c67-3776-45c7-ae16-8b038b18cbb4" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Basic data partition" PARTUUID="00009cf1-ead0-6342-c96b-db01e2390100"
Is this line correct to add to my fstab?
UUID="57521c67-3776-45c7-ae16-8b038b18cbb4 /mnt/media ext4 defaults 0 1
--- End quote ---
That looks correct to me, but make sure a) that an empty directory already exists at /mnt/media and that it is accessible for your user, and then b) after adding the line to your fstab run the mount test I described in my previous post to make sure it mounts correctly before you reboot.
You can see if the directory exists and its permissions by typing
--- Code: ---ls -la /mnt
--- End code ---
--- Quote from: bob on April 04, 2025, 12:04:43 pm ---Shouldn't he specify the uid and gid on mount so it's writable by the user?
or use the user option added to defaults?
--- End quote ---
So you definitely need those options for remote or network mounts (because the remote drive permissions need to be mapped to a local user/group), but I've never used uid/gid mount options for mounting *local* disks and have no trouble accessing things. They do need to make sure the mountpoint (/mnt/media) is user accessible, but that's about it for local drives in my experience.
--- Quote from: Awesome Donkey on April 04, 2025, 12:26:19 pm ---If you need a GUI and you're using Ubuntu, you can open GNOME's Disks app and manage it from there too so it's automounts on boot.
--- End quote ---
I didn't realize Gnome Disks allowed you to permanently change mount options. That's good to know. I just clicked around and didn't see how to do it, which sub menu is it in?
sg27:
Okay. I was able to verify through Dolphin that the drive isn't mounting on startup because when I go in there, I get a message at the top that says "the file or folder /media/sophie/data does not exist" even though the drive appears on the Devices list in the left hand column. Data is the name of the volume. As soon as I click on Data under Devices, the message disappears and I can access all of the files.
When I access the device called Data through the drive itself on the Linux desktop, I can then click on "Other Locations," right click on the volume called Data in the main screen and then I am given the option to open the device in Disks. Then, I can click the gear icon under Volumes and click "Edit Mount Options." I have attached to images to show you what I see. When I look at the drive under Disks, it looks like it is set When I look at the Mount Options, it looks like it is set to mount to the directory /media/sophie/data. Inside the media/sophie folder, there is no empty directory called Data. Could this be my issue? I tried to test this out by adding a folder called Data to the Sophie folder and it appears I don't have permission. When I right click on the Media folder or the Sophie folder to change the permissions, it's owned by the root. Is there a way to give a user administrative privileges similar to Windows or is that even appropriate in Linux?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version