Can not mount drive

[Edward78]

Dolpjin tells me, An error occurred while accessing ‘Data’, the system responded: An unspecified error has occurred: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. I checked & repaired the drive in KDE Par. Man. T ook 00:00 like it did nothing, so not fixed.

It qas mounting fine a few hoars ago. The breaker tripped is the only issue that happed. Dolphin seems to have issues with this, it just haooens sometimes, never happened before the switch to KDE/ I

[Aragorn]

@Edward78

Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

1. How is this drive connected?
2. What is the filesystem on that drive?
3. Have you tried manually mounting it by way of the command line?
4. Have you read the following tutorial?

[Tutorial] Working with additional 'drives'

Difficulty: ★★☆☆☆ 1. INTRODUCTION Microsoft Windows started its life as a graphical user interface on top of MS-DOS, a 16-bit single-user, single-tasking operating system that in turn originated as 86DOS, an unauthorized 16-bit rewrite (by Tim Paterson of Seattle Computer) of Digital Research’s originally 8-bit CP/M operating system. Both CP/M and MS-DOS were at the time developed for computers that did not support any other storage media than floppy disks. Considering this legacy, Microsof…

[Edward78]

Onternal ssd, NTFS & no. Not really a CLI person, so I am almost never in it.

[Aragorn]

You said “the breaker tripped”. So what you’re saying is that you had an unclean shutdown?

In that case, given that it’s ntfs, you need to repair the drive with CHKDSK.EXE from within Windows. If you do not have Windows installed anymore, then there are Windows live images you can download and put on a USB stick, and then you can boot up from that.

[Edward78]

Ok, thanks.

[Edward78]

Had to go to properties of drive in Windows to do a repair, chkdsk, said it was fine. It was not.

[Aragorn]

Try following the advice in my tutorial to see whether you can get it to work that way, but if you cannot, then report back with the exact error messages.

There is always a chance that whatever tripped the circuit breaker has damaged you drive.

[Edward78]

I fixed it, went to drive right clicked in windows, went to properties, tools & checked drive for errors, That did it.

[BG405]

If you haven’t done this already, I’d recommend, modified from another post of mine:

In windows, open an elevated command prompt and run powercfg -h off. This helps a least reduce these mount issues; apparently also gets rid of the hiberfil.sys file.

N.B. If it’s not a partition you really need to access from Windows, I’d recommend backing up the data and putting it on an ext4 partition instead.

[cscs]

@BG405

In windows, open an elevated command prompt and run powercfg -h off. This helps a least reduce these mount issues; apparently also gets rid of the hiberfil.sys fil

This disables hibernation in windoze.
(which is also the default operation of ‘shut down’, and the same as disabling ‘Fast Startup’).

Fully shutting down is a requirement when multibooting.

And honestly even on a solely windoze machine I would still disable the ‘feature’.