On one of my Linux "SLES8" systems, I had the same problem.
The reason for the problem was that I did not have an FBA device that was to be defined to Linux, at install time. Of course it eventually to be a swap file, but initially, I used old Ramac dasd. The old Ramac dasd being cheaper and more available then using vdisk on my 1 GB system. And these were test systems.
But then I documented the addition of vdisk space to a running system. Perhaps I would need to add vdisk volumes to a production system later on.
Without having an FBA device at install time, the FBA device driver wasn't part of the resulting install package.
It is a simple process to add this driver to a running system. I have it documented (under a page had written) and, if you still need it, I will send it to you Friday.
I haven't taken my SLES8 technical notes and validated them on a SLES9 system, yet. But it is in the plans.
Being a VM and VSE type for quite a while, and seeing small, incremental updates between versions and releases, it is really an eye opener at some of the major changes between SLES8 and SLES9. I guess for the better, but major changes none the less.
Tom Duerbusch THD Consulting
Peter Rothman wrote:
Update. I tried the commands ('mkinitrd; zipl') below but could not get the vdisk swap active.
I am now trying to put everything back as it was before but am having problems. My original mdisk/dasd setup was:
201 - dasda: 3390 full pack linux system 202 - dasdb: 300 cylinders of 3390 for swap 203 - dasdc: 3390 full pack that had a mount point of /ztpf.
When I boot now the 202 and 203 are not recognized and linux complains about dasdc and /ztpf - se below.
Checking file systems... fsck 1.34 (25-Jul-2003) Checking all file systems. [/sbin/fsck.ext2 (1) -- /ztpf] fsck.ext2 -a /dev/dasdc1 fsck.ext2: No such device or address while trying to open /dev/dasdc1 Possibly non-existent or swap device? fsck.ext2 /dev/dasdc1 failed (status 0x8). Run manually! [1A..failedblogd: no message logging because /var file system is not accessible No available keymaps for machine s390x found fsck failed. Please repair manually and reboot. The root file system is currently mounted read-only. To remount it read-write do:
bash# mount -n -o remount,rw /
Attention: Only CONTROL-D will reboot the system in this maintanance mode. shutdown or reboot will not work.
Please, can someone please advise on how to fix this. This is a base install and nothing has been written to /ztpf so I could re-install and start from scratch but I would prefer to fix and learn at the same time.
Thanks Peter.
Hannes Reinecke <[EMAIL PROTECTED]> Sent by: Linux on To 390 Port [email protected] <[EMAIL PROTECTED] cc IST.EDU> Subject Re: FBA device driver 05/19/2005 02:35 AM
Please respond to Linux on 390 Port <[EMAIL PROTECTED] IST.EDU>
Leland Lucius wrote:
I was trying to change my Linux swap to vdisk and received
he message
below. Where do I get the driver. I am using SUSE 9 - the free one.
Try run 'mkinitrd; zipl'. mkinitrd needs to be run after each change to /etc/fstab to make sure that all devices are properly activated.
Will this fix his issue with /sbin/modprobe not being found too?
Most likely. /sbin/modprobe is invoked (or rather, would be invoked if found) when a DASD should be configured for which no corresponding module has been loaded. However, within initrd all modules are loaded statically in a previous step. So if modprobe should be invoked this indicates that the module has not been loaded, which in turn means the modules is not copied into the initrd. So recreating the initrd with 'mkinitrd; zipl' should fix it.
Cheers,
Hannes -- Dr. Hannes Reinecke [EMAIL PROTECTED] SuSE Linux AG S390 & zSeries Maxfeldstra_e 5 +49 911 74053 688 90409 N|rnberg http://www.suse.de
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
