yes, if you can overwrite the old partitions and are sure that is what your are overwriting you should.
My point being more that the install procedure is the same regardless of any aborted or other installs -- make sure partitions are there and install into them.

OK, thank you for clarifying. In my current spot in the install, I am seeing a screen that informs me:
"No ethernet card was detected. If you know the name of the driver needed by your ethernet card, you can select it from the list".

I was unable to determine my driver via googling. Should I go ahead by selecting "no ethernet card"?

Thanks for all the help. My apologies if this is tedious.

How did you install the first time? The hjardware has not changed so why is this news to you?

Oops, I guess I was unclear in my OP. This is the reason for my disquiet. Prior to the cancelled install, this did not occur. Now, after the cancelled install, it occurs whenever I begin the installation. So it seems as if something has changed.

Running from USB is funny. Believe it or not, how the flash drive is sitting in the port will affect its reliability. I've been through this, getting kernel panics on boot, to find that if I just wiggled the stick a bit and rebooted, the panic went away.

Just format the existing Linux partitions when installing. The only partition you really do not want to touch is the EFI Boot partition, it's usually the smallest one there on the order of 100-200MB, or thereabouts.

So, just to confirm- I should go ahead without selecting ethernet drivers, etc? Hopefully this is just down to something like a USB hiccup.

If you have no ethernet device, then there's no need to select one.

Yes, as long as you don't have a ethernet (wired connection)

After you installation is complete if the wifi doesn't work you can always find the driver for it in the debian package search for you wireless card.-

You'll just have to run a simple command that will tell us what wifi card you have but you should start another thread for that.

Well, I believe that I have one- unless this message didn't show up on the first run for some reason. In any event, I have proceeded, but now I cannot advance past configuring the package manager.

Regardless of which mirror I select, I get "bad archive mirror". This did not happen earlier. I am using a tether, but that seems to be my only option at the moment, owing to the absence of an ethernet port on this machine.

Virtual kernel 4 tells me that "mirror does not support the specified release(stretch)". This also did not happen prior to the failed install.


What should I do at this point? Thanks for all the help- you are a lifesaver.

I had that once, was a network issue, not a mirror issue.

http://forums.debian.net/viewtopic.p...=80657#p511231

Seems similar to your problem, maybe try some of those suggestions.

Well if it doesn't have an ethernet port it is very unlikely to have a vestigial ethernet device.
You're trying to do a net-install via your phone connected by usb?

Why not just get a full installer image then set up the network (and apt-mirrors) later.

athanasius, you do realize everyone on this forum has made a number of huge mistakes before. Don't think you are the only one. The best people here have made almost every mistake once or twice.

Thanks again for the help. By following one of the suggestions(running network config again) I was able to successfully connect to a mirror. However, once it actually begins to install files, I get the following:

Grub installation failed

"The 'grub-efi-ia32' package failed to install into /target/"

How should I proceed from here?

Indeed, that's how we're able to give the answers, because we've already learned the hard way as well.

Well, seeing as I am already here(and have sufficient mobile data), I wouldn't mind just going through with it this way, if possible. If not, that seems like the best course of action.

---------- Post added 08-08-15 at 06:01 PM ----------

Yeah, the OP may have been a little bit hysterical. I was worried I had somehow managed to brick my machine in a moment of stupidity, so I was a little perturbed.