How so??altair4 wrote:
Besides ntfs-config just makes a mess of things.
I've used it for several years now without a single glitch..
How so??altair4 wrote:
Besides ntfs-config just makes a mess of things.
Code: Select all
00000000 ef bb bf 23 20 2f 65 74 63 2f 66 73 74 61 62 3a |...# /etc/fstab:|
00000010 20 73 74 61 74 69 63 20 66 69 6c 65 20 73 79 73 | static file sys|
00000020 74 65 6d 20 69 6e 66 6f 72 6d 61 74 69 6f 6e 2e |tem information.|
00000030 0a 23 0a 23 20 55 73 65 20 27 62 6c 6b 69 64 27 |.#.# Use 'blkid'|
00000040 20 74 6f 20 70 72 69 6e 74 20 74 68 65 20 75 6e | to print the un|
00000050 69 76 65 72 73 61 6c 6c 79 20 75 6e 69 71 75 65 |iversally unique|
00000060 20 69 64 65 6e 74 69 66 69 65 72 20 66 6f 72 20 | identifier for |
00000070 61 0a 23 20 64 65 76 69 63 65 3b 20 74 68 69 73 |a.# device; this|
00000080 20 6d 61 79 20 62 65 20 75 73 65 64 20 77 69 74 | may be used wit|
00000090 68 20 55 55 49 44 3d 20 61 73 20 61 20 6d 6f 72 |h UUID= as a mor|
000000a0 65 20 72 6f 62 75 73 74 20 77 61 79 20 74 6f 20 |e robust way to |
000000b0 6e 61 6d 65 20 64 65 76 69 63 65 73 0a 23 20 74 |name devices.# t|
000000c0 68 61 74 20 77 6f 72 6b 73 20 65 76 65 6e 20 69 |hat works even i|
000000d0 66 20 64 69 73 6b 73 20 61 72 65 20 61 64 64 65 |f disks are adde|
000000e0 64 20 61 6e 64 20 72 65 6d 6f 76 65 64 2e 20 53 |d and removed. S|
000000f0 65 65 20 66 73 74 61 62 28 35 29 2e 0a 23 0a 23 |ee fstab(5)..#.#|
00000100 20 3c 66 69 6c 65 20 73 79 73 74 65 6d 3e 20 3c | <file system> <|
00000110 6d 6f 75 6e 74 20 70 6f 69 6e 74 3e 20 20 20 3c |mount point> <|
00000120 74 79 70 65 3e 20 20 3c 6f 70 74 69 6f 6e 73 3e |type> <options>|
00000130 20 20 20 20 20 20 20 3c 64 75 6d 70 3e 20 20 3c | <dump> <|
00000140 70 61 73 73 3e 0a 23 20 2f 20 77 61 73 20 6f 6e |pass>.# / was on|
00000150 20 2f 64 65 76 2f 73 64 61 36 20 64 75 72 69 6e | /dev/sda6 durin|
00000160 67 20 69 6e 73 74 61 6c 6c 61 74 69 6f 6e 0a 55 |g installation.U|
00000170 55 49 44 3d 30 65 62 62 30 32 38 61 2d 61 33 64 |UID=0ebb028a-a3d|
00000180 33 2d 34 61 35 61 2d 61 39 66 33 2d 31 65 61 64 |3-4a5a-a9f3-1ead|
00000190 38 32 33 65 65 35 37 62 20 2f 20 20 20 20 20 20 |823ee57b / |
000001a0 20 20 20 20 20 20 20 20 20 65 78 74 34 20 20 20 | ext4 |
000001b0 20 65 72 72 6f 72 73 3d 72 65 6d 6f 75 6e 74 2d | errors=remount-|
000001c0 72 6f 20 30 20 20 20 20 20 20 20 31 0a 23 20 73 |ro 0 1.# s|
000001d0 77 61 70 20 77 61 73 20 6f 6e 20 2f 64 65 76 2f |wap was on /dev/|
000001e0 73 64 61 35 20 64 75 72 69 6e 67 20 69 6e 73 74 |sda5 during inst|
000001f0 61 6c 6c 61 74 69 6f 6e 0a |allation.|
Code: Select all
kdesudo kate /etc/fstab
Code: Select all
sudo mount -a
If that doesn't fix it we'll have to wait for WharfRat's recommendation on how to fix this.00000000 ef bb bf 23 20 2f 65 74 63 2f 66 73 74 61 62 3a |...# /etc/fstab:|
I wouldn't have known about that byte order thingy. I don't see anything like that in pluma so I would have just sent the fstab file back withaltair4 wrote:Run this command again:
kdesudo kate /etc/fstab
Then select the Tools button and deselect "Add Byte Order Mark (BOM)"
If that doesn't fix it we'll have to wait for WharfRat's recommendation on how to fix this.
Code: Select all
cat > /etc/fstab << "EOF"
...
...
EOF
At the very least we all know now that the mount error referred to the actual first line in/etc/fstab and not the first uncommented linealtair4 wrote:KDE gives me the willies