More > JRiver Media Center 33 for Linux
MC 33 with Ubuntu 24.04.2 LTS - intermittent file not found error on playback
mwillems:
So one question that OP has never answered is how the internal drive is actually mounted in software. We know it's not the OS drive, so there's no guarantee it's actually automounted on boot. Here's a theory of the case and tell me if you think this could be you:
1) The drive is not mounted in the fstab (or is listed in the fstab, but has an option flag that prevents automounting on boot)
2) When you reboot and try to play in JRiver the file appears unavailable because the drive isn't mounted.
3) You then open your file manager which then detects and automagically mounts the drive like a removable drive. Because this is transparent to you, the files look like they've been there the whole time.
4) What happens if you go back to JRiver MC and try to play a file *after* you've navigated to the files in your file manager on any given boot?
If the answer to 4) is "the file plays" then my hunch is right and you might just need to actually mount the drive on boot in your fstab. If the answer to 4) is the file is still unavailable in MC, what steps do you normally go through to get things playing in MC?
Alternatively, reboot and then (before doing anything else) run the terminal command "lsblk" and post the output here. Also post the contents of the file at /etc/fstab
sg27:
Here's the lsblk output taken immediately after reboot. It looks like the drive is mounting. Here is fstab. For testing purposes, I am simply opening MC33, finding Rockville through the search box and clicking play.
mwillems:
--- Quote from: sg27 on April 04, 2025, 10:52:33 am ---Here's the lsblk output taken immediately after reboot. It looks like the drive is mounting.
--- End quote ---
Just the opposite, your lsblk shows that your extra drive is not actually mounting on boot at all. The lsblk shows the disks that exist in the left column and the mountpoints in the far right column. The only physical disk partitions that are mounted are two partitions on /dev/sda (i.e. your root and boot partitions). By contrast /dev/sdb (which is probably your second internal drive) has one partition that is not mounted anywhere. Which makes sense because your second drive has no entry in the fstab: the only drives in the fstab are the root and boot partitions for the OS drive.
So your problem is almost certainly that your internal drive is not being automatically mounted on boot (only when you try to browse to it in the OS file manager). You should add your drive to the fstab so that it mounts automatically on boot, which should solve your issue.
sg27:
Great. It sounds like we have found the problem. How do I fix it? I am very new to linux.
mwillems:
--- Quote from: sg27 on April 04, 2025, 11:04:09 am ---Great. It sounds like we have found the problem. How do I fix it? I am very new to linux.
--- End quote ---
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version