Fedora Linux Support Community & Resources Center
  #1  
Old 13th September 2006, 02:29 PM
gary4gar Offline
Registered User
 
Join Date: Sep 2006
Posts: 14
Unhappy error Installing fc5:partion table unreadable

hi people,
my first post at this forums & many more to come
when i tried to install fc5. the anaconda installer said that my partions are unreadable & asked if i should erase whole hdd.
here is my outpu of "fdisk -l"
Code:
root@ubuntu:~# fdisk -l
omitting empty partition (5)

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        9729    78148161    f  W95 Ext'd (LBA)
/dev/sda2   *        2433        6080    29302528+   b  W95 FAT32
/dev/sda5               1        1337    10739358    7  HPFS/NTFS
/dev/sda6   *        1338        2383     8401963+  83  Linux
/dev/sda7            2384        2432      393561   82  Linux swap / Solaris
/dev/sda8            6081        9729    29310561    b  W95 FAT32
i have a single 80gb sata hdd,msi-k8mm-v,amd athlon 64 3000+,256 ram(64mb for shared gfx).first i was using ubuntu 5.10 then tried 6.06. 5.10 worked great for me but 6.06 gave the same error like this one. so i suspect there is some thing wrong with the new sata drivers from via(via-kbmm-v chipset).so i dicided to do some R&D with it. tried installing windows xp with sp2 which has the sata drivers inbuilt.it too failed.now downlaod latest drivers(ver 5.30c) from via's site still noting. so tried installing older version drivers(Ver - 4.20a) and worked

so i want any way that i can use older version of drivers.also from where should i get those drivers b'cos at via site only gfx drivers are available for fc5.i used ask method for installing

regards,
gary
Reply With Quote
  #2  
Old 13th September 2006, 02:47 PM
markjensen's Avatar
markjensen Offline
Registered User
 
Join Date: Feb 2004
Location: Middle Tennessee
Age: 46
Posts: 390
Well, I don't see any problem there. Unless, for whatever reason, the extended partition stuff is causing your grief.

You have only one primary partition, sda1. It is a container (holds extended partitions) for all of your real 'filesystem' partitions. Organized by start location:
Code:
sda1         1    9729    95 ext
sda5         1    1337    ntfs
sda6    1338    2383    ext3
sda7    2384    2432    swap
sda2    2433    6080    fat32
sda8    6081    9729    fat32
I have never set up a system this way, as I use up my primaries before starting extended partitions. Maybe this is causing your problem? Someone else with more experience in various partitioning layouts will be able to better answer your question.

My main look was to make sure you didn't overlap partitions, or have any extendeds going beyond the limits set with your sda1 partition. You don't have any errors in the layout that I can see (other than the possibility of requiring a primary partition).


EDIT: Did you edit your post and add in that additional information while I was typing? You want to see if you can use older (working) drivers now?
__________________
Semi-Recent screenshot: here
Fluxbox user certified with a Linux Genuine Advantage provided by the GNU GPL
Reply With Quote
  #3  
Old 13th September 2006, 04:38 PM
gary4gar Offline
Registered User
 
Join Date: Sep 2006
Posts: 14
^^^
yes i always save long posts b'cos i don't have a ups!
how to use older drivers??
Reply With Quote
  #4  
Old 13th September 2006, 04:42 PM
gary4gar Offline
Registered User
 
Join Date: Sep 2006
Posts: 14
i set out only four partions i don't know from where this sda1 came from
Reply With Quote
  #5  
Old 13th September 2006, 06:00 PM
markjensen's Avatar
markjensen Offline
Registered User
 
Join Date: Feb 2004
Location: Middle Tennessee
Age: 46
Posts: 390
Well, you have more than four. And, like I stated earlier, using extendeds right off the bat isn't what I normally do. It should be OK, but I don't have any personal experience in that.

sda1 has to exist. It is your holder for your filesystems. I guess a bit of explanation is in order:
A hard drive has four partitions. That's it. Linux calls them hda1 through hda4 (or sda). That is all the room that the partition table is set up for (I don't know the technical details, but it is a BIOS thing, I think). There was/is a need for more than just four, so the ability to "extend" was added. You set a special attribute to your partition, and it allows the first section for that "real" partition to be another virtual partition table, allowing four more partitions.

Your setup does this. Partition #1 in the table is set to extended, and the extended table points to four additional partitions, sda5, 6, 7 & 8. You also have a partition #2 defined. This is another primary partition.

Looking at your configuration again. I see that your #2 is in the middle of the large "extended" sda1 space. There is no overlap with other partitions, but maybe this is causing the problem you see?

I'm sorry, but I really don't know how the system should handle this. It seems OK to me, and that is why I am suggesting hanging tight until someone with this exact expertise comes along.

If you have another (blank) hard drive, you can try setting up similar systems with different partitioning layouts.
__________________
Semi-Recent screenshot: here
Fluxbox user certified with a Linux Genuine Advantage provided by the GNU GPL
Reply With Quote
  #6  
Old 13th September 2006, 07:45 PM
gary4gar Offline
Registered User
 
Join Date: Sep 2006
Posts: 14
well i will try installing orlder version of drivers. pls tell me how to do it??
if not done i will erase my hdd
Reply With Quote
  #7  
Old 15th September 2006, 09:45 AM
gary4gar Offline
Registered User
 
Join Date: Sep 2006
Posts: 14
*bumo*
well someone pls help
Reply With Quote
  #8  
Old 18th September 2006, 09:44 AM
gary4gar Offline
Registered User
 
Join Date: Sep 2006
Posts: 14
here is a report from partion magic

Quote:
Symantec PartitionInfo 8.0 -- Windows NT/2000 Version
Date Generated: 09/18/06 14:05:41
Copyright (c)1994-2004, Symantec Corporation
Permission is granted for this utility to be freely copied so long
as it is not modified in any way. All other rights are reserved.

Symantec, makers of Norton PartitionMagic(r), Drive Image(tm), and DriveCopy(tm), can be reached at:
Voice: 801-437-8900
Fax: 801-226-8941
Web site: http://www.symantec.com/techsupp/

General System Information:
Total Physical Memory (bytes): 200,785,920
Used Physical Memory: (bytes): 184,545,280
Maximum Page File Size: (bytes): 487,329,792
Current Page File Size: (bytes): 203,612,160



================================================== ================================================== =======
Disk Geometry Information for Disk 1: 9729 Cylinders, 255 Heads, 63 Sectors/Track
System PartSect # Boot BCyl Head Sect FS ECyl Head Sect StartSect NumSects
================================================== ================================================== =======
0 0 00 0 1 1 0F 1023 0 63 63 39,070,080
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 0 00 0 1 1 0F 2432 0 63 63 39070080
Info: Partition didn't end on cylinder boundary.
ucEndHead expected to be 254, not 0.
DISK1_VOL2 0 1 80 1023 1 1 0B 1023 254 63 39,070,143 58,605,057
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 1 80 2432 1 1 0B 6079 254 63 39070143 58605057
63 1 00 0 1 2 05 1023 254 63 64 21,478,841
Info: End C,H,S values were large drive placeholders.
Actual values are:
63 1 00 0 1 2 05 1336 254 63 64 21478841
Info: Partition didn't begin on head boundary.
ucBeginSector expected to be 1, not 2.
64 0 00 0 3 1 07 1023 254 63 189 21,478,716
Info: End C,H,S values were large drive placeholders.
Actual values are:
64 0 00 0 3 1 07 1336 254 63 189 21478716
Error #105: Partition didn't begin on head boundary.
ucBeginHead expected to be 0 or 1, not 3.
64 1 00 1023 0 1 05 1023 254 63 21,478,905 16,803,990
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
64 1 00 1337 0 1 05 2382 254 63 21478905 16803990
21,478,905 0 80 1023 1 1 83 1023 254 63 21,478,968 16,803,927
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
21478905 0 80 1337 1 1 83 2382 254 63 21478968 16803927
21,478,905 1 00 1023 0 1 05 1023 254 63 38,282,895 787,185
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
21478905 1 00 2383 0 1 05 2431 254 63 38282895 787185
SWAPSPACE2 38,282,895 0 00 1023 1 1 82 1023 254 63 38,282,958 787,122
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
38282895 0 00 2383 1 1 82 2431 254 63 38282958 787122
38,282,895 1 00 1023 0 1 05 1023 254 63 97,675,200 58,621,185
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
38282895 1 00 6080 0 1 05 9728 254 63 97675200 58621185
DISK1_VOL3 97,675,200 0 00 1023 1 1 0B 1023 254 63 97,675,263 58,621,122
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
97675200 0 00 6080 1 1 0B 9728 254 63 97675263 58621122



================================================== ================================================== =======
Partition Information for Disk 1: 76,316.6 Megabytes
Volume PartType Status Size MB PartSect # StartSect TotalSects
================================================== ================================================== =======
ExtendedX Pri 19,077.2 0 0 63 39,070,080
EPBR Log 0.0 None -- 63 63
EPBR Log 10,487.7 63 1 64 21,478,841
Warning #113: EPBR partition starting at 64 overlaps previous EPBR partition.
D: NTFS Log 10,487.7 64 0 189 21,478,716
Error #114: Logical starting at 189 is not one head away from EPBR.
EPBR Log 8,205.1 64 1 21,478,905 16,803,990
Linux Ext3 Log,Boot 8,205.0 21,478,905 0 21,478,968 16,803,927
EPBR Log 384.4 21,478,905 1 38,282,895 787,185
*:SWAPSPACE2 Linux Swap Log 384.3 38,282,895 0 38,282,958 787,122
CISK1_VOL2 FAT32 Pri,Boot 28,615.8 0 1 39,070,143 58,605,057
EPBR Log 28,623.6 38,282,895 1 97,675,200 58,621,185
Warning #113: EPBR partition starting at 97675200 overlaps extended partition.
Unallocated Pri 28,623.6 None -- 97,675,200 58,621,185
EISK1_VOL3 FAT32 Log 28,623.6 97,675,200 0 97,675,263 58,621,122
Error #113: Logical starting at 97675263 overlaps extended partition.


================================================== ================================================== =======
Boot Record for drive D: (Drive: 1, Starting sector: 189, Type: NTFS)
================================================== ================================================== =======
1. Jump: EB 52 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 125 (0x7D)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 21478715
17. MFT Start Cluster: 786432
18. MFT Mirror Start Clust: 1342419
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0xB894F76294F72214
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

================================================== ================================================== =======
Boot Record for drive *: (Drive: 1, Starting sector: 21,478,968, Type: Ext3)
================================================== ================================================== =======
Ext3 file system super block:
1. Inodes count: 1050400
2. Blocks count: 2100490
3. Reserved blocks count: 105024
4. Free blocks count: 973591
5. First data block: 0
6. Logical block size: 2
7. Logical fragment size: 2
8. Blocks/group: 32768
9. Fragments/group: 32768
10. Inodes/group: 16160
11. Mount time: 0x45073281
12. Last write time: 0x450735A5
13. Mount count: 22
14. Max. mount count: 30
15. Magic number: EF53
16. State: 0x0001
17. Error behavior: 0x0001
18. Minor revision level: 0
19. Last check time: 0x44F82F8E
20. Max. time bet. checks: 0
21. Creator oper. system: 0
22. Major revision level: 1
23. Reserved block def. UID:0x0000
24. Reserved block def. GID:0x0000

================================================== ================================================== =======
Boot Record for drive C: (Drive: 1, Starting sector: 39,070,143, Type: FAT32)
================================================== ================================================== =======
1. Jump: EB 58 90
2. OEM Name: MSWIN4.1
3. Bytes per Sector: 512
4. Sectors per Cluster: 32
5. Reserved Sectors: 32
6. Number of FAT's: 2
7. Reserved: 0x0000
8. Reserved: 0x0000
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 39070143 (0x25429BF)
14. Big Total Sectors: 58605057 (0x37E3E01)
15. Big Sectors per FAT: 14301
16. Extended Flags: 0x0000
17. FS Version: 0
18. First Cluster of Root: 2 (0x2)
19. FS Info Sector: 0
20. Backup Boot Sector: 0
21. Reserved: 000000000000000000000000
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 0x29
25. Serial Number: 0x708F5A22
26. Volume Name: DISK1_VOL2
27. File System Type: FAT32
28. Boot Signature: 0xAA55

Last edited by gary4gar; 18th September 2006 at 09:46 AM.
Reply With Quote
  #9  
Old 18th September 2006, 09:47 AM
gary4gar Offline
Registered User
 
Join Date: Sep 2006
Posts: 14
Part-2 count....
Quote:
============================
Boot Record for drive E: (Drive: 1, Starting sector: 97,675,263, Type: FAT32)
================================================== ================================================== =======
1. Jump: EB FE 90
2. OEM Name: MSWIN4.1
3. Bytes per Sector: 512
4. Sectors per Cluster: 32
5. Reserved Sectors: 32
6. Number of FAT's: 2
7. Reserved: 0x0000
8. Reserved: 0x0000
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 97675263 (0x5D267FF)
14. Big Total Sectors: 58621122 (0x37E7CC2)
15. Big Sectors per FAT: 14305
16. Extended Flags: 0x0000
17. FS Version: 0
18. First Cluster of Root: 2 (0x2)
19. FS Info Sector: 0
20. Backup Boot Sector: 0
21. Reserved: 000000000000000000000000
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 0x29
25. Serial Number: 0x740DD728
26. Volume Name: DISK1_VOL3
27. File System Type: FAT32
28. Boot Signature: 0xAA55
Reply With Quote
Reply

Tags
error, fc5partion, installing, table, unreadable

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Partition table on device sda was unreadable dbet Installation and Live Media 1 10th July 2008 02:25 AM
F7 Installation: The partition table on device sda was unreadable. Zeppe|in Installation and Live Media 14 18th May 2008 08:27 AM
The partition table on device sdb was unreadable - Again nigel_b Installation and Live Media 0 30th January 2008 07:19 PM
Partition table unreadable johnfw Installation and Live Media 1 29th July 2005 06:07 PM
Invalid Partion Table AndreDekolta Using Fedora 13 12th June 2004 04:43 AM


Current GMT-time: 21:11 (Friday, 24-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat