On Mon, Jan 27, 2003 at 07:35:50AM -0500, Scott Chapman wrote: > I took down one of the virtual servers, and attached it's minidisk to > another one running SuSE. I then used debootstrap to install the base > configuration on that minidisk. I then configured the base Debian image > and ran zipl to make it bootable. I detached the minidisk from the SuSE > system, logged on to the VM userid for the Debian system and tried to IPL > it (device 151). It seemed to start the boot process ok, but it fails > trying to access the ext2 filesystem on the minidisk that has the root > filesystem--which is the same minidisk it was booting off from. I can > re-attach the minidisk to the SuSE system and access the file system fine, > but I can't even do an fdasd on the volume from the Debian system--almost > like Debian isn't recognizing the DASD at all, despite being able to boot > from it.
Debian uses the devfs. Its DASD is named things like /dev/dasd/device/0151/part1 rather than /dev/dasda /dev/dasdb, etc. I'm confused as to how you did this, because Debian can write a correct IPL record for a devfs system. Your /boot/paramfile file should have something like root=/dev/dasd/0151/part1 ro noinitrd dasd=0151-0152 vmpoff="LOGOFF" But it sounds like you have root=/dev/dasdb1 at the start instead. > Even trying to run fdasd fails on Debian: > (none):~# fdasd /dev/dasdb > fdasd /dev/dasdb > > fdasd error: device verification failed > The specified device is not a valid DASD device > (none):~# fdasd /dev/dasd/0151/device would work, though. Adam -- [EMAIL PROTECTED] "My eyes say their prayers to her / Sailors ring her bell / Like a moth mistakes a light bulb / For the moon and goes to hell." -- Tom Waits
