fdisk show FAT16 in a ext3 partition

Bug #329509 reported by Antonio Orvay
8
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

hi, I'm trying to install Kubunto 8.10 in a fakeRAID. I folow the fakeRaidHowTo but it didn't work.
fdisk -l shows the second partition formatted during installation as ext3 like FAT16.

In the GRUB, the order >root (hd0,1) results unknown format.

I think it has a correspondancy between the two problems.

please help.

Revision history for this message
whtvr (whtvr) wrote :

how do you know it didn't work? did you get an error while following the howto?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in ubuntu:
status: Incomplete → Invalid
Revision history for this message
James_o (xme-and-sonic) wrote :

I am having this same problem, and it is very frustrating because grub cannot boot either linux or windows.

For me, this started when I was trying to change my external hard drive (which has linux on it) to be able to boot on any computer.

I tried it on my desktop computer, and it booted successfully--once. After that, I always had this problem.

A few days later I noticed that my SuperGrubDisk flash drive partition started having the same problem--after using it in the same desktop computer.

I think that it's a drive access problem that may be solvable with the help of this link
http://ubuntuforums.org/showthread.php?t=442945
...but I was never able to make it work.

Any help is appreciated.

Changed in ubuntu:
status: Invalid → New
shankao (shankao)
affects: ubuntu → ubiquity (Ubuntu)
tags: added: derivatives intrepid
Revision history for this message
Phillip Susi (psusi) wrote :

James, can you describe what you did leading up to this, and post the output of fdisk -l showing the partition is fat?

Shankao, why did you assign this to ubiquity?

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
shankao (shankao) wrote :

Hi, I don't really recall the reason but could be something related to the bug appearing during ubuntu install. I agree that the change could have being too premature, my fault.

Anyway, I don't like to leave the package filled against the generic "ubuntu" and prefer to triage it correctly instead. If the problem is the format during installation, the page in https://wiki.ubuntu.com/Bugs/FindRightPackage suggests filling it agains ubiquity or maybe better debian-installer as this case has being probably done with the alternate image. Any other package suggestions?

Revision history for this message
Phillip Susi (psusi) wrote :

To be honest it sounds like this is not a bug at all to me. It sounds like the OP was following the fakeraid howto so he probably created the partition himself with fdisk and left the partition tag as fat instead of Linux. This doesn't really matter at all other than looking odd.

Revision history for this message
James_o (xme-and-sonic) wrote :

Hey, thanks for responding! Sorry for the few-days-delay.
I've actually reformatted the hard drive since then. I could try to recreate the problem, it's just
1) boot from the disk
2) reboot

and it will no longer boot.

What's an "OP"? Original Post, I suppose. Anyway, the problem it created for me was that grub no longer recognized the partition. Can you give me some advice for if it happens again? If not, I'll try to recreate the problem, but I might not get around to it till summer ( it scares me to try again =-X and I feel guilty trying to create a problem when I have enough *embarrassed*)

Thanks again. If you don't have time to dwell on troubleshooting, don't worry. It's not causing me any more problems.

Revision history for this message
Phillip Susi (psusi) wrote :

Yes, OP means the Original Poster. I can't really understand his original description, but then you mention you have the same issue. If so ( and you still care ), please try to reproduce it and describe exactly:

1) What you did
2) What happened as a result
3) What you expected to happen

If you have managed to move on and can not or do not care to reproduce it and describe it better, then I can just close this report.

Revision history for this message
James_o (xme-and-sonic) wrote :

Ok, you can close it; thanks!

P.S.: before you close, can you respond to this question?
If i have this problem again (a few months from now)... Can I just create a new thread? =D

Revision history for this message
Phillip Susi (psusi) wrote :

That would probably be best.

Changed in ubiquity (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.