Home » forums » Debian Help Forums: Users Helping Users » Installation Issues

AMD-64 installation issue

Tags:

This forum looks completely dead but i thought I'd give this a shot anyway.

I havn't used Debian for a while since I built my new system (ages ago actually) but finnally got round starting the installation.

I downloaded the unofficial AMD-64 netinstall image.

I ran the basic installation (no fancy options or anything). The first minor annoyance was the fact that either this installation or the partitions I created right before installing managed to destroy my Windows partition which I use for gaming. Although appearing on the GRUB bootloader the partition failed to boot. No big deal everything is backed up.

Here's the bit I need help resolving...

Having completed the installation of the base system the computer reboots and displays the same 4 lines repeatedly:

nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed

This text repeats forever stopping me from continuing with the installation.

Looks to me although I'm no expert like it's a HDD problem but the installation options when the CD is initially loaded don't say anything about SATA HDDs and there is nothing which suggests the basic installation is unsuitable for my machine.

Stats:

AMD Athlon 64 3000+ (newcastle core) 2.0GHz
DFI Lanparty UT nf3 250GB
2x 512mb Corsair DDR400
ATI Radeon 9550 (9600 bios)
120GB sata HDD

Any help you can offer me would be greatly appreciated as I'm very keen to get my system up and running again. Cheers. J.

Bookmark/Search this post with:
  • Delicious
  • Digg
  • StumbleUpon
  • Propeller
  • Reddit
  • Magnoliacom
  • Newsvine
  • Furl
  • Google
  • Yahoo
  • Technorati
0
‹ A Debian Router Gateway Configuration Installing a bare bones debian installation ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

1. Did the installer boot

Submitted by pinniped on Wed, 2006-08-16 03:16.

1. Did the installer boot and run with no problems?
2. What SATA controller have you got - is it part of the NForce-4 chipset?

As for your partitions "disappearing" - it is probably a case of GRUB guessing the wrong HD names. Try entering interactive mode (press any button except enter shortly after the GRUB screen is visible). You can then "edit" the boot arguments and try a different disk for booting WinDos. For example, if the WinDos partition was specified as (hd0,0) you might try (hd1,0). OR you can also try:
find ntldr
and see if/where GRUB finds that file - it will be the WinDos boot partition.

I had an awful problem getting my system to work because I had one IDE drive (with WinDos - for games and for submitting my tax return) and two SATA drives set up for RAID. After installing Linux, the BIOS for some reason decided to rename the drives - and WinDos would not boot! AAAAA! Then I thought "the drives were renamed, I will specify a different boot partition. OK - now the boot process starts - then crashes. I had to somehow edit the c:\boot.ini file to point to the correct partition, because the original partition (which was correct and allowed the system to boot) was now wrong. If you need to do that sort of work and your WinDos partition is NTFS rather than FAT, you can try the "Trinity Rescue Kit" to edit the file.

»

(1)Yeah there were no issues

Submitted by Zaireeka on Wed, 2006-08-16 07:07.

(1)Yeah there were no issues with the installation of the base system at all. The installer even recognises my HDD during setup.

I have my entire windows partition fully backed up and that's a breeze to install so I just let the installer run the partitioning automatically using the entire disc space but it had the same promlem so there wasn't an issue with the way I set up the partitions during the initial installation.

(2) My sata controller (as far as I know) is part of the nForce-3 chipset

»
Syndicate content