+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Cannot Access HDD (/t-cannot-access-hdd)
Pages:
1
2
RE: Cannot Access HDD - TheDreadPirate - 2024-08-18
sudo apt install mount
RE: Cannot Access HDD - Disentomb - 2024-08-18
I'm still getting the unknown command with unmount despite mount already being installed and up to date
Code:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
mount is already the newest version (2.39.3-9ubuntu6).
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.I'll provide all the previous info like OP did as welll.
Output of sudo ls -l /dev/disk/by-id/
Code:
total 0
lrwxrwxrwx 1 root root 9 Aug 18 09:37 ata-ST18000NM001J-2TV113_ZR50SZ55 -> ../../sda
lrwxrwxrwx 1 root root 13 Aug 18 09:37 nvme-eui.0025385c81b0dcfc -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Aug 18 09:37 nvme-eui.0025385c81b0dcfc-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Aug 18 09:37 nvme-eui.0025385c81b0dcfc-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 13 Aug 18 09:37 nvme-Samsung_SSD_970_EVO_1TB_S467NX0KC12734E -> ../../nvme0n1
lrwxrwxrwx 1 root root 13 Aug 18 09:37 nvme-Samsung_SSD_970_EVO_1TB_S467NX0KC12734E_1 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Aug 18 09:37 nvme-Samsung_SSD_970_EVO_1TB_S467NX0KC12734E_1-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Aug 18 09:37 nvme-Samsung_SSD_970_EVO_1TB_S467NX0KC12734E_1-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Aug 18 09:37 nvme-Samsung_SSD_970_EVO_1TB_S467NX0KC12734E-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Aug 18 09:37 nvme-Samsung_SSD_970_EVO_1TB_S467NX0KC12734E-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 9 Aug 18 09:37 wwn-0x5000c500dca9571b -> ../../sdaOutput of df -h
Code:
Filesystem Size Used Avail Use% Mounted on
tmpfs 3.2G 5.2M 3.2G 1% /run
/dev/nvme0n1p2 916G 19G 851G 3% /
tmpfs 16G 4.0K 16G 1% /dev/shm
tmpfs 5.0M 12K 5.0M 1% /run/lock
tmpfs 3.2G 96K 3.2G 1% /run/user/120
tmpfs 3.2G 2.5M 3.2G 1% /run/user/1000
/dev/sda 17T 4.9T 11T 32% /media/disentomb/Jelly DriveOutput of fdisk -l
Code:
Disk /dev/loop0: 4 KiB, 4096 bytes, 8 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop1: 55.66 MiB, 58363904 bytes, 113992 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop2: 63.95 MiB, 67051520 bytes, 130960 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop3: 74.24 MiB, 77844480 bytes, 152040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop4: 74.24 MiB, 77848576 bytes, 152048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop5: 269.32 MiB, 282402816 bytes, 551568 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop6: 268.65 MiB, 281702400 bytes, 550200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop7: 10.72 MiB, 11239424 bytes, 21952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 970 EVO 1TB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: AE2B72A5-720B-41AA-826F-A97287E01D0A
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 4095 2048 1M BIOS boot
/dev/nvme0n1p2 4096 1953521663 1953517568 931.5G Linux filesystem
Disk /dev/sda: 16.37 TiB, 18000207937536 bytes, 35156656128 sectors
Disk model: ST18000NM001J-2T
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/loop8: 349.7 MiB, 366682112 bytes, 716176 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop9: 505.09 MiB, 529625088 bytes, 1034424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop10: 91.69 MiB, 96141312 bytes, 187776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop11: 7.39 MiB, 7745536 bytes, 15128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop12: 10.32 MiB, 10821632 bytes, 21136 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop13: 38.73 MiB, 40615936 bytes, 79328 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop14: 38.83 MiB, 40714240 bytes, 79520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop15: 476 KiB, 487424 bytes, 952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop16: 321.1 MiB, 336699392 bytes, 657616 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop17: 453.06 MiB, 475066368 bytes, 927864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop18: 497.79 MiB, 521965568 bytes, 1019464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop19: 495.16 MiB, 519217152 bytes, 1014096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytesOutput of sudo nano /etc/fstab
Code:
/dev/disk/by-uuid/93a32ff4-a2ea-472c-bf0e-a3a05105a854 / ext4 defaults 0 1
/swap.img none swap sw 0 0
/dev/disk/by-id/wwn-x5000c500dca9571b /media/disentomb/Jelly Drive ext4 defaults 0 0Thanks for the help as always.
RE: Cannot Access HDD - TheDreadPirate - 2024-08-18
I made a typo in my earlier thread. It is "umount" instead of "unmount". umount is provided by the mount package. Your other option is to reboot to apply the new fstab.
BUT, before you do any of that, you need to put the mount path in quotes since there is a space in the folder name.
Code:
/dev/disk/by-id/wwn-x5000c500dca9571b "/media/disentomb/Jelly Drive" ext4 defaults 0 0Additionally, as I suggested earlier, you should move this out of /media/disentomb. Since the OS's auto-mount will apply an ACL to /media/disentomb the next time you plug in a USB drive or something.
Code:
sudo umount "/media/disentomb/Jelly Drive"
sudo mount -aRE: Cannot Access HDD - Disentomb - 2024-08-19
All worked out, although for my HDD the "wwn..." didn't seem to be the correct id, I replace it with the "ata..." and it worked.
Thanks