Followup-For: Bug #123926
Package: boot-floppies
Version: 3.0.18
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux Voyager 2.4.16-02 #1 Mon Dec 17 00:37:44 PST 2001 i586
Locale: LANG=C, LC_CTYPE=C
The purpose of this bug report is to supplement the existing report by
someone else who had trouble with some sort of Windows partitions when using
the 3.0.17 boot-floppies. Here I report a similar problem but with a
partition on a ReiserFS when using the 3.0.18 boot-floppies.
I took an existing swap partition on /dev/hdc4 out of service from a working
Debian system, ran fdisk to change the file type to 83 Linux Native, ran
'mkreiserfs /dev/hdc4' to create a ReiserFS on it, and copied basedebs.tgz
from an existing ext2 partition, obtained from Jaqque earlier, in order to
prepare for installing using the 3.0.18 boot floppies.
I booted the system using the 3.0.18 rescue disk, and used the root disk
when directed. I ran through the installation noting only minor problems
until the step "Install the Base System".
I chose the option "harddisk: partition on the hard disk".
I selected "/dev/hdc4: Linus native", and pressed ENTER.
The result was "Mount Failed
The partition wa not mounted sucessfully. <continue>".
I verified with the View Partition Table option that this partition was NOT
already mounted, just in case.
In response to comments made earlier by Eduard Bloch, who said, in part:
"Which filesystem? Why did you not attach the log files? Your report does
not contain much helpful data.",
please note that the present report specifies that I used the ReiserFS.
I did not attach the log files since there appears to be a bug with that as
well, which I will report separately to give it specific tracking. But for
the sake of completeness, here is what I did.
I selected "Report a Problem".
"Select Report Medium: Mounted: Already mounted filesystem",
and then typed the / character , which should have been the root filesystem,
but I suspect it was not.
Anyhow, the installer reported apparent success with "Problem report saved
to /instmnt//dbg_log.tgz". Please note the double slashes. This
double-slash notation is unfamiliar to me. If the double slashes are not a
bug, then please tell me where I can read more about it.
At this point, I unmounted the partition /dev/hda10 which nominally
contained the new root filesystem, and then used the installer reboot
option to reboot the system, this time back into my regular Debian system.
Checking /dev/hda10 I found no evidence of a problem report there under the
name "dbg_log.tgz".
I hope this information is helpful to you.
John
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
