| View previous topic :: View next topic |
| Author |
Message |
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
 Posted: Wed Apr 07, 2004 12:57 am Post subject: Strange problem with parted/qtparted... |
 |
|
If I run parted on my first disk it doesn't recognize any of the partitions. It recognizes the entire disk as being a fat16 partition.
| Quote: |
Using /dev/ide/host0/bus0/target0/lun0/disc
Information: The operating system thinks the geometry on
/dev/ide/host0/bus0/target0/lun0/disc is 9964/255/63. Therefore, cylinder 1024
ends at 8032.499M.
(parted) print
Disk geometry for /dev/ide/host0/bus0/target0/lun0/disc: 0.000-78167.250 megabyt es
Disk label type: loop
Minor Start End Filesystem Flags
1 0.000 78167.250 fat16
(parted)
|
But if I run fdisk on it and do a probe it displays the following:
| Quote: |
Disk /dev/hda: 81.9 GB, 81964302336 bytes
255 heads, 63 sectors/track, 9964 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 4783 38419416 7 HPFS/NTFS
/dev/hda3 4784 9964 41616382+ f W95 Ext'd (LBA)
/dev/hda5 4784 7415 21141508+ 7 HPFS/NTFS
/dev/hda6 7416 7424 72261 83 Linux
/dev/hda7 7425 7522 787153+ 82 Linux swap
/dev/hda8 7523 9964 19615333+ 83 Linux
Command (m for help):
|
So what's going on? |
|
| Back to top |
|
 |
Nate_S
Guru
Joined: 18 Mar 2004
Posts: 414
|
| Posted: Fri Apr 09, 2004 10:27 pm Post subject: |
|
|
it looks like parted is converting /dev/hda to /dev/ide/host0/bus0/target0/lun0/disc, and is seeing a loop device. fdisk, it seems is just using the /dev/hda symlink which in your case may not point to the primary master.
are you using raid, lvm, cryptoloop or anything that might make your disk be a loop device?
try running
ls -l /dev | grep hda
and you can see where the symlink points
-Nate |
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Sat Apr 10, 2004 8:49 am Post subject: |
|
|
Nope. And fdisk is actually seeing the correct partitions and everything which are located on the primary master.
And oddly enough, my other disk (/dev/hdb; the slave) is seen perfectly fine. It sees that it's got nothing but an NTFS partition.
Oh well. Not like it matters. |
|
| Back to top |
|
|
PowerFactor
Veteran
Joined: 30 Jan 2003
Posts: 1693
Location: out of it
|
| Posted: Tue Apr 13, 2004 8:27 pm Post subject: |
|
|
It matters to me, for I just discovered I have the same problem. And it's not just with qtparted, partimage and the debian installer partitioning tool both claim that my disk is a single fat12/16 partition. But both fdisk and cfdisk show the correct partition layout which is as follows. | Code: | Disk /dev/hda: 60.0 GB, 60040544256 bytes
255 heads, 63 sectors/track, 7299 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 1044 8385898+ 7 HPFS/NTFS
/dev/hda2 1045 7299 50243287+ f W95 Ext'd (LBA)
/dev/hda5 1045 2088 8385898+ 7 HPFS/NTFS
/dev/hda6 2089 2098 80293+ 83 Linux
/dev/hda7 2099 3142 8385898+ 83 Linux
/dev/hda8 3143 3175 265041 82 Linux swap |
This isn't my gentoo box with the problem though. It's my secondary/windows box. It has redhat9 on it as well. I was going to install debian on it in the free space just for the experience. But I think this partition wierdness needs investigating lest I nuke my windows partitions.(backing them up now anyway) I was using all those tools from Knoppix, except the debian installer of course.
slycordinator: Have you ever had Smart Boot Manager installed on that drive? I have it on this drive and that's the only unusual thing I can think of. All the partitions on this drive were created with linux fdisk. The windows filesystems were simply copied frome another drive with dd. |
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Wed Apr 14, 2004 1:18 am Post subject: |
|
|
Yes I have had Smart Boot Manager now that you speak of it. I'm guessing that's the whole problem.
Sometime I'll try to get rid of the partition it installed to and make sure to reset the mbr.
edit: So yeah I'm not currently using Smart Boot Manager; I used it as part of XOSL. Though I still have the partition I made it install XOSL/SBM to. |
|
| Back to top |
|
|
PowerFactor
Veteran
Joined: 30 Jan 2003
Posts: 1693
Location: out of it
|
| Posted: Wed Apr 14, 2004 1:56 am Post subject: |
|
|
Ah yes, sbm was the culprit. I finally found the mbr backup file sbminst made for me and used that to uninstall sbm. Now qtparted is working correctly.  Now maybe I can get this debian installer to actually work. |
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Wed Apr 14, 2004 5:22 am Post subject: |
|
|
What's strange is that I USED to use smb. I had replaced it with grub. Seems that when grub installs itself to the mbr it doesn't first erase the mbr.
All I did to fix this was boot off a win98 boot floppy and run "fdisk /mbr" which resets the entire mbr. Then when I booted off my old gentoo disk, mounted the disks and chrooted parted worked just fine. And I obviously made sure to reinstall grub. |
|
| Back to top |
|
|
PowerFactor
Veteran
Joined: 30 Jan 2003
Posts: 1693
Location: out of it
|
| Posted: Wed Apr 14, 2004 5:53 pm Post subject: |
|
|
| Glad to hear that "fdisk /mbr" can fix it. I'm not suprised that installing grub over it didn't completely wipe it out. I had gathered from the sbm docs that it installs stuff outside the "normal" mbr and the online uninstall facility doesn't remove it all. So I was afraid that without a mbr backup created by sbminst the only to fix it would be to zero the mbr and partition table with dd. |
|
| Back to top |
|
|
|
Other Things Gentoo
