Page MenuHomeSolus

Can't mount ntfs device
Closed, ResolvedPublic

Description

Hello,

When I try to access my data partition on my disk / dev / sdb1 which is a 1.47 TBD in ntfs it shows me the pop-up below.

Capture du 2017-09-22 08-15-16.png (169×378 px, 8 KB)

Yet it worked well not so long ago.

Would you have an idea of ​​what I have to do to be able to access this disc again?

Thank you in advance.

Sorry for my English ?

Event Timeline

What are you using to mount the device? Files (nautilus)? Try GNOME Disks to have it mounted at boot.

JoshStrobl added a subscriber: JoshStrobl.

This can sometimes occur if it takes too long trying to mount. Just try again or if it's an external USB drive, unplug and plug it back in.

JoshStrobl claimed this task.

Closing due to lack of response.

baimafeima added a subscriber: baimafeima.

I get the same error message when trying to use my external SSD with an MBR partition table and formatted to NTFS. The error messages are:

  • Unable to access "512 GB Volume": No object for D-Bus interface
  • Unable to unmount "512 GB Volume": No object for D-Bus interface

Not sure if this is of any help but dmesg output is:
[ 5943.431007] usb 2-1.2: new high-speed USB device number 3 using ehci-pci
[ 5943.590943] usb 2-1.2: New USB device found, idVendor=125f, idProduct=a67a
[ 5943.590951] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5943.590954] usb 2-1.2: Product: SD700
[ 5943.590957] usb 2-1.2: Manufacturer: ADATA
[ 5943.590959] usb 2-1.2: SerialNumber:
[ 5943.604617] usbcore: registered new interface driver usb-storage
[ 5943.606127] scsi host6: uas
[ 5943.606210] usbcore: registered new interface driver uas
[ 5943.606929] scsi 6:0:0:0: Direct-Access ADATA SD700 9301 PQ: 0 ANSI: 6
[ 5944.108040] sd 6:0:0:0: [sdb] 1000215216 512-byte logical blocks: (512 GB/477 GiB)
[ 5944.108042] sd 6:0:0:0: [sdb] 4096-byte physical blocks
[ 5944.108300] sd 6:0:0:0: [sdb] Write Protect is off
[ 5944.108304] sd 6:0:0:0: [sdb] Mode Sense: 5f 00 00 08
[ 5944.109480] sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5944.115750] sdb: sdb1 sdb2
[ 5944.118159] sd 6:0:0:0: [sdb] Attached SCSI disk
[ 9217.081750] perf: interrupt took too long (2523 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
[11542.822439] sdb:
[11542.827419] sdb:
[11543.021924] sdb:
[11543.027152] sdb:
[11783.362813] sdb:
[11783.475987] sdb:
[12022.240247] sdb:
[12022.444424] sdb:
[12022.581150] sdb:
[12156.252123] sdb:
[12195.414345] sdb: sdb1

In my case, it is an external, freshly bought 512 GB SSD. Just to be sure, was I wrong in creating an MBR/DOS partition table if I only intend to use it for data storage? I have asked about this in different IRC channels and got contradicting answers, some regarding it as necessary in any case, while others considered it not necessary.
@Alphacox Were you able to access the partition again?

I have an internal 2TB drive I use for backup, NTFS. From everything I can see, I have it mounted in a location that says I have rights to read/write, but it will not actually let me write files, or create folders, etc. etc.

polinco77 how are you mounting the drive?

I could reproduce your results mounting with Files file manager, but mounting in /etc/fstab with umask=000 resolved the problem.

Closing once again due to lack of response. If you have further issues, please ensure:

  1. You have fast startup / shutdown in Windows disabled. This will keep your NTFS partition locked.
  2. Create a new task with further details.
JoshStrobl changed the edit policy from "All Users" to "Triage Team (Project)".Jul 20 2018, 1:47 PM