System hang when creating file system during install

I started the installer with maximum debug output and was able to switch to console 4 before the hang occurs.

However, I cannot see anything strange going on here:

--> PROGRESS SET 15
<-- 0 OK
--> SUBST partman-basicfilesystems/progress_formatting_mountable STATE writing per-group metadata.

That's the last thing that gets printed out before the total freeze.

Does this still happen with beta 2? If so, please get a trace:

https://wiki.ubuntu.com/DebuggingSystemCrash

Until this gets confirmed in dapper, I'm leaving it on breezy's kernels source. Please retest against latest dapper (Currently Flight 7).

It still happens on my system too (Dell Latitude X300, 40GB of HD). Was the same on beta 6.

I found out that if you delete the file

   /lib/partitioner/commit.d/32update-dev

the system do not hang up anymore and the installation complete.

That would mean it's udevplug that's hanging.

I forgot to say that for me it happens ONLY on Dapper. Confirmed also with latest beta 7.

This is not a duplicate of bug 37970. That bug describes a user-level crash in the partitioning tool, not a kernel crash.

The problem I experienced was due to an error in the BIOS.
An update from ASUS corrected the problem.

Alessio Signorini skrev:
> I forgot to say that for me it happens ONLY on Dapper. Confirmed also
> with latest beta 7.
>
> ** This bug has been marked a duplicate of bug 37970
> partitioner loops without committing changes
>

I cannot proceed with Dapper (final) installation when I am in the partitioner for my SATA harddisk in my Asus.
I have tried 2 harddisks and both will not go pass a few Megs when creating the filesystem.

I get the lost page IO error.

I tried it a few times:
- small pations are seeming to work.
- from partiotioner as in rescue mode from console creating INodes fail after some time (lets say 13% of 200 Gb)

1st attempt HDisk: Maxtor 200Gb S-ATA
2nd attempt HDisk: Samsung 250Gb S-ATA

Hopefully you can help me with this. I cannot get it working.

Magnus what is the asus Bios update you used?
My Mainboard: P4P8T-SP-ASUS-1007

is a barebone pc

Please forgive me for hijacking this bug, but clicking on the link to "Report a bug in debian-installer" which I was told in another page is where I should report my bug goes to a page telling me that d-i does not user Malone. https://launchpad.net/products/debian-installer/+filebug goes on that I should use the official bug tracker but does not mention where it is. So basically, this comes across as a "F*ck off and don't bother us" message.

Please add d-i to Malone so ppl can report bugs. How did the three bugs that are in the tracker now ever get reported?

Anyways, on to my problem. It is some failure in parted which I reported in bug 59620. D-i's part in it is that said bug should not be able to bring the installation process to a complete halt at least in my case where all partitions are already laid out.

Moving from the debian-installer upstream product (which indeed does not use Launchpad for bug tracking) to the debian-installer source package in Ubuntu.

This bug has had no activity for a considerable period. This is a check to see if there is still interest in investigating this bug report.

Wherever this bug is, it isn't in debian-installer-utils ...

Moving to the linux source package, where kernel bugs are being collected from here on in.

Rolf, your problem is different from the one described here. You're describing a user-level hang in the installer, whereas this bug is about a kernel-level hang. Conflating them into the same bug is likely only to cause confusion.

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!