- To: submit@bugs.debian.org
- Cc: ecuador01@reagan.com
- Subject: Installation Report-- Install glitch-keeps looping the install
- From: ecuador01@reagan.com
- Date: Wed, 9 Oct 2013 19:50:36 -0400 (EDT)
- Message-id: <1381362636.552825959@webmail.reagan.com>
Package: installation-reports
My Name: Myrna
email: ecuador01@reagan.com
Boot method: network: via website http://goodbye-windows.com.
Image version: see above and 6.0.7
Date: 9 October 2013 at 12 noon central time and repeated at about 4:30 same afternoon
Machine: custom build from Puget systems: ACPIx64 based.
Processor: Intel i7 3.1ghz quad core
Memory:16mb
Partitions:
drives C, E, and R are windows. The 6 debian volumes are located on the back half of the drive containing E, not primary .
The first 6 volumes are from the debian installation partitioning process:
5=root
6=/usr
7=/var
8=swap
9=tmp
10=home
scsi12 (0,0,0) sdb ext 4
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [0 ]
Detect network card: [ 0]
Configure network: [ 0]
Detect CD: [ 0]
Load installer modules: [ 0]
Detect hard drives: [ 0]
Partition hard drives: [ 0]
Install base system: [ 0]
Clock/timezone setup: [ 0]
User/password setup: [ 0]
Install tasks: [ 0]
Install boot loader: [ 0]
Overall install: [e ]
Comments/Problems:
I used jigdo to download the first few debian CDs for 6.0.7 stable version but there were 2 problems: one the disk wouldn't boot and so when I used setup.exe the 3rd screen said the win32-loader.ini file could not be found. However, that file is easily seen just below the setup.exe file. So why is the ini file not being recognized. Then I went to goodbye-windows.com with the hope of getting the win32-loader file thinking I could point it to the cd to complete the installation. Unfortunately, the loader file at the site was connected to the entire install. So I went with it.....twice, with the same outcome both times........
the install seemed to go without problem all the way to the point of rebooting after the install had completed. Upon reboot grub showed only 2 lines—one for the win7 install and the other said: debian/linux –complete installation . The system just begins the installation process again. I can get to the install menu and step through any step near the end of the install process but the system takes me back to the beginning of the install.
I am going back into the install and checking the logs tonight but am hoping there is a fix.
Should I instead NOT use grub? In the win 7 bios I left the boot option as both legacy and UEFI. I know other machines do not have that option-those machines must select legacy only. Should I have changed that to only legacy? It is after the fact but I shall give that a try.
Does the install need to be on the first part of the drive? It isn't currently.
<Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.>
--- End Message ---