Windows Partitions are Sometimes "Writeable" Sometimes "Read Only"
in BackTrack2 windows partitions was allways "Read Only", after I intsalled BT3 I see they have permission for reading and writing with a big glad.
But sometimes they can be "read only" again. When I open BT3 if it begins with "read only" it always goes like that to the end of season. What makes it in that way or this way? How can I change the settings?
Back Track and linux in general doesnt like NTFS file partitions. I will assume that that is what your windows partition is on. It can behave strangly when you force it to mount. The other thing is your permissions might be whacky. Try using:
"kdsu konquerer"
In command line. If it is a permissions issue then you should be able to make changes from the root browser.
Morpheus: "You take the blue pill - the story ends, you wake up in your bed and believe whatever you want to believe. You take the red pill - you stay in Wonderland and I show you how deep the rabbit-hole goes."
Neo: "What if I take both?"
Morpheus: "Don't do that! You end up like Nick Nolte!"
I have experienced this also when windows did not shutdown properly. I'm not positive that this is the source of the problem or even a contributing factor, but every time I access an NTFS partition when windows has been shutdown correctly it reads and writes fine.
When hungry, eat your rice; when tired, close your eyes. Fools may laugh at me, but wise men will know what I mean. -- Lin-Chi
- - - - - - - -
I slept once, it was a Tuesday.
If I give my current situation as a real example,
I am running BT3 in in my laptop and desktop, everyting was same in the installation process of BT3 because I prepared a USB Stick in my laptop and dublicated (cloned) that stick to an other (same brand and model) second stick. And I dedicated the first USB stick to Laptop and second stick to Desktop. I've only changed the setting in boot file in Desktop from sdb1 to sdc1 for writing "persistan changes". Beacuse partition was seen as sdc1 in my Desktop computer. And there is no other difference between them.
But when I run BT3 from my Laptop, it can easily make every chnage in NTSF partitions, there is no problem for writing, updating, saving new files.
In Desktop computer when I run BT3 it can never change anything in other HD partitions.
I did "kdsu konquerer" but it didn't work. Before I tried it, when I opened my Desktop computer to try that command I saw that this time NTSF partitions are writeable!! So I didn't try.
And in next boot I saw that they became "read only" again and I tried the command but nothing was changed.
I understand linux don't like NTSF partitions but I guess that linux don't decide to allow writing or not in every boot by itsself according to "his emotions!
There must be something triggers it in that way or this way. Anyone has an idea about what makes the difference?
Hi damlayss,
that's not exactly what you were asking for, but maybe you will try this drivers: http://www.ntfs-3g.org/
If u give it a try, feel free to let me know if you were successful.
I for my self never had any problems with NTFS formated disks / partitions.
Be sensitive in choosing where you ask your question. You are likely to be ignored, or written off as a loser, if you:
* post your question to a forum where it's off topic
* post a very elementary question to a forum where advanced technical questions are expected, or vice-versa
* cross-post to too many different newsgroups
* post a personal e-mail to somebody who is neither an acquaintance of yours nor personally responsible for solving your problem
I tried that program but the result was like this below,
Is it really a mystery why linux can not write to partitions?Code:bt / # mount -t ntfs-3g /dev/sdc1 /mnt/windows ntfs-3g: Failed to access volume '/dev/sdc1': No such file or directory Please type '/sbin/mount.ntfs-3g --help' for more information.
Can you post your output ofOriginally Posted by damlayss
Maybe you have another problem that wasn't examined yet.Code:fdisk-l and /etc/fstab
Be sensitive in choosing where you ask your question. You are likely to be ignored, or written off as a loser, if you:
* post your question to a forum where it's off topic
* post a very elementary question to a forum where advanced technical questions are expected, or vice-versa
* cross-post to too many different newsgroups
* post a personal e-mail to somebody who is neither an acquaintance of yours nor personally responsible for solving your problem
This time it gives an other message when I tried to access harddisk with NTFS-3G Stable Read/Write Driver
Code:bt ntfs-3g-1.5012 # mount -t ntfs-3g /dev/sdd1 /mnt/windows -o force $LogFile indicates unclean shutdown (0, 0) WARNING: Forced mount, reset $LogFile. ntfs-3g-mount: failed to access mountpoint /mnt/windows: No such file or directory
fdisk -l gives
Code:bt ntfs-3g-1.5012 # fdisk -l Disk /dev/hdc: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdc1 1 4207 33792696 7 HPFS/NTFS Disk /dev/sda: 4025 MB, 4025810432 bytes 124 heads, 62 sectors/track, 1022 cylinders Units = cylinders of 7688 * 512 = 3936256 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 357 1372277 b W95 FAT32 /dev/sda2 358 1022 2556260 83 Linux Disk /dev/sdc: 2059 MB, 2059403264 bytes 64 heads, 63 sectors/track, 997 cylinders Units = cylinders of 4032 * 512 = 2064384 bytes Device Boot Start End Blocks Id System /dev/sdc1 1 997 2009830+ b W95 FAT32 Disk /dev/sdd: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdd1 1 24321 195358401 7 HPFS/NTFS
Hacking Wireless ...
Guys ...i dont know is this right place, but i have downloaded "Auditor security collection" for hacking wireless networks and says that i should boot my pc with the Cd, but after booting i dont get anything, it stops with INIT process after that nothing is happen .
Please for Help ...
Thanks.
Posting Permissions
