Michael, Have you looked at the definition of the minidisk in the directory? If you have a VM label on the disk, it will be on cylinder 0. The minidisk should start on cylinder 1 or above or the VM label will be overwritten and the next time you IPL (reboot), LINUX will not be able to find the DASD because it will be looking for the VM label first. Just a thought, it has already happened to me.
Loren Charnley, Jr. Tech Support Administrator Family Dollar Stores, Inc. Phone: (704) 847-6961 Ext. 2000 > -----Original Message----- > From: Post, Mark K [SMTP:[EMAIL PROTECTED]] > Sent: Monday, October 14, 2002 11:38 PM > To: [EMAIL PROTECTED] > Subject: Re: Dasd partition disappeared > > While Michael and Volker work on this problem offline, I wanted to comment > that the shutdown, logoff, logon and re-boot _are_ (usually) unnecessary > with a 2.4 kernel system. I have in the past successfully done the "link > myuserid devaddr devaddr" command under z/VM, followed by the echo to > /dev/dasd/devices to activate a new minidisk so that I could dasdfmt it > and > start using it immediately. We won't know what happened in Michael's case > for a while, but it doesn't appear to be very common. > > Mark Post > > -----Original Message----- > From: Michael K Lambert [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 08, 2002 1:49 PM > To: [EMAIL PROTECTED] > Subject: Dasd partition disappeared > > > Hello everyone, > > I'm running a Red Hat 7.2 linux/390 network on a s390 G6 under z/VM. Just > yesterday I added a 5 gig minidisk from a mod9 to one of our images using > dirmaint. I added the new disk to zipl.conf, zipl'd, shutdown and logged > the image and brought it back up with the minidisk. I dasdfmt'd, fdasd'd > and put a ext2 filesystem on it. I then used the disk as normal, NFS > exporting it and sharing the data held on it with no problem. > > However, this morning I bounced the image again and, on startup, I got the > message "bad superblock" on dasde, the new disk, and was thrown into > single > user mode. After commenting out the /dev/dasde1 entry in /etc/fstab I was > able to boot fully. Attempting to fun e2fsck on the disk resulted in the > "bad superblock" message, and fdasd reported that there was no volume > label > or partition on it. The disk is still fully visible on the VM level, it > just appears that the linux level formatting had disappeared entirely. > > Has anyone else seen any problems similar to this? I have had this happen > once before, but I assumed it occured because I had linked the drive from > the owner to itself, eg from image lnxsa01 I issued the command "#cp link > lnxsa01 401 401 mr," so that I wouldn't need to bounce the image to pick > up > the drive. I avoided that self-linking this time, but here it is again. > > Michael Lambert ************************************************************ NOTE: This e-mail message contains PRIVILEGED and CONFIDENTIAL information and is intended only for the use of the specific individual or individuals to which it is addressed. If you are not an intended recipient of this e-mail, you are hereby notified that any unauthorized use, dissemination or copying of this e-mail or the information contained herein or attached hereto is strictly prohibited. If you receive this e-mail in error, notify the person named above by reply e-mail and please delete it. Thank you.
