Hi Scott, I think you may be running into problems because the Debian kernel is compiled with the DEVFS option turned on. You need to reference your dasd with /dev/dasd/xxxx where xxxx is the device address instead of /dev/dasda /dev/dasdb etc.
Lonny -----Original Message----- From: Scott Chapman [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 7:36 AM To: [EMAIL PROTECTED] Subject: DASD not recognized in Debian I wanted to install Debian on one of our virtual servers just to see it work and possible to keep around as a "demo" system if we don't move forward witha full SuSE/VM installation at this time. Unfortunately I haven't been successful. 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. I've probably missed something "obvious"--if somebody could point it out to me, I'd appreciate it. Thanks! Scott Chapman American Electric Power dasd: initializing... debug: dasd: new level 3 dasd: Registered successfully to major no 94 dasd(eckd): ECKD discipline initializing dasd(eckd): /dev/dasdb ( 94: 4),0151@03: 3390/0A(CU:3990/01) Cyl:1365 Head:15 Sec:224 dasd(eckd): /dev/dasdb ( 94: 4),0151@03: 3390/0A(CU:3990/01): Configuration da ta read debug: dasdb: new level 3 dasd(eckd): /dev/dasdb ( 94: 4),0151@03: (4kB blks): 982800kB at 48kB/trk comp atible disk layout dasd(eckd): /dev/dasdc ( 94: 8),0152@04: 3390/0A(CU:3990/01) Cyl:50 Head:15 Se c:224 dasd(eckd): /dev/dasdc ( 94: 8),0152@04: 3390/0A(CU:3990/01): Configuration da ta read debug: dasdc: new level 3 dasd: waiting for responses... dasd(eckd): /dev/dasdc ( 94: 8),0152@04: (4kB blks): 36000kB at 48kB/trk compa tible disk layout Partition check: /dev/dasd/0151:VOL1/ 0X0180: p1 /dev/dasd/0152:VOL1/ 0X0152: p1 Checking root file system... fsck 1.27 (8-Mar-2002) fsck.ext2: No such file or directory while trying to open /dev/dasdb1 /dev/dasdb1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> 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):~#
