Debootstrap error

[honest_new-b]

Hello, I'm trying to install Debian for the first time and after getting to the "Install the base system" part I get a Debootstrap error. When I try to preform the installation I get the error "Failed to determine the codename for the release.". If it's any help, I'm trying to do a Unetinboot install from a SanDisk Cruzer USB drive.

Thanks.

[TobiSGD]

Don't use Unetbootin. Use dd (Linux/UNIX) or win32 image writer (Windows) to directly write the ISO image to the USB device.

[Illuminated]

I ran into this same problem. I used unetbootin to create the image on a USB thumb drive.

unetbootin was not the problem. The problem was related to the media not being mounted under /cdrom

I had to manually mount the usb to /cdrom and when I retried the install, I was able to get past the "bootstrap error".

I did this by hitting alt-f2 and then
mount /dev/sdc1 /cdrom
then alt-f1 to get back to the install

The device for the usb drive may vary. For me it was /dev/sdc1.

I have no idea why the installer isn't smart enough to know to either mount the install media in /cdrom itself of look for it in /target/media/cdrom where it already had it mounted.

[llivv]

I ran into this same problem. I used unetbootin to create the image on a USB thumb drive.

unetbootin was not the problem. The problem was related to the media not being mounted under /cdrom

I had to manually mount the usb to /cdrom and when I retried the install, I was able to get past the "bootstrap error".

I did this by hitting alt-f2 and then
mount /dev/sdc1 /cdrom
then alt-f1 to get back to the install

The device for the usb drive may vary. For me it was /dev/sdc1.

I have no idea why the installer isn't smart enough to know to either mount the install media in /cdrom itself of look for it in /target/media/cdrom where it already had it mounted.

very inte4resting

[Byakko]

Thank you very much for this answer, it helped me go through the installation !

I think the USB connection was dropped for some reason during the very very long cleaning process (LVM encrypted).

[abladelnx]

I ran into this same problem. I used unetbootin to create the image on a USB thumb drive.

unetbootin was not the problem. The problem was related to the media not being mounted under /cdrom

I had to manually mount the usb to /cdrom and when I retried the install, I was able to get past the "bootstrap error".

I did this by hitting alt-f2 and then
mount /dev/sdc1 /cdrom
then alt-f1 to get back to the install

The device for the usb drive may vary. For me it was /dev/sdc1.

I have no idea why the installer isn't smart enough to know to either mount the install media in /cdrom itself of look for it in /target/media/cdrom where it already had it mounted.

Thank you. This works perfectly. Must say that I'm surprised this hasn't been fixed in the interim though!

[beefes]

Thanks. Worked like a charm.

[bbbf0621]

Thank you! this fixed my problem too, hope it'll be fixed in next update

[milomak]

am i to believe that the installer doesn't know to identify that it is being installed via usb?

[GarryRicketson]

Don't use Unetbootin. Use dd (Linux/UNIX) or win32 image writer (Windows) to directly write the ISO image to the USB device.

+1

Illuminated »unetbootin was not the problem.

Usually it does not work with unebootin, that is the problem.

From:https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775689Unetbootin is wasting massive amounts of developer and user time.

Please add:

* An entry in the Debian package description to say "Do not use
unetbootin for Debian CD images, just write them raw using dd" or
similar.

I have no idea why the installer isn't smart enough to know to either mount the install media in /cdrom itself of look for it in /target/media/cdrom where it already had it mounted.

The installer is fine, but when people do not read manuals on how to use it, this is where the problems start.
https://www.debian.org/releases/stable/installmanual

https://wiki.debian.org/BootUsb
If one does go through the Debian Documentation, ( I have), and I have not ever been able to find any where that they suggest or recommend using "unebootin".
These are good places to start, before trying to install,
https://debian-handbook.info/browse/stable/installation.html#sect.installation-methods

https://debian-handbook.info/browse/stable/sect.installation-steps.html

[spacex]

Garry. Stop throwing all that documentation at people. The problem was solved, and unetbootin was not the issue in this case. Just accept it and move on. Your latest post was redundant. You don't need to defend your answer just because someone chooses to fix their issue in another way. Whatever works, works. Easy as that. You can never argue with results.

[dzz]

This issue has been discussed here and solved, at least for wheezy, already. You don't have to trash your nicely customized 64GB multiboot sandisk cruzer with dd. viewtopic.php?f=17&t=75604

Here's the documentation everyone missed (which, like "unetbootin", uses syslinux not dd): https://www.debian.org/releases/stable/ ... y-flexible

[kellt]

I had same problem installing jessie on a laptop, I'd left the installer alone for several hours and the cdrom had unmounted itself somehow. When I plugged it back in, it came up as sr1, instead of sr0. Then this error. Mounting the DVD to /cdrom fixed the issue.

[jkbgbr]

The problem still exists on a Thinkpad x61 when installing jesse from USB written using Etchy. The workaround is effective, however, as a first-time linux installing user I find it _very_ annoying to have to deal with a such a problem in 2017!

[Head_on_a_Stick]

as a first-time linux installing user I find it _very_ annoying to have to deal with a such a problem in 2017!

As a long-time forum member, I find it _very_ annoying when the n00bs don't even bother to read TFM...

https://www.debian.org/releases/jessie/ ... -isohybrid

EDIT: welcome to the forums!