NotebookForums.com › Forums › General Notebook Discussions › Linux & Other OS's › Feisty ext3 and windows ext2 driver incompatibility
New Posts  All Forums:Forum Nav:

Feisty ext3 and windows ext2 driver incompatibility

post #1 of 7
Thread Starter 
Recently I reformatted my Linux partition and installed KUbuntu Feisty Fawn. The partition was formatted using the KUbuntu live installer. I also have a Windows ext2 driver which gave read and write access when I was using Edgy.

Now, I get an error in Windows - says the drive is 'not formatted'.

Did ext3 fs change in some way with Feisty?
post #2 of 7
Thread Starter 
(notices attachments are disabled here. Was going to post a screenshot)
post #3 of 7
Thread Starter 
Using the mountdiag.exe for windows, which can be found here

Chris@brigindona /cygdrive/d/travel-downloads/Ext2 IFS
$ ./mountdiag.exe U:

The volume has an Ext2/Ext3 file system, but the Ext2 IFS 1.10 software
did not mount it because there is at least one incompat feature flag set.
The Ext2 IFS software does not implement:
* needs_recovery *
Here we have an Ext3 file system which has transactions left in its journal. A
pure Ext2 driver must not access such a volume which is in that state (to
prevent data loss!).
You may solve it by mounting it on Linux (which has a kernel with Ext3
support). Be sure that you cleanly dismount it, before you shutdown Linux.
After that the Ext2 IFS software should be able to access the volume.


Reboots into Linux to see if that fixes it.
post #4 of 7
Thread Starter 
Booting Ubuntu there is no fsck. mount says everything is fine:

Code:
chris@Thirona:~$ mount
/dev/sda4 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
lrm on /lib/modules/2.6.20-12-generic/volatile type tmpfs (rw)
/dev/sda5 on /media/data type ntfs (rw,nls=utf8,umask=007,gid=46)
/dev/sda1 on /media/delldiag type vfat (rw,utf8,umask=007,gid=46)
/dev/sda2 on /windows type ntfs (rw,nls=utf8,umask=007,gid=46)

Apparently fsck is not a good idea if already mounted:

Code:
chris@Thirona:~$ sudo fsck /dev/sda4
Password:
fsck 1.40-WIP (14-Nov-2006)
e2fsck 1.40-WIP (14-Nov-2006)
/dev/sda4 is mounted.

WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? no

check aborted.

and apparently I don't have unmount. sudo touch /forcefsck did not do anything either.

But, now I reboot into Windows and it can see the drive. Most odd. It can also see the external USB drive which I reformatted to ext3.

Well, sorry to ramble on. I was trying to document the problem and solution, but it seems to have auto-healed.
post #5 of 7
It seems like it was not cleanly unmounted one time, which is what you ran into.

The drivers on linux probably detected this on the mount and cleaned up the problems.

For the record, you DO have umount but it has to be run as root in general by default on most systems. Also note that it is umount, not unmount.

And as you already gathered, running fsck manually on the drive is not a bad idea after an error like that.

Seablade
post #6 of 7
Thread Starter 
Quote:
Originally Posted by seablade
It seems like it was not cleanly unmounted one time, which is what you ran into.

The drivers on linux probably detected this on the mount and cleaned up the problems.
Okay. Although I would have expected to see 'fsck forced' or somesuch on the console during boot, in that case. Or perhaps it just replays the journal and fixes things silently?

Quote:
Originally Posted by seablade
For the record, you DO have umount but it has to be run as root in general by default on most systems. Also note that it is umount, not unmount.

That would explain why 'which unmount' said it wasn't there
/me learns to read
post #7 of 7
Quote:
Okay. Although I would have expected to see 'fsck forced' or somesuch on the console during boot, in that case. Or perhaps it just replays the journal and fixes things silently?
I don't have enough knowledge in FS practices to be able to answer this one effectively myself. As I said, I would run a fsck myself, apparently they disagree and might have a good reason Seablade
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Linux & Other OS's
NotebookForums.com › Forums › General Notebook Discussions › Linux & Other OS's › Feisty ext3 and windows ext2 driver incompatibility