Mounting My Linux Library

Plex Media Server Desktops & Laptops
1

Hi there,

I’m a non-tech professional, attempting to be snazzy and self-autonomous, but I seem to have gone as far as I am able, on my own.

I’m trying to get Plex to recognise my USB hardrives, where my library is, using the the Tips & Tricks guide, here:

And I am unable to follow, past, this:

Having created the directories as root, verify empty (unmounted) directory permissions are 0755 before mounting

The code example is this:

# The location 
[root@lizum chuck]# mkdir /disks /disks/c /disks/media3 /disks/chuck2t
[root@lizum chuck]# chown -R chuck:chuck /disks

[root@lizum chuck]# ls -la /disks
drwxr-xr-x   3 chuck chuck 4096 Jul 27 11:14 .
dr-xr-xr-x. 30  root  root 4096 Jul 27 11:14 ..
drwxrwxrwx   4 chuck chuck 4096 Jul 27 11:04 c
drwxrwxrwx   4 chuck chuck 4096 Jul 27 11:04 chuck2t
drwxrwxrwx   4 chuck chuck 4096 Jul 27 11:04 media3
[root@lizum chuck]#

… and mine is this:

drwxr-xr-x  4 rudy rudy 4096 Feb  4 00:48 .
drwxr-xr-x 27 root root 4096 Feb  4 00:48 ..
drwxr-xr-x  2 rudy rudy 4096 Feb  4 00:48 New
drwxr-xr-x  2 rudy rudy 4096 Feb  4 00:48 Toshy

I hope this makes sense enough for you to help me, and not to have to instantly apologize for my stupidity. Ahem.

Thank you in advance, lovely people.

EDIT:

Just noticed one of my USB drives was originally called New Volume, but seemed like it was unwise as it already become just “New” while trying to mkdir, so tried to rename with disks, and in the terminal…

ntfslabel /dev/sdb2 Westie

…and got this error, each time:

Please boot into Windows TWICE, or use the ‘force’ option.
NOTE: If you had not scheduled check and last time accessed this volume
using ntfsmount and shutdown system properly, then init scripts in your
distribution are broken. Please report to your distribution developers
(NOT to us!) that init scripts kill ntfsmount or mount.ntfs-fuse during
shutdown instead of proper umount.

2

One thing you might want to do here is make the NTFS drive “clean” from the linux perspective.

If you see it mounted now. wherever it is, remember where it’s mounted (the device & partition info)

sudo umount /dev/sdxx
sudo ntfsfix /dev/sdxx

Now check the label to make sure it’s what you want:

sudo ntfslabel /dev/sdxx

If not right,

sudo ntfslabel /dev/sdxx NewLabelName

Lastly, if the UUID info is correct,

sudo mount /ntfs/partition/mount/point

This last step confirms everything in /etc/fstab is correct for that drive.

1 Like
4

Hi Chuck,

I arrived at:

sudo nftslabel /dev/sdxx

And was given:

Volume is scheduled for check.
Please boot into Windows TWICE, or use the ‘force’ option.
NOTE: If you had not scheduled check and last time accessed this volume
using ntfsmount and shutdown system properly, then init scripts in your
distribution are broken. Please report to your distribution developers
(NOT to us!) that init scripts kill ntfsmount or mount.ntfs-fuse during
shutdown instead of proper umount.

5

Did you use ntfsfix

[chuck@lizum ~.501]$ ntfsfix --help
ntfsfix v2017.3.23AR.3 (libntfs-3g)

Usage: ntfsfix [options] device
    Attempt to fix an NTFS partition.

    -b, --clear-bad-sectors Clear the bad sector list
    -d, --clear-dirty       Clear the volume dirty flag
    -h, --help              Display this help
    -n, --no-action         Do not write anything
    -V, --version           Display version information

For example: ntfsfix /dev/hda6

Developers' email address: ntfs-3g-devel@lists.sf.net
News, support and information:  http://tuxera.com
[chuck@lizum ~.502]$
1 Like
6

Hello chuck, I do appreciate the quick responses, even on a Sunday, matey.

So, I did indeed, just gave it a reboot, and another run through and I’m still at our error message, there.

sudo umount /dev/sdb2
sudo ntfsfix /dev/sdb2
Mounting volume… OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector… OK
NTFS volume version is 3.1.
NTFS partition /dev/sdb2 was processed successfully.
sudo ntfslabel /dev/sdb2
Volume is scheduled for check.
Please boot into Windows TWICE, or use the ‘force’ option.
NOTE: If you had not scheduled check and last time accessed this volume
using ntfsmount and shutdown system properly, then init scripts in your
distribution are broken. Please report to your distribution developers
(NOT to us!) that init scripts kill ntfsmount or mount.ntfs-fuse during
shutdown instead of proper umount.

7

@Celestialbiscuit, did you see this:

The reason it’s suggested to use Windows to check/fix the drive is that Windows understands NTFS best, and does the best job of fixing any errors, if there are errors.

But since ntfsfix doesn’t see anything wrong, you can also use ntfsfix -d to clear the dirty flag on the disk. That’s why you’re getting the Volume is scheduled for check. message.

1 Like
8

which ntfs packages installed ?
distro?

it definitely looks like the os has it mounted

1 Like
9

I’m on Kubuntu?

I don’t know how to tell you the ntfs packages, I’m afraid.

Is it safe to re-run with -d flag on ntfsfix?

10

Kloned Ubuntu ? :roll_eyes: LOL

you need to learn how to do things like get package listings. (cough) :wink:

sudo dpkg -l | grep ntfs

now run mount and see if it’s mounted

1 Like
11

rudy@hope:~$ sudo dpkg -1 | grep ntfs
dpkg: error: unknown option -1

Type dpkg --help for help about installing and uninstalling packages [*];
Use ‘apt’ or ‘aptitude’ for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;

12

lowercase L

[chuck@lizum tv2.513]$ sudo dpkg -l | grep ntfs
ii  libntfs-3g883                                               1:2017.3.23AR.3-3ubuntu1              amd64        read/write NTFS driver for FUSE (runtime library)
ii  ntfs-3g                                                     1:2017.3.23AR.3-3ubuntu1              amd64        read/write NTFS driver for FUSE
[chuck@lizum tv2.514]$
1 Like
13 
ii  libntfs-3g88 1:2017.3.23-2ubuntu0.18.04.2 amd64 read/write NTFS driver for FUSE (runtime library)
ii  ntfs-3g 1:2017.3.23-2ubuntu0.18.04.2 amd64 read/write NTFS driver for FUSE
14

And is it mounted? Did you forget ? LOL

(it’s complaining about the init scripts/service so something is amiss there)

15 
/dev/sdb2 on /media/rudy/New Volume type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default
_permissions,allow_other,blksize=4096,uhelper=udisks2)
16

DUH!!!

you can fix a mounted volume! :hammer:
(that’s why Windows forces you to reboot)

  1. Unmount the volume
  2. Now fix the partition
  3. Next change the label
  4. Mount the partition

:wink:

17

Heh. Chuck’s mood is improving, I am pleased to aid in this process.

What am I typing to fix the partition, exactly? To check, I’m to do something other than this again, right?

sudo umount /dev/sdb2
sudo ntfsfix /dev/sdb2
sudo ntfslabel /dev/sdb2

As I again got our old favourite error message, repeating these steps.

18

Improving? :boom:

:rofl:

1 Like
19

Show me the console output please?

I may be good at this but not a mindreader :wink:

1 Like
20

You’ll probably need to close all the graphical windows plus anything which refers to the drive.

Then –

sudo umount -f /dev/sdb2

If it still complains – Reboot the box

1 Like
21 
rudy@hope:~$ sudo umount /dev/sdb2
[sudo] password for rudy: 
rudy@hope:~$ sudo ntfsfix /dev/sdb2
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sdb2 was processed successfully.
rudy@hope:~$ sudo ntfslabel /dev/sdb2
Volume is scheduled for check.
Please boot into Windows TWICE, or use the 'force' option.
NOTE: If you had not scheduled check and last time accessed this volume
using ntfsmount and shutdown system properly, then init scripts in your
distribution are broken. Please report to your distribution developers
(NOT to us!) that init scripts kill ntfsmount or mount.ntfs-fuse during
shutdown instead of proper umount.