Robert, If this is a 2.4 system, fdasd must be used to create at least one partition on the target volumes before running mke2fs.
Mark Post -----Original Message----- From: Nix, Robert P. [mailto:Nix.Robert@;mayo.edu] Sent: Wednesday, November 06, 2002 11:25 AM To: [EMAIL PROTECTED] Subject: SuSE install frustration re: First DASD mount... This should be dirt simple, and I've already done it several times, so I'm not really understanding what I've done wrong here, but... I wanted to build a new Linux/390 image. I created the new userid, loaded up the ram image, went through defining the network and logged into root via telnet. I ran YaST, picked the language and install from FTP, selected my swap device, and got to the dasd definitions. On the Partition Harddrives box, "Partitioning" is not an allowable choice (tabbing jumps over it). I can only choose "Do not partition" or "Setting up LVM". I marked my dasd: 292-ext2-Normal format-/, 294-ext2-Normal-/usr, 295-ext2-Normal-/home, and 296-ext2-Normal-/usr/local. I selected continue. The message I get back is "An error occurred mounting the filesystem of partition "/dev/dasda1" to the directory "/mnt". Here is the error message of the 'mount' command: mount: wrong fs type, bad option, bad superblock on /dev/dasda1, or too many mounted file systems". It gives options for "Repeat" or "Abort". On the system console, I have the message "VFS: Can't find an ext2 filesystem on dev dasd(94,1).", just after the message about adding the swap-space. >From the system console, I can mount -t ext2 /dev/dasda /mnt, but I cannot mount -t ext2 /dev/dasda1 /mnt. I tried hand-formatting and running mke2fs for the devices before starting YaST, but that seems to have no effect on the problem either. What am I doing wrong? ---- Robert P. Nix internet: [EMAIL PROTECTED] Mayo Clinic phone: 507-284-0844 200 1st St. SW page: 507-255-3450 Rochester, MN 55905 ---- "In theory, theory and practice are the same, but in practice, theory and practice are different."
