[ENBD] diskless enbd-client/enbd on initrd

[Rudolph Bott]

Ok, I made another huge mistake ;)
Since I used the nbd_root package as a base for my 
root-over-enbd-initrd, i created the initrd with genROMfs
i think this explains the pid-file-writing-errors quite well :S

now i switched over to an ext2 ramdisk...and as you can see below, 
writing to it works

now the problem has shifted to a somewhat more difficult problem:
ENBD #2469[1]: do_enbd_request device not enabled.
(at least i think thats the error...can't find anything else)
What does that mean? google didn't come up with a good answer to that one..

.....
TCP: Hash tables configured (established 16384 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
IP-Config: Complete:
       device=eth0, addr=172.16.20.3, mask=255.255.255.224, 
gw=255.255.255.255,
      host=nbdtest, domain=, nis-domain=(none),
      bootserver=1.2.3.4, rootserver=1.2.3.4, rootpath=
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 2340KiB [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 108k freed
enbd_root version 0.2
root: 172.16.20.1:1111
Loading enbd module...
ENBD #5427[0]: enbd_init Network Block Device originally by 
pavel at elf.mj.gts.cz
ENBD #5428[0]: enbd_init Network Block Device port to 2.0 by ptb at it.uc3m.es
ENBD #5430[0]: enbd_init Network Block Device move networking to user 
space by amarin at it.uc3m.es
ENBD #5432[0]: enbd_init Enhanced Network Block Device 2.4.30 $Date: 
2002/09/17 16:33:22 $ by ptb at it.uc3m.es
ENBD #5472[0]: enbd_init registered device at major 43
Starting enbd-client...
enbd-client   592: client says target 0 is 172.16.20.1:1111
enbd-client   592: client (-1) opened device /dev/nda
enbd-client   592: client (-1) opened NBD device /dev/nda (2b00)
warning: process `enbd-client' used the obsolete bdflush system call
Fix your initscripts?
enbd-client   592: client (-1) left kernel bdflush sync boundary at 
134988640%
warning: process `enbd-client' used the obsolete bdflush system call
Fix your initscripts?
warning: process `enbd-client' used the obsolete bdflush system call
Fix your initscripts?
enbd-client   592: client (-1) set kernel bdflush async boundary to 25% 
from 134971615%
enbd-client   592: client (-1) detaches from shell
nbd/pidfile   593: # 147 lockpidfile: returning err 0 for lock attempt
enbd-client   593: client (-1) made pidfile 
/var/run/enbd-client-xenoo.pid with pid 593
enbd-client   593: client (-1) starts introduction sequence on 
172.16.20.1:1111
ENBD #2469[1]: do_enbd_request device not enabled.
EXT3-fs: unable to read superblock
mount: Invalid argument
pivot_root: Device or resource busy
Failed to start init :(
Kernel panic - not syncing: Attempted to kill init!


-- 
Mit freundlichen Gruessen / with kind regards
  Rudolph Bott

-------------------------------------------------------------------
Megabit Informationstechnik GmbH  Karstr.25  41068 Moenchengladbach
Tel: 02161/308980   mailto:info at megabit.net       ftp://megabit.net
Fax: 02161/3089818  mailto:support at megabit.net   http://megabit.net
-------------------------------------------------------------------