Bug 231714 - wrong filesystem detected on sata drive
Summary: wrong filesystem detected on sata drive
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: redhat-config-services
Version: 6
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-03-10 16:14 UTC by Henri Ala-Peijari
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-03-10 16:29:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Device manager view of hardware (222.60 KB, image/png)
2007-03-10 16:14 UTC, Henri Ala-Peijari
no flags Details

Description Henri Ala-Peijari 2007-03-10 16:14:27 UTC
Description of problem:
In an installation running from an IDE drive I also have a SATA drive with an
EXT3 partition. Everything works ok when I boot to Fedora Core 5. When I boot to
Fedora Core 6, I am unable to mount the partition and when I use fdisk /dev/sda
I notice that it shows the parition as type NTFS (ID:7). 


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

How reproducible:
Every time. 

Steps to Reproduce:
1.Boot fedora core 6
2.fdisk /dev/sda --> "p" to print filesystem types, shows wrong filesystem
3.Unable to mount partition
  
Actual results:
fdisk shows wrong filesystem type, unable to mount

Expected results:
fdisk should show ext3 partition type ID:83

Additional info:
Harware:

Asus A8N-E motherboard
AMD 64 3000+ processor 939-socket
Seagate 160GB IDE drive ST3160021A
Western Digital 80GB SATA drive
NEC DVD+-rw drive
CD-ROM drive 
1gigabyte memory (2x512)
Original bios (never updated)

Comment 1 Henri Ala-Peijari 2007-03-10 16:14:27 UTC
Created attachment 149777 [details]
Device manager view of hardware

Comment 2 Henri Ala-Peijari 2007-03-10 16:29:43 UTC
My mistake. Filesystem was ntfs, I didn't realise there was support for ntfs in FC5.


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