Jump to content

Ubuntu 14.04 Unable to Access Data Drive--hibernation conflict without hibernation files

Go to solution Solved by Jonny,

Go in to windows and shut it down correctly. Also see if Fastboot is enabled in windows 10 that could make it have a conflict

Hi everyone,

 

I've recently installed Ubuntu on an old SSD I had sitting around, and I'm having a problem accessing the my data drive. It's a Seagate Constellation 1 TB HDD, has no OS on it (I have Windows 10 Technical Preview installed on my Samsung 840 EVO) but when I try to view files on it or mount it I get this message:

 

Unable to access Seagate HDD

 

Error mounting /dev/sdc1 at /media/ian/Seagate HDD: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" "/dev/sdc1" "/media/ian/Seagate HDD"' exited with non-zero exit status 14: The disk contains an unclean file system (0, 0).

Metadata kept in Windows cache, refused to mount.
Failed to mount '/dev/sdc1': Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown
Windows fully (no hibernation or fast restarting), or mount the volume
read-only with the 'ro' mount option.

 

I'm pretty rusty with Ubuntu but I"m reasonably familiar with Terminal. But I can't figure out why it's giving me this error. As I understand it, this is usually an error originating from having Windows go into hibernation mode and then booting into Ubuntu, causing the Windows drive to appear unsafe for access since making changes could corrupt the wake up cycle. However, as this is not a Windows drive but simply a data drive, I can't see why this error is occurring.

 

Anyone know how to solve this issue?

 

EDIT: I did also find this line of code suggested to solve the problem but I am uneasy about trying it as the original poster warned that it would delete all hibernation files on the drive. I'm fairly certain I don't have any since I never even used hibernation on any version of Windows I've used, but I'd still like to confirm that I won't be harming my Windows installation (especially since I'm running Windows 10 Technical Preview and it has been rock solid so far). The sudo command is:

 

 

 

sudo mount -t ntfs-3g -o remove_hiberfile /dev/sde2 /media/FE46D60C46D5C615

Fractal Design Arc Midi R2 | ASUS Z97-A | Intel Core i5 4690K | G.Skill Ripjaw 4 GB (desperately needs upgrade) | MSI Radeon R9 290 | EVGA SuperNOVA 750 G2 | Samsung 840 EVO 250 GB SSD | Seagate Constellation 1 TB HDD (also needs upgrade) | NZXT Kraken X61 for CPU | NZXT Kraken X61 + G10 for GPU | Corsair M45 | CM Storm Quickfire TK | ASUS Xonar DSX | Denon AD-H2000

Link to comment
Share on other sites

Link to post
Share on other sites

 

What is meaning of this?

Fractal Design Arc Midi R2 | ASUS Z97-A | Intel Core i5 4690K | G.Skill Ripjaw 4 GB (desperately needs upgrade) | MSI Radeon R9 290 | EVGA SuperNOVA 750 G2 | Samsung 840 EVO 250 GB SSD | Seagate Constellation 1 TB HDD (also needs upgrade) | NZXT Kraken X61 for CPU | NZXT Kraken X61 + G10 for GPU | Corsair M45 | CM Storm Quickfire TK | ASUS Xonar DSX | Denon AD-H2000

Link to comment
Share on other sites

Link to post
Share on other sites

Go in to windows and shut it down correctly. Also see if Fastboot is enabled in windows 10 that could make it have a conflict

Our Lord and Saviour Chunt!!!

Link to comment
Share on other sites

Link to post
Share on other sites

Go in to windows and shut it down correctly. Also see if Fastboot is enabled in windows 10 that could make it have a conflict

 

I ensured that Windows shut down correctly (multiple times). I will check to see if fastboot is enabled, but I don't quite understand why that would cause the data drive to show this error. The same error does occur on my Windows drive (840 EVO), but that I can completely understand and expect. I will report back when I have investigated whether Fastboot is enabled or not.

Fractal Design Arc Midi R2 | ASUS Z97-A | Intel Core i5 4690K | G.Skill Ripjaw 4 GB (desperately needs upgrade) | MSI Radeon R9 290 | EVGA SuperNOVA 750 G2 | Samsung 840 EVO 250 GB SSD | Seagate Constellation 1 TB HDD (also needs upgrade) | NZXT Kraken X61 for CPU | NZXT Kraken X61 + G10 for GPU | Corsair M45 | CM Storm Quickfire TK | ASUS Xonar DSX | Denon AD-H2000

Link to comment
Share on other sites

Link to post
Share on other sites

I ensured that Windows shut down correctly (multiple times). I will check to see if fastboot is enabled, but I don't quite understand why that would cause the data drive to show this error. The same error does occur on my Windows drive (840 EVO), but that I can completely understand and expect. I will report back when I have investigated whether Fastboot is enabled or not.

Also do a chkdisc as well somties that can fix the error by running that in windows before trying to access in ubuntu/linux

Our Lord and Saviour Chunt!!!

Link to comment
Share on other sites

Link to post
Share on other sites

Also do a chkdisc as well somties that can fix the error by running that in windows before trying to access in ubuntu/linux

 

I disabled Fastboot and I'm running a chkdsk scan now. I will shut down and boot into Ubuntu and then let you know. 

Fractal Design Arc Midi R2 | ASUS Z97-A | Intel Core i5 4690K | G.Skill Ripjaw 4 GB (desperately needs upgrade) | MSI Radeon R9 290 | EVGA SuperNOVA 750 G2 | Samsung 840 EVO 250 GB SSD | Seagate Constellation 1 TB HDD (also needs upgrade) | NZXT Kraken X61 for CPU | NZXT Kraken X61 + G10 for GPU | Corsair M45 | CM Storm Quickfire TK | ASUS Xonar DSX | Denon AD-H2000

Link to comment
Share on other sites

Link to post
Share on other sites

Looks like Fastboot was the culprit, I can now access my data drive. Thanks Jonny!

Fractal Design Arc Midi R2 | ASUS Z97-A | Intel Core i5 4690K | G.Skill Ripjaw 4 GB (desperately needs upgrade) | MSI Radeon R9 290 | EVGA SuperNOVA 750 G2 | Samsung 840 EVO 250 GB SSD | Seagate Constellation 1 TB HDD (also needs upgrade) | NZXT Kraken X61 for CPU | NZXT Kraken X61 + G10 for GPU | Corsair M45 | CM Storm Quickfire TK | ASUS Xonar DSX | Denon AD-H2000

Link to comment
Share on other sites

Link to post
Share on other sites

No problem :) I had that erorr before but with windows 7 because of hybernation.

Our Lord and Saviour Chunt!!!

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×