Hello All,
I wanted to try out this month's Chip DVD which showed a blank disk in Etch. It has Kubuntu 6.10. So I rebooted to try out the same dvd in windows. However I missed the boot-loader and it booted back into Debian. While it was in progress, I gave the 3 finder salute and the pc rebooted decently and this time I selected xp. However it would not load beyond the account login part.
I attached a spare hdd and booted into debian and backed up my entire disk for safety. Then using the xp recovery console I gave the command 'chkdsk c: /p' and now I am able to boot into the admin account only and that too slowly. Many features have got disabled. In short, I got to reload windows for the first time ever since I got the system 5 years ago with all its umpteen updates having to be reloaded again. :P
My fstab has ntfs as the file system for the win partition. Now I have added a hash to that line to prevent the partition from being mounted in Linux. This is a caution to all those using Debian Etch with an NTFS partition in the pc. Please don't keep the ntfs partition permanently mounted via /etc/fstab. From other problems too, Debian Etch is far from 'Testing' or almost stable. Its *Unstable* .
On 3/5/07, Rony ronbillypop@yahoo.co.uk wrote:
Hello All,
I wanted to try out this month's Chip DVD which showed a blank disk in Etch. It has Kubuntu 6.10. So I rebooted to try out the same dvd in windows. However I missed the boot-loader and it booted back into Debian. While it was in progress, I gave the 3 finder salute and the pc rebooted decently and this time I selected xp. However it would not load beyond the account login part.
I attached a spare hdd and booted into debian and backed up my entire disk for safety. Then using the xp recovery console I gave the command 'chkdsk c: /p' and now I am able to boot into the admin account only and that too slowly. Many features have got disabled. In short, I got to reload windows for the first time ever since I got the system 5 years ago with all its umpteen updates having to be reloaded again. :P
My fstab has ntfs as the file system for the win partition. Now I have added a hash to that line to prevent the partition from being mounted in Linux. This is a caution to all those using Debian Etch with an NTFS partition in the pc. Please don't keep the ntfs partition permanently mounted via /etc/fstab. From other problems too, Debian Etch is far from 'Testing' or almost stable. Its *Unstable* .
doesnt this only apply to ntfs partitions mounted read-write (which is tagged experimental & use at own risk in kernel), mounting as read-only (the default way) doesnt seem spoil things!
Karunakar
On Monday 05 Mar 2007 01:19:10 Rony wrote:
My fstab has ntfs as the file system for the win partition. Now I have added a hash to that line to prevent the partition from being mounted in Linux. This is a caution to all those using Debian Etch with an NTFS partition in the pc. Please don't keep the ntfs partition permanently mounted via /etc/fstab.
Hmmm. http://gentoo-wiki.com/HOWTO_NTFS_write_with_ntfs-3g
Also, Alt+Ctrl+Del during fsck could lead to some rather /interesting/ issues, for example:
http://floyd-n-milan.blogspot.com/2006/08/4294967294.html
From other problems too, Debian Etch is far from 'Testing' or almost stable. Its *Unstable* .
I don't think so.
Sometime on Mon, Mar 05, 2007 at 01:19:10AM +0530, Rony said:
mounted via /etc/fstab. From other problems too, Debian Etch is far from 'Testing' or almost stable. Its *Unstable* .
Well, i dont know why dont i face any of the problems with etch ;)
I've been running etch on office mail server. No issues since past 6 months. As in, _no_ issues till now.
Anurag
On 05-Mar-07, at 1:24 PM, Mrugesh Karnik wrote:
From other problems too, Debian Etch is far from 'Testing' or almost stable. Its *Unstable* .
I don't think so.
i hope this issue gets resolved soon - I have two servers struggling along with sarge and am getting fed-up
On Monday 05 March 2007 01:19, Rony wrote:
Hello All,
This is a caution to all those using Debian Etch with an NTFS partition in the pc. Please don't keep the ntfs partition permanently mounted via /etc/fstab. From other problems too, Debian Etch is far from 'Testing' or almost stable. Its *Unstable* .
Using sarge with 2.6.17-3 and ntfs rw. No problem except when doze does somthing wierd. On the next linux boot the ntfs mount will bomb. fsck the ntfs partition (invariably some cross linked files) and everything will work normally. note linux never did anyhing since the last boot to the ntfs partition. I notice this behavioue very often on systems with one of the commercial AV crap installed. In the most recent case it was brontok something, which mangles the fat (whatever) entries and was "cleaned" by the av program. Doze continues to work across reboots until u boot into linux, then the "unable to mount ntfs" error.
Anurag wrote:
Sometime on Mon, Mar 05, 2007 at 01:19:10AM +0530, Rony said:
mounted via /etc/fstab. From other problems too, Debian Etch is far from 'Testing' or almost stable. Its *Unstable* .
Well, i dont know why dont i face any of the problems with etch ;)
I've been running etch on office mail server. No issues since past 6 months. As in, _no_ issues till now.
You may not be using gui. Command line part in etch is ok but gui is too buggy.
G Karunakar wrote:
doesnt this only apply to ntfs partitions mounted read-write (which is tagged experimental & use at own risk in kernel), mounting as read-only (the default way) doesnt seem spoil things!
hmmm.
jtd wrote:
Using sarge with 2.6.17-3 and ntfs rw. No problem except when doze does somthing wierd. On the next linux boot the ntfs mount will bomb. fsck the ntfs partition (invariably some cross linked files) and everything will work normally. note linux never did anyhing since the last boot to the ntfs partition. I notice this behavioue very often on systems with one of the commercial AV crap installed. In the most recent case it was brontok something, which mangles the fat (whatever) entries and was "cleaned" by the av program. Doze continues to work across reboots until u boot into linux, then the "unable to mount ntfs" error.
It was a linux problem. I interrupted the linux loading sequence with the 3 finger salute and it gave the message that it was rebooting but XP couldn't go further beyond the login screen. Before that I have used XP a few times even after installing etch. I use AVG which is quite stable. The av program in the above case may have cleaned an infected fs. My system is clean as I use it with caution.
I faced a similar problem earlier when I had Freespire installed but was able to recover the NTFS partition just by a few reboots into XP. This time it was a big bang. Anyway I clean-reinstalled the system today. Only updates need to be done now.
On Monday 05 March 2007 19:27, Rony wrote:
jtd wrote:
It was a linux problem. I interrupted the linux loading sequence with the 3 finger salute and it gave the message that it was
linux does not write to the ntfs partition unless it was fscking. Rebooting at any point prior to mounting a file system wont make a difference.
rebooting but XP couldn't go further beyond the login screen. Before that I have used XP a few times even after installing etch. I use AVG which is quite stable. The av program in the above case may have cleaned an infected fs.
The concept of "cleaning" an infected a filesystem ( removing portions of a file rather than the file itself) is stupid at the least. You are presuming that no virus = uncorrupt files and filesystem.
My system is clean as I use it with caution.
I faced a similar problem earlier when I had Freespire installed but was able to recover the NTFS partition just by a few reboots into XP. This time it was a big bang. Anyway I clean-reinstalled the system today. Only updates need to be done now.
On Wednesday 07 March 2007 17:36, Vihan Pandey wrote:
linux does not write to the ntfs partition unless it was fscking.
i think there is limited NTFS write support. i can edit an existing ASCII file on an NTFS partition and save the changes. However i obviously can't copy or move files into the NTFS partition.
In which case linux wont be able to mangle it at all.
-
Anurag -
G Karunakar -
jtd -
Kenneth Gonsalves -
Mrugesh Karnik -
Rony -
Vihan Pandey