[Bug 1043936] Re: Biosdevname not installed in the target after server install
Dmitrijs Ledkovs
launchpad at surgut.co.uk
Thu Aug 30 19:42:00 UTC 2012
Was the network available during the first failed installation? (and
usable?!)
Aug 30 16:07:55 in-target: The following extra packages will be installed:
Aug 30 16:07:55 in-target: libpci3
Aug 30 16:07:55 in-target: The following NEW packages will be installed:
Aug 30 16:07:55 in-target: biosdevname libpci3
Aug 30 16:07:55 in-target: 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Aug 30 16:07:55 in-target: Need to get 47.8 kB of archives.
Aug 30 16:07:55 in-target: After this operation, 213 kB of additional disk space will be used.
Aug 30 16:07:55 in-target: Err http://us.archive.ubuntu.com/ubuntu/ quantal/main libpci3 amd64 1:3.1.9-5ubuntu2
Aug 30 16:07:55 in-target: Temporary failure resolving 'us.archive.ubuntu.com'
Aug 30 16:07:55 in-target: Err http://us.archive.ubuntu.com/ubuntu/ quantal/main biosdevname amd64 0.4.1-0ubuntu1
Aug 30 16:07:55 in-target: Temporary failure resolving 'us.archive.ubuntu.com'
Aug 30 16:07:55 in-target: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/p/pciutils/libpci3_3.1.9-5ubuntu2_amd64.deb Temporary failure resolving 'us.archive.ubuntu.com'
Aug 30 16:07:55 in-target: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/b/biosdevname/biosdevname_0.4.1-0ubuntu1_amd64.deb Temporary failure resolving 'us.archive.ubuntu.com'
Aug 30 16:07:55 in-target: E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Needs checking if biosdevname is available in the squashfs and installed
by the default server tasks / always?!
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1043936
Title:
Biosdevname not installed in the target after server install
Status in “debian-installer” package in Ubuntu:
Triaged
Status in “debian-installer” source package in Quantal:
Triaged
Bug description:
I'm installing quantal from scratch on a Dell PowerEdge R310. When the
system finishes installing ifconfig -a thinks the interface names are
eth0 and eth1. The /etc/network/interfaces file thinks the name should
be em1. Upon initial boot, post install the interface does not come
up.
cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto em1
iface em1 inet dhcp
root at rizzo:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr d4:ae:52:a3:6a:22
inet addr:10.97.2.3 Bcast:10.97.2.255 Mask:255.255.255.0
inet6 addr: fe80::d6ae:52ff:fea3:6a22/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18191 errors:0 dropped:0 overruns:0 frame:0
TX packets:4532 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20872409 (20.8 MB) TX bytes:663870 (663.8 KB)
eth1 Link encap:Ethernet HWaddr d4:ae:52:a3:6a:23
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1184 (1.1 KB) TX bytes:1184 (1.1 KB)
root at rizzo:~# biosdevname -i eth0
em1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1043936/+subscriptions
More information about the foundations-bugs
mailing list