--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Success: Etch, DVD binary1.iso, 10-Nov-2006, 'expertgui' method, (possible rescuegui bug)
- From: Willie Wonka <floydstestemail@yahoo.com>
- Date: Mon, 13 Nov 2006 13:32:55 -0800 (PST)
- Message-id: <20061113213255.11799.qmail@web62410.mail.re1.yahoo.com>
Subject: Success: Etch, DVD binary1.iso, 10-Nov-2006, 'expertgui' method
Package: installation-reports
Version: 2.23
Severity: normal
*** Please type your report below this line ***
-- Package-specific info:
http://ftp.acc.umu.se/cdimage/weekly-builds/i386/iso-dvd/debian-testing-i386-binary-2.iso
(debian-testing-i386-binary-1.iso 10-Nov-2006 13:57 4.4G)
*****************************
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked: [O]
Configure network HW: [O]
Config network: [O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O] --> SLIGHT CAVEAT .. details below
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [O]
Reboot: [O]
*******************************
Hello;
Just to report a successful install using the DVD binary1.iso. However some
possible issues with "rescuegui" (perhaps severe) , and "partman" (minor
annoyances, but confusing). Maybe even Grub .. but that's not for sure.
Naturally, I ran an md5sum on the d/l DVD iso image(s) "prior" to burning them,
and all checked out. I used this command to burn;
~$ growisofs -dvd-compat -Z /dev/hdd=/mnt/p3/debian-testing-i386-binary-1.iso
..where '/dvd/hdd=' is the actual IDE/ATAPI DVD-RW Drive location,
and '/mnt/p3' is where the .iso is (was) located.
***************************
Here's what my system partitions and HDD setup "used" to look like;
http://pastebin.ca/247185 (fdisk -l and orig /etc/fstab on hdc) .. also
~$ df -Tl
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/hdc1 ext3 8364900 4826280 3113704 61% /
tmpfs tmpfs 161036 0 161036 0% /dev/shm
tmpfs tmpfs 10240 120 10120 2% /dev
/dev/hda3 reiserfs 19534436 1765148 17769288 10% /mnt/p3
**hda = 80GB ATA/IDE HDD
*hdb = lite-on cdrw drive
**hdc = 9.1GB ATA/IDE HDD
*hdd = nec dvdrw drive (ND-3550A)
System specs;
Intel Pentium II 350Mhz/100FSB
320MB SDRAM (PC100/133)
Intel 440BX 82443/82371(AB/EB) Chipset
Mobo gateway taborII w/onboard AudioPCI64 (Ensoniq)
***********
***********
Ok .. so Booted up DVD .. and entered 'expertgui' at the boot: prompt
I chose the Tasksel ("Desktop" and "Standard System") boxes, which were already
ticked when I got there. I had to Erase and reformat a 20GB old ext2
partition(hda3), which I previously used as a scratch area for cd burning.
After going through the language/keyboard/time/date settings; I had chosen "no"
at the UTC choice. I also let ALL the IDE modules load, for fear of missing one
necessary .. even though I know the generic linux IDE would do for my system. I
selected some crypt, loopAES, ppp, and USB modules, though no RAID, nor LVM
modules, IIRC.
*************
Onto partman;
*************
I chose ReiserFS (for the heck of it), note; no other partitions on either HDDs
(hda and hdc) have any reiserfs partitions).
But .. I had to proceed through the Erase procedure twice(10-15min each time);
since after the 1st time erasing, I was thrown right back to the orig screen
(Partman) .. and it appeared nothing had changed. (human error?, maybe could be
a better interface?, a status update perhaps?).
After 2nd time erasing the same partition(hda3), I double-clicked on same
partition (status had said "do not use"); where I was then given the
prompt/list of FS type choices. Double-clicked (on each) to alter whatever
options were remaining; mount point, bootable flag, etc .. and set
accordingly. BTW, I didn't set it as 'bootable' (no need using linux).
I chose to install the entire shebang ( /, /boot, /home, /usr, etc) to that one
partition (hda3), if that wasn't clear yet...and altered the FS from ext2 to
reiserfs for the installation. Size of partition remains the same --> 20GiB
*************
Onto Grub;
*************
Ok .. got to the Grub installation choices; MBR or Bootsector only .. I chose
bootsector only(originally). Why? .. here's the deal; I already have a fully
functional Debian Installation on this system, (Sarge upgraded to Sid on
2.6.16), as well as a win98 working installation ..and even though Sid is on
/dev/hdc1 (hdc5 is swap), Grub is already my bootloader.. which appears to be
installed to hda MBR, not hdc (please see the pastbin above). Somehow, my
system boots into either Debian Sid(hdc) or win98(hda) .. no prob.
So i thought I'd just install Grub to hda3 (new Etch installation partition)..
but when I tried there was an error from Grub. I entered exactly this -->
(hd0,2) in the dialog as for where Grub should be installed. IIRC, the error
had to do with not being able to "could not install to (hd0,2) please try to
install to MBR instead" .. I should've taken a "screenshot" at the point .. but
I was worried about ending up with a totally useless system then.
I installed grub to the MBR (hda) .. and continued on with install .. then
waited as all was loaded and configured. Kernel choice was 2.6.17-2-686.
Rebooted after ejecting (btw.. I loaded that module too earlier) and Grub
appeared perfectly .. except it had moved all my prior Debian Kernel Titles (6
total (3diff Kerenls + 3 Single modes)) out of the Automagic Kernel area .. and
placed them into that other OS section beneath :-). No biggy. Besides, I was
now viewing my newer Grub menu.lst found on /dev/hda3 .. the original one on
/dev/hdc1 (Sid) is still exactly how I left it.
I immediately chose an Older kernel (2.6.16) to boot into, as I wanted to
return to IRC quickly and report my findings. Did that, and then started
messing with both copies of /boot/grub/menu.lst and /etc/fstab .. as well as my
/mnt Dirs. There's 2 separate Debian installations now (orig Sid (hdc1) + new
Etch (hda3)) and each has their own files as noted above.
*********************
Possible issues with "rescuegui"?;
Needless to say I made a few configuration errors that caused quite a few
"*failure" (red) messages on boot console scroll/screen, when trying to boot
into 2.6.17 for the 1st time. I managed to recover(bad /etc/fstab entries (ext2
instead of reiser) and /mnt point entries. BUT .. when initially trying to
recover, I first booted the installer and chose "rescuegui" .. which once I got
to the select the / partition .. got hooked into an incessant loop that just
hung, no matter which partition I chose, nor which shell I launched, nor from
hda,hdc, or installer. Luckily the "continue" button stayed active and threw me
back into forth into a console (with errors), and immediately returned to GUI
mode, at the same choose mount for '/' screen again. So I kept trying different
options .. nothing doing.
****************
Ok . that's it for now .. hope I haven't confused, nor chewed your ear off for
too long. GREAT job! with the installer .. Never seen the GUI until now ..
Looks great. Thanks for your work team.
enouf
(iforone to some)
ps. a little pleasure in seeing I don't need to use 'acpi=force' as a kernel
parameter anymore, using the 2.6.17-2-686 kernel. I use that parameter with the
2.6.16-2-686 and earlier kernels (2.6.8-2-386, 2.6.8-3-686).
*****************
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
installation-report depends on no packages.
Versions of packages installation-report recommends:
ii pciutils 1:2.1.11-15 Linux PCI Utilities
ii reportbug 3.21.2 reports bugs in the Debian distrib
-- no debconf information
____________________________________________________________________________________
Sponsored Link
Mortgage rates near 39yr lows. $420k for $1,399/mo.
Calculate new payment!
http://www.LowerMyBills.com/lre
--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
Installer.
- indications in the installation report give the feeling that
the reported problem waslying in another software, unrelated to
D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful
The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet.
In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.
You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.
If some problems are found, please report them with a new bug sent
against installation-reports.
Many thanks for your understanding and your help improving Debian,
past and present.
--- End Message ---