Thanks for the quick response. The machine is an old pc that was retired when the disk crashed. So I put in a small SSD and installed Linux mint. The plan is to build a ‘proper’ media centre but for now I’m using it as a test bed to what works best and learn Linux. I think you are right about mounting the disk, (not something I have had to do before) It is a 'local' disk that was added after the OS was installed and I recall that when I first ran MC21 I only had a few music files but they were on the SSD and I don’t recall this issue cropping up then. I have attached a screen shot from the terminal as requested.
That confirms my suspicion. For purposes of Linux learning I'll explain some theory instead of just telling you what to do:
lsblk lists the block devices (typically disk drives) on your system. You can see that you have three block devices:
1) sda: The "sd" originally stood for SCSI device, but the category also includes SATA devices now (IDE drives and removable media have different prefixes). This drive has three partitions on it, each denoted by adding a number after the "sda" (although the swap is curiously numbered "5", did the drive previously have more partitions?). In any case you can see that the partition sda1 is mounted at "/" which means it's the root partition. So I'm assuming that's your SSD.
2) sdb: This is your second SCSI/SATA drive and based on the size I'm assuming it's your WD Red. It has one partition (sdb1) that is mounted under /media. /media or /run are where linux systems mount transient or removable media (like cd roms or external hard drives). The fact that it's mounted there (using a long random looking mount point) is a strong hint that the partition is being auto-mounted when accessed by the file manager rather than mounted at boot.
3) sr0 usually refers to a CD-ROM drive. You'll note that it's mounted under /media.
So with that in hand we can have a look at the fstab, which stands for Filesystem Table and is where the OS looks to find instructions on how and where to mount drives at boot. You can see that there are only three lines that aren't commented out: it's only auto-mounting the root partition, the swap partition, and a floppy disk drive (that doesn't appear to be connected to the system anymore based on the lsblk?).
That confirms that sdb1 isn't being mounted at boot. So you need to add a line to your fstab file to mount sdb1. The entries are structured as six entries separated by spaces or tabs (any number of spaces is the same as one space, so it's important there aren't spaces within the entries).
/device/to/be/mounted /place/to/mount/it filesystemtype options dump pass
The device to be mounted can be expressed either as a filesystem location (e.g. /dev/sdb1)or a universal unique identifier (UUID). Looking at your fstab, your root partition is being mounted by UUID instead of filesystem location if you want to see what a UUID looks like. UUIDs are "safer" as the block device ordering is not guaranteed to be stable across reboots (but usually is), with the result that sometimes what is sda today may be sdb tomorrow. If you experience that, you'll need to use UUID's in your fstab. The blkid command will tell you the UUIDs of all your block devices (but typically needs to be run as root or with sudo).
However, for most systems the block device ordering is stable enough unless you're adding or removing disks, so filepath works just fine. So we'll start with that because it's easier. Assuming your WD Red is formatted ext4 like your root partition you'd want to add a line like this to your fstab:
/dev/sdb1 /home/mh/data ext4 rw,defaults 0 0
You would need to make a directory called "data" in your user's home directory (/home/mh) first for this to work. You'll also need to edit the fstab as a privileged user (i.e. use sudo). Ask if you need any tips. If you find that your wd red is not consistently sdb, you'll need to use a UUID for the first entry instead.
More info here:
https://wiki.archlinux.org/index.php/fstabHope this helps!
Author
Topic: 'Something went wrong with playback' (Read 7367 times)