--- Begin Message ---
- To: "François P. Rotzinger" <Am843@gmx.ch>
- Subject: Re: Bug#790724: 790724 - additional information
- From: "Theodore Ts'o" <tytso@mit.edu>
- Date: Fri, 3 Jul 2015 15:20:38 -0400
- Message-id: <20150703192038.GL9456@thunk.org>
- In-reply-to: <5596DA28.4060800@gmx.ch>
- References: <559679E1.7000301@gmx.ch> <20150703164358.GF9456@thunk.org> <5596C92F.10503@gmx.ch> <20150703183246.GI9456@thunk.org> <5596DA28.4060800@gmx.ch>
On Fri, Jul 03, 2015 at 08:53:28PM +0200, "François P. Rotzinger" wrote:
> I have run mkfs.ext2 manually, and the message displayed on the screen was
> that the partition was formatted (there was no error message). That's why I
> rebooted, reinstalled, and did not format this partition (again). This way,
> the installation succeeded. This server is in Lausanne and shut down for the
> moment; I shall turn it on next Monday. Will the information still be in
> /var/log/kern.log,or more likely in /var/log/kern.log.1? I shall send you
> then the desired file.
I wonder if the issue is how the installer kernel is configured, or
the version of the installer kernel.
Unfortunately, what we need is the dmesg output from the failed
installer run, which won't be in /var/log/* of the installed system,
alas.
Is there any chance you can try redoing the reformat during the
install process, and when the system hangs, change to a different
virtual console, and then grabbing the dmesg output and then putting
it some place where it will survive the reboot into the freshly
installed system?
Thanks,
- Ted
--- End Message ---