|
How do I access my Windows Formatted Hard Drive in Knoppix?
I am using Knoppix to access my data on my Windows Formatted Hard Drive but it does not allow me in. It pops up as sdc1 and displays a weird message displayed below when I click on it. Does not give me any other options.
mount: /dev/sdc1 is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. How can I access the hard drive and pull my data out of the download folder? please help. |
Quote:
With that and the proper mount options or fstab entry, you should be good afterward. |
What knoppix version do you have?
How are you trying to access it, by mount command or thorough a gui file manager? |
To Rickkkk
It is connected by a USB adapter to SATA. Where do I or how can I download ntfs-3g package? I am running Knoppix 7.7 off of a USB stick. |
Jefro
I believe it is Knoppix 7.7 that is what it says on the desktop screen. I was trying to mount it but the path to destination does not matter. Or that matters is me getting their. I like to access the folder/files the original way it was organized in Windows. I ran recovery software in Windows and it just throughs the data all over the place. Organizes it based on what it is/Was instead of how I had originally organized. I would have spend years reorganizing everything if I chose the recovery software way. |
Quote:
*** time passing *** .. OK, after a quick search, it appears that Knoppix live DOES include ntfs support. So this is odd. We need to determine the file system of the disk you are trying to read ... Could you please try this command and show us the result : $ lsblk -f |
Having recently been crushed in another thread along these same lines, I have to ask,
Are any of the hosts a virtual machine? Hi Rikkkk ;) |
NTFS-3G should be in Knoppix. Use the built in file manager to open the internal drive. Read on ntfs has been in linux forever. In this case you don't really need to write to it, just read. Don't attempt to add ntfs-3g in yet.
The drive sdc1 seems odd to me. Think we need to verify that. Guess you can run the partition manager in knoppix. Guess you could see if testdisk would see anything. |
Quote:
|
Quote:
I am not familiar with Linux let alone Knoppix. Is there a user guide some where on the internet? I ran the command in Knoppix LXTerminal and it stated bash command not found. |
Quote:
At this point I just want my downloads from the download folder. Many people on the Internet say what you cannot do in Windows you can do in Linux. And the #1 Linux for data recovery is Knoppix which brings me here. |
I'm surprised the "lsblk -l" command returned the message it did. Try running the fdisk -l or gdisk -l commands (Lower Case Letter L in the command). I'm not sure if Knoppix uses sudo, so try preceding each of the commands with sudo and if that fails enter: su - and hit the enter key and if prompted for a password, hit the enter key again. I don't think a Knoppix Live DVD has a password but I guess you'll find out.
With windows 10, you have hibernate always on unless you manually turn it off. That leads to problems accessing from any Linux but the output you posted doesn't look like that is the problem. More likely, from your last post, you have a corrupted filesystem on your windows partition and will probably need your windows DVD or some other windows software to repair that. Do an online search "how to use knoppix" and you will get countless results, pick one. |
Quote:
http://www.webupd8.org/2015/06/workarounds-for-not-being-able-to-mount.html?m=1 |
Quote:
- As you may have already experienced, one can sometimes worsen a situation while trying to fix a problem. That doesn't mean you shouldn't try to fix things yourself, just that if you have absolutely no experience with the issue, it is best to do some research before starting. - That said, in my experience, it is rare that events such as you describe would lead to not being able to recover ANY data from the affected disk ... so keep the faith for now ;-) - Not being familiar with linux is not a weakness - everyone starts somewhere. Your instinct to ask for help (from this community, for example) is a good one. - Concerning the problem at hand: I agree with the suggestion made by at least 2 other members here, that Windows' hybrid/hibernation function may have made the disk temporarily inaccessible. As suggested by yancek, I believe the safest way to troubleshoot this issue is by booting the Windows 10 installation DVD or accessing the recovery partition at boot. This would mean reinstalling the disk into the system it is normally part of and restarting. You may want to consult folks either in this thread (if they are willing to help - this is after all a linux forum ...) or on a Windows-based forum before trying things you are unfamiliar with. Personally, I would be happy to continue to help you, since I dual-boot Windows 10 and linux on most of my computers and have extensive experience on both OS'es. - If that doesn't yield any results, and we're getting a little ahead of ourselves here, we may have to try resolving this with a different version of linux. I echo yancek's surprise at the lsblk command being absent from knoppix, or from ANY version of linux .. It is a fairly basic command going back to the Unix roots of all 'nix systems ... Those are my comments and suggestions - best of luck, keep us informed and don't hesitate to get back to us for help. |
I suspect the drive is formatted as NTFS and the "dirty" bit is set - which it would be if the file system wasn't closed properly when it crashed.
You will need to get the file system checked either using Windows CHKDSK /F or a packaged NTFS file utility in Linux. |
| All times are GMT -5. The time now is 11:55 AM. |