Looks to me like he might have added the new disk at the beginning of the address list, and it's become dasda, replacing the original one.
Remember, the device nodes are assigned sequentially based on the device list passed in the DASD= parm in zipl.conf. First device becomes dasda, second, dasdb, and so on. So you should always add new device numbers AFTER existing ones to keep the sequence intact. LVM is smart enough to find it's volumes even if they move, but you still need the root filesystem to stay put. > -----Original Message----- > From: Post, Mark K [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 08, 2003 3:28 PM > To: [EMAIL PROTECTED] > Subject: Re: [LINUX-390] Urgent, receiving panic on my guest > > > In that case, it sounds like you re-ran zipl, but the contents of > /etc/zipl.conf are bad. > > Re-IPL your system from the reader, using the three starter > files. Do: > insmod dasd dasd=addr1,addr2,addr3 > mount /dev/dasda1 /mnt > chroot /mnt > cd /etc > cat zipl.conf > > Does the "parameters=" value specify all the disks you want? Does it > specify the correct "root=" value? If not, start the > installation process, > but when you telnet/ssh in, do this: > chroot /mnt > vi /etc/zipl.conf > zipl > exit > > During the vi editing session, make sure the parms are > correct. When you > reboot your system, make sure the parameters are reflected in > the messages > put out by the system. > > > Mark Post > > -----Original Message----- > From: Eric Sammons [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 08, 2003 3:04 PM > To: [EMAIL PROTECTED] > Subject: Re: Urgent, receiving panic on my guest > > > How would one fix this if it was working prior to the > addition of a new > disk? > > Eric Sammons > (804)697-3925 > FRIT - Infrastructure Engineering > > > > > > "Post, Mark K" <[EMAIL PROTECTED]> > Sent by: Linux on 390 Port <[EMAIL PROTECTED]> > 07/08/2003 02:39 PM > Please respond to Linux on 390 Port > > To: [EMAIL PROTECTED] > cc: > Subject: Re: Urgent, receiving panic on my guest > > It looks like you punched an install kernel to the virtual > reader, but not > the initrd. Device "01:00" is a ram disk. > > > Mark Post > > -----Original Message----- > From: Eric Sammons [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 08, 2003 2:31 PM > To: [EMAIL PROTECTED] > Subject: Urgent, receiving panic on my guest > Importance: High > > > Anyone seen this error before? If so how do you resolve it? > > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. > VFS: Cannot open root device "" or 01:00 > Please append a correct "root=" boot option > Kernel panic: VFS: Unable to mount root fs on 01:00 > HCPGIR450W CP entered; disabled wait PSW 000A0000 802A04F0 > > > Thanks! > Eric Sammons > (804)697-3925 > FRIT - Infrastructure Engineering >
