[ SOLVED ] USB drive partition not mounting @ connection

[H]

Daveboy:

Thank you for that link. Greatly appreciated. I worked my way through it and the process it advised.

Yes, upon reboot all is fixed and forgiven.

Very pleased that this is now resolved.
thank you
regards
H

[Daveyboy]

Would the information contained in this link help solve your problem ?

https://www.tutorialspoint.com/how-to-fix-quot-ntfs-partition-failed-to-mount-quot-error-in-linux

[stevef]

I appreciate your help

You're welcome.

The disk is quite full and is 1TB, so i dont have anywhere big enough to transfer the data too

Hope the data isn't too important then.

As your preference was not to have to use the command line, chkdsk remains an option to fix the problem properly. I was advising caution as without a current Windows system I can't be sure how Windows behaves when an NTFS/ext4 dual partitioned drive is plugged in.
I do recall older Windows immediately trying to re-format any ext4 drive that got plugged in which always worried me.
If you use the drive in a Windows system you'll know what happens.
Clearly you should be able to decline the Windows offer to reformat and then identify the NTFS partition and run chkdsk on it - provided you take due care.

An NTFS disk with dirty status indicates that the file system may be in an inconsistent state.

If it is mounted and used as though it is 'clean' the inconsistent state may cause data loss.
You may be fine, but there is a risk.  On a USB stick used only to copy the odd file or two from one place to another you might accept the risk.
But if there's 1TB of important data that only exists on the Seagate drive then that's a different matter.

Refusing to mount a dirty NTFS disk is technically the correct behaviour.
If a system automatically mounts a dirty NTFS disk (or allows it to be mounted from the CLI without reporting the flag) it is hiding the risk.

Using ntfsfix with the -n option, is a dry run. 'Do not write anything, just show what would have been done.'

Since it is a Windows issue the correct thing is to get Windows to fix it.
ntfsfix can fix some NTFS inconsistencies but it is not chkdsk.

I'll move this thread to Hardware->Hard Drives and SSDs which is probably a better fit than Software->Support->Other

edit - added further information and explanation

[H]

stevef:

thank you for your reply. I think my best option for now is to continue to mount via command line. I knew chkdsk was not an option. So I think I will just stay with command line.

The disk is quite full and is 1TB, so i dont have anywhere big enough to transfer the data too, in order to re format the seagate.

I appreciate your help though, and I will mark this as solved, in order to close this off.

Kind regards
H.

[stevef]

Ok, LL7 is detecting that the NFTS partition is 'dirty'.
NTFS drives use flags which are Windows specific and don't translate on non-Windows systems.
These are used for things like suspend, encryption etc.
A previous use on a Windows system may left it with one of the NTFS flags set.

You have at least three options.

1) Put the drive in a Windows system and try to clear the flag.  This would normally be the best option - if it was just an NTFS drive.
Simply opening the NTFS partition in Windows and then doing a safe removal may tidy it up enough for Linux to be happy with it.
The problem with a dual partition drive is that Windows will try to get you to reformat because it doesn't understand ext4.
I'd be wary of doing the chkdsk as suggested by the log.

2) Change the Linux system so that it will force mount a dirty disk.  This is probably what is happening when you mount from the command line.
Again this is unsatisfactory because it does not solve the root cause.

3) In your position, I would get all the data I want safely off the USB and then recreate the partitions and copy the data back.

Taking care to 'safely' remove the USB after use in both systems may help prevent it happening again.

Linux support for NTFS has relatively recently been incorporated into the kernel.  The kernel used by LL7 has this native support for NTFS.  Previous versions (LL6, LL5 etc) had older kernels in which the function required additional software called ntfs-3g.

This may be the explanation for why your LL7 system is more 'picky' about this drive than older set ups.

[H]

stevef:

looking at the read out of the journalctl command, i searched and found this command

sudo ntfsfix /dev/sdb1 -n

this did not fix the issue.

I know this issue is only related to LL 7.0 and not linux issue. This partition works with Linux Mint Virginia, it also works on Elive 3.8.42 so
I know it has nothing to do with drive itself, or it would not work on the others as well. The issue is only on LL 7.0

H.

[H]

stevef:

if i create a file ntfs(i can call it anyhting really but I use ntfs as this is the drive I am wanting to read)

/media/ntfs

I can mount it via command line, and it works just fine. I have been using it for the last several hours, with out issue.

sudo mount /dev/sdb1 /media/ntfs

and use umount to un mount with out issue.

regards
H

[H]

Not sure what happened there here is first command

journalctl -b | grep ntfs
Jun 07 21:37:27 linuxlite-N53SV kernel: ntfs3: Max link count 4000
Jun 07 21:37:27 linuxlite-N53SV kernel: ntfs3: Enabled Linux POSIX ACLs support
Jun 07 21:37:27 linuxlite-N53SV kernel: ntfs3: Read-only LZX/Xpress compression included
Jun 07 21:37:27 linuxlite-N53SV kernel: ntfs3: sdb1: It is recommened to use chkdsk.
Jun 07 21:37:27 linuxlite-N53SV kernel: ntfs3: sdb1: volume is dirty and "force" flag is not set!
Jun 07 21:37:39 linuxlite-N53SV kernel: ntfs3: sdb1: It is recommened to use chkdsk.
Jun 07 21:37:39 linuxlite-N53SV kernel: ntfs3: sdb1: volume is dirty and "force" flag is not set!

[H]

Thank you stevef, for your reply.

Yes I was aware NTFS is supported by Linux, have been using it for years. This is the first time I have encountered a problem.

Just to clarify, this drive has 2 partitions ext4 which does laod no problem, and the NTFS partition which always loads on other Linux distributions is only failing here.

I have copied below the outcome of your request, look forward to your advise, thank you.

journalctl -b | grep ntfs
Jun 07 21:37:27 linuxlite-N53SV kernel: ntfs3: Max link count 4000

journalctl -b --since 21:37
Jun 07 21:37:13 linuxlite-N53SV kernel: usb 3-1: new high-speed USB device number 2 using xhci_hcd
Jun 07 21:37:14 linuxlite-N53SV kernel: usb 3-1: New USB device found, idVendor=0bc2, idProduct=3300, bcdDevice= 1.30
Jun 07 21:37:14 linuxlite-N53SV kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 07 21:37:14 linuxlite-N53SV kernel: usb 3-1: Product: Desktop         
Jun 07 21:37:14 linuxlite-N53SV kernel: usb 3-1: Manufacturer: Seagate
Jun 07 21:37:14 linuxlite-N53SV kernel: usb 3-1: SerialNumber: 2GHJPEQM   
Jun 07 21:37:14 linuxlite-N53SV kernel: usb-storage 3-1:1.0: USB Mass Storage device detected
Jun 07 21:37:14 linuxlite-N53SV kernel: scsi host7: usb-storage 3-1:1.0
Jun 07 21:37:14 linuxlite-N53SV mtp-probe[3669]: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0/usb3/3->
Jun 07 21:37:14 linuxlite-N53SV mtp-probe[3669]: bus: 3, device: 2 was not an MTP device
Jun 07 21:37:14 linuxlite-N53SV kernel: usbcore: registered new interface driver uas
Jun 07 21:37:14 linuxlite-N53SV mtp-probe[3679]: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0/usb3/3->
Jun 07 21:37:14 linuxlite-N53SV mtp-probe[3679]: bus: 3, device: 2 was not an MTP device
Jun 07 21:37:15 linuxlite-N53SV kernel: scsi 7:0:0:0: Direct-Access     Seagate  Desktop          0130 PQ: 0 ANSI: 4
Jun 07 21:37:15 linuxlite-N53SV kernel: sd 7:0:0:0: Attached scsi generic sg3 type 0
Jun 07 21:37:15 linuxlite-N53SV kernel: sd 7:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Jun 07 21:37:15 linuxlite-N53SV kernel: sd 7:0:0:0: [sdb] Write Protect is off
Jun 07 21:37:15 linuxlite-N53SV kernel: sd 7:0:0:0: [sdb] Mode Sense: 2f 08 00 00
Jun 07 21:37:15 linuxlite-N53SV kernel: sd 7:0:0:0: [sdb] No Caching mode page found
Jun 07 21:37:15 linuxlite-N53SV kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through
Jun 07 21:37:15 linuxlite-N53SV kernel:  sdb: sdb1 sdb2
Jun 07 21:37:15 linuxlite-N53SV kernel: sd 7:0:0:0: [sdb] Attached SCSI disk
Jun 07 21:37:21 linuxlite-N53SV kernel: EXT4-fs (sdb2): mounted filesystem 0fd896a3-0c0e-4013-ab71-e72c159606dc r/w with ordered data>
Jun 07 21:37:21 linuxlite-N53SV udisksd[925]: Mounted /dev/sdb2 at /media/linuxlite/BU_Drive on behalf of uid 1000
Jun 07 21:37:21 linuxlite-N53SV dbus-daemon[3017]: [session uid=1000 pid=3017] Activating via systemd: service name='org.gtk.vfs.Meta>
Jun 07 21:37:21 linuxlite-N53SV systemd[2984]: Starting gvfs-metadata.service - Virtual filesystem metadata service...
Jun 07 21:37:21 linuxlite-N53SV dbus-daemon[3017]: [session uid=1000 pid=3017] Successfully activated service 'org.gtk.vfs.Metadata'
Jun 07 21:37:21 linuxlite-N53SV systemd[2984]: Started gvfs-metadata.service - Virtual filesystem metadata service.
Jun 07 21:37:27 linuxlite-N53SV kernel: ntfs3: Max link count 4000
Jun 07 21:37:27 linuxlite-N53SV kernel: ntfs3: Enabled Linux POSIX ACLs support
Jun 07 21:37:27 linuxlite-N53SV kernel: ntfs3: Read-only LZX/Xpress compression included
Jun 07 21:37:27 linuxlite-N53SV kernel: ntfs3: sdb1: It is recommened to use chkdsk.
Jun 07 21:37:27 linuxlite-N53SV kernel: ntfs3: sdb1: volume is dirty and "force" flag is not set!
Jun 07 21:37:39 linuxlite-N53SV kernel: ntfs3: sdb1: It is recommened to use chkdsk.
Jun 07 21:37:39 linuxlite-N53SV kernel: ntfs3: sdb1: volume is dirty and "force" flag is not set!
Jun 07 21:37:27 linuxlite-N53SV kernel: ntfs3: Enabled Linux POSIX ACLs support
Jun 07 21:37:27 linuxlite-N53SV kernel: ntfs3: Read-only LZX/Xpress compression included
Jun 07 21:37:27 linuxlite-N53SV kernel: ntfs3: sdb1: It is recommened to use chkdsk.
Jun 07 21:37:27 linuxlite-N53SV kernel: ntfs3: sdb1: volume is dirty and "force" flag is not set!
Jun 07 21:37:39 linuxlite-N53SV kernel: ntfs3: sdb1: It is recommened to use chkdsk.
Jun 07 21:37:39 linuxlite-N53SV kernel: ntfs3: sdb1: volume is dirty and "force" flag is not set!

thanks
H

[stevef]

Linux does support NTFS and Linux Lite should auto mount an NTFS partition if set to do so, but may not if it detects a problem.
Linux Lite 7 seems to be more 'picky' than LL6

To check what is happening on your system
Do a fresh boot.
Once everything has settled down, note the time (HH:MM) on the system clock.

Insert the dual partition USB and allow time for any auto mounting to complete.
Open a terminal by pressing Ctrl Alt and T together.

In the window that opens type in the following command followed by return.

Code: [Select]

journalctl -b | grep ntfsThis command will show just the ntfs events for this boot and may show the problem.
Post back with the results.

For context, this command will show everything logging since HH:MM
Replace HH:MM with your value.

Code: [Select]

journalctl -b --since HH:MM

[H]

Thank you karlheinz for your reply.

I do not read German, but it looks like your saying it is a windows system drive, and not recognized by Linux.

Linux uses NTFS. I have used NTFS with linux for years. It auto mounts in other systems, only here in LL does it need to be manually mounted. I can read and write to it, but I do need to mount via command line.

I just want to be able to plug usb in and have it working with out mucking around witht he command line.
H.

[karlheinz]

NTFS ist eine Windows Partition,wird wahrscheinlich von Linux nicht erkannt. Die Festplatte mit G-Partet untersuchen und die NTFS Part. in ext.4partitonieren, eventuell eine kleine Part in SWAP und eine ext.4 als Sicherungsdatei.

[H]

I have just installed LL 7.0. I have a USB drive, Seagate, that has 2 partitions on it. one is ext 4, the other NTFS.

When I plug the USB drive in, the ext 4 is recognized and is usable straight up. The NTFS partition is not.

The message for the error is
" wrong fs type, bad option, bad superblock on /dev/sdb1, missing code page or helper program, or other error"

If I load disks and try and mount the partition there, I get the same error.

HOWEVER:
I am able to mount via the commend line. 
If i use sudo mount /dev/sdb1 /media/        . It will load and be usable.

The ownership of the drive is all.

Any advise / help would be greatly appreciated.

I am not a Linux expert, so please do keep it simple if you are able to help.

H.