boot reseau: pb demarrage serveur dhcp Fermé

Question

Bonjour,

je voudrais installer une debian via le reseau.
j'ai suivi ce tuto:
http://www.lea-linux.org/cached/index/Install-install-debian-reseau.html

tout se passe bien jusqu'au démarrage du serveur dhcp:
Starting DHCP server: dhcpd failed to start - check syslog for diagnostics.

n'etant pas un expert meme en lisant le syslog je ne suis pas capable de resoudre mon pb
Sep 18 16:55:19 pc kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep 18 16:55:19 pc kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep 18 16:55:19 pc kernel: ide: failed opcode was: unknown
Sep 18 17:12:30 pc kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep 18 17:12:30 pc kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep 18 17:12:30 pc kernel: ide: failed opcode was: unknown
Sep 18 17:34:43 pc -- MARK --
Sep 18 17:54:43 pc -- MARK --
Sep 18 17:57:47 pc kernel: VMBlock warning: DentryOpRevalidate: invalid args from kernel
Sep 18 17:57:47 pc kernel: VMBlock warning: DentryOpRevalidate: invalid args from kernel

pourriez vous m'aider?
merci d'avance

duvduv

kiki · Answer

BBonsoir,

les erreurs que vous avez sont des problèmes de disque.

Donnez votre fichier de config dhcp que l'on verifie...

Cordialement,

duvduv · Answer

# Sample configuration file for ISC dhcpd for Debian
#
# $Id: dhcpd.conf,v 1.4.2.2 2002/07/10 03:50:33 peloy Exp $
#

# option definitions common to all supported networks...
option domain-name "fugue.com";
option domain-name-servers toccata.fugue.com;

option subnet-mask 255.255.255.224;
default-lease-time 600;
max-lease-time 7200;

#subnet 204.254.239.0 netmask 255.255.255.224 {
#  range 204.254.239.10 204.254.239.20;
#  option broadcast-address 204.254.239.31;
#  option routers prelude.fugue.com;
#

#}

# The other subnet that shares this physical network
#subnet 204.254.239.32 netmask 255.255.255.224 {
#  range dynamic-bootp 204.254.239.10 204.254.239.20;
#  option broadcast-address 204.254.239.31;
#  option routers snarg.fugue.com;
#}

#subnet 192.5.5.0 netmask 255.255.255.224 {
#  range 192.5.5.26 192.5.5.30;
#  option name-servers bb.home.vix.com, gw.home.vix.com;
#  option domain-name "vix.com";
#  option routers 192.5.5.1;
#  option subnet-mask 255.255.255.224;
#  option broadcast-address 192.5.5.31;
#  default-lease-time 600;
#  max-lease-time 7200;
#}

# Hosts which require special configuration options can be listed in
# host statements.   If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.

#host passacaglia {
#  hardware ethernet 0:0:c0:5d:bd:95;
#  filename "vmunix.passacaglia";
#  server-name "toccata.fugue.com";
#}

# Fixed IP addresses can also be specified for hosts.   These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP.   Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
#  hardware ethernet 08:00:07:26:c0:a5;
#  fixed-address fantasia.fugue.com;
#}

# If a DHCP or BOOTP client is mobile and might be connected to a variety
# of networks, more than one fixed address for that host can be specified.
# Hosts can have fixed addresses on some networks, but receive dynamically
# allocated address on other subnets; in order to support this, a host
# declaration for that client must be given which does not have a fixed
# address.   If a client should get different parameters depending on
# what subnet it boots on, host declarations for each such network should
# be given.   Finally, if a domain name is given for a host's fixed address
# and that domain name evaluates to more than one address, the address
# corresponding to the network to which the client is attached, if any,
# will be assigned.
#host confusia {
#  hardware ethernet 02:03:04:05:06:07;
#  fixed-address confusia-1.fugue.com, confusia-2.fugue.com;
#  filename "vmunix.confusia";
#  server-name "toccata.fugue.com";
#}

#host confusia {
#  hardware ethernet 02:03:04:05:06:07;
#  fixed-address confusia-3.fugue.com;
#  filename "vmunix.confusia";
#  server-name "snarg.fugue.com";
#}

#host confusia {
#  hardware ethernet 02:03:04:05:06:07;
#  filename "vmunix.confusia";
#  server-name "bb.home.vix.com";
#}


#host confusia {
#  hardware ethernet 02:03:04:05:06:07;
#  fixed-address confusia-3.fugue.com;
#  filename "vmunix.confusia";
#  server-name "snarg.fugue.com";
#}

#host confusia {
#  hardware ethernet 02:03:04:05:06:07;
#  filename "vmunix.confusia";
#  server-name "bb.home.vix.com";
#}

subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.50 192.168.0.99;
server-name "server";
next-server ipduserveur
filename "/tftpboot/pxelinux.0";
}

duvduv · Answer

bonsoir,

en reeditant mon fichier conf je ne recoit plus que:
ep 19 18:27:57 pc kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep 19 18:27:57 pc kernel: ide: failed opcode was: unknown
Sep 19 18:55:04 pc -- MARK --
Sep 19 19:15:04 pc -- MARK --
Sep 19 19:35:04 pc -- MARK --
Sep 19 19:55:05 pc -- MARK --
Sep 19 20:15:07 pc -- MARK --
Sep 19 20:35:08 pc -- MARK --
Sep 19 20:55:10 pc -- MARK --
Sep 19 21:15:10 pc -- MARK --


en me baladant un peu j'ai trouvé que c'etait surement un pb de secteurs sur le dd.
du coup je tente
fsck -c -c hda 
resultat:
Sep 19 18:27:57 pc kernel: ide: failed opcode was: unknown
Sep 19 18:55:04 pc -- MARK --
Sep 19 19:15:04 pc -- MARK --
Sep 19 19:35:04 pc -- MARK --
Sep 19 19:55:05 pc -- MARK --
Sep 19 20:15:07 pc -- MARK --
Sep 19 20:35:08 pc -- MARK --
Sep 19 20:55:10 pc -- MARK --
Sep 19 21:15:10 pc -- MARK --
Sep 19 21:35:11 pc -- MARK --

alors je tente: 
hdparm -m 16 /dev/hda
resultat:
Sep 19 20:15:07 pc -- MARK --
Sep 19 20:35:08 pc -- MARK --
Sep 19 20:55:10 pc -- MARK --
Sep 19 21:15:10 pc -- MARK --
Sep 19 21:35:11 pc -- MARK --
Sep 19 21:55:13 pc -- MARK --
Sep 19 22:01:02 pc kernel: cdrom: hdb: mrw address space DMA selected
Sep 19 22:01:02 pc kernel: cdrom open: mrw_status 'not mrw'
Sep 19 22:01:02 pc kernel: cdrom: hdb: mrw address space DMA selected
Sep 19 22:01:02 pc kernel: cdrom open: mrw_status 'not mrw'

est ce que quelqu'un peut m'aider?

Boot reseau: pb demarrage serveur dhcp

3 réponses

Discussions similaires