Sandy, Is your LINUX running under VM? If so, did you change the minidisk statements in the directory and make sure that the volumes are in the sys config and are attached to system when you start?
I moved some of my dasd around a few months ago under VM and didn't have any problems. It also verified that my DDR backups for disaster recovery would work. Loren Charnley, Jr. Tech Support Administrator Family Dollar Stores, Inc. Phone: (704) 847-6961 Ext. 2000 > -----Original Message----- > From: Gelbard, Sandy [SMTP:[EMAIL PROTECTED]] > Sent: Monday, April 15, 2002 10:37 AM > To: [EMAIL PROTECTED] > Subject: can't mount root after dasd move > > Hello again, > > I am having difficulty accessing my linux system now that I have moved my > dasd packs. > Here are the facts: > > 1) I updated my parmfile to replace the old ucb's with the new ucb's > > old = dasd=31A0,31A1 root=/dev/dasdb1 noinitrd > > new = dasd=216A,216B,216C root=/dev/dasdb1 noinitrd > > 2) I ran silo: > lnx390t:cd /boot > lnx390t:/boot # silo -d /dev/dasdb -f image -p parmfile -b ipleckd.boot > o->ipldevice set to /dev/dasdb > o->image set to image > o->parmfile set to parmfile > o->bootsect set to ipleckd.boot > Testlevel is set to 0 > IPL device is: '/dev/dasdb' > bootsector is: 'ipleckd.boot'...ok... > bootmap is set to: './boot.map'...ok... > Kernel image is: 'image'...ok... > original parameterfile is: 'parmfile'...ok...tempfile is ./parm.q9EPib > final parameterfile is: './parm.q9EPib'...ok... > ix 0: offset: 082b7a count: 0c address: 0x00000000 > ix 1: offset: 082b87 count: 80 address: 0x0000c000 > ix 2: offset: 082c07 count: 80 address: 0x0008c000 > ix 3: offset: 082c87 count: 72 address: 0x0010c000 > ix 4: offset: 082e03 count: 01 address: 0x00008000 > Bootmap is in block no: 0x00082e04 > > > 3) I backed up my dasd w/ OFFLINDR > > 4) My system was brought down (not cleanly if that matters) > 5) I activated my new IOCP to include new dasd devices > 6) Restored data to vols : 31a0 to 216a etc... > 7) IPL'd from 216B and received the following : > > amongst other messages... > > Command line is dasd=33a0,33a1 root=/dev/dasdb1 initrd ro (<---this is a > bad sign) > .... > detected device 216a > detected device 216b > detected device 216c > (so my gen is looking good) > ... > > dasd: devn 0x33A1 on subchannel 9342= /dev/dasdb (94:5) cannot open > unrecognized device. > VFS: cannot open root 5e:05 > > My guess is I "botched" SILO . > > > Is there a way to get this system up on the new dasd without a complete > reinstall ? > > TIA, > SG
