Bug 495933 - Resizing NTFS makes Installtion fail
Summary: Resizing NTFS makes Installtion fail
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-15 15:46 UTC by Thomas Ahle
Modified: 2009-04-16 13:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-16 13:39:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Error file which the dialog proposed to save (142.40 KB, text/plain)
2009-04-15 15:47 UTC, Thomas Ahle
no flags Details

Description Thomas Ahle 2009-04-15 15:46:17 UTC
Description of problem:

Anaconda starts resizing the only partition, which is in ntfs, but then brings up a dialog with installation falled and offers to save the attached filed.

Version-Release number of selected component (if applicable):

Fedora 11 Snap 1

How reproducible:

Every time

Steps to Reproduce:
1. Have a partition with ntfs
2. Ask anakonda to resize it (32000 to 24000MB)
  
Actual results:

"Installation failed" dialog

Expected results:

Resize and continue installation

Comment 1 Thomas Ahle 2009-04-15 15:47:36 UTC
Created attachment 339700 [details]
Error file which the dialog proposed to save

Comment 2 Chris Lumens 2009-04-16 13:39:30 UTC
Here's the real problem:

ERROR(95): Opening '/dev/sda2' as NTFS failed: Operationen er ikke understøttet
The NTFS journal file is unclean. Please shutdown Windows properly before
using this software! Note, if you have run chkdsk previously then boot
Windows again which will automatically initialize the journal correctly.

The next build of anaconda will not traceback here, so you'll be able to do whatever is required in Windows and then retry resizing without getting the annoying traceback dialog.


Note You need to log in before you can comment on or make changes to this bug.