I went through this a couple of weeks ago. SLES9 by default doesn't add a DASD= into the zipl.conf parameters line. Therefore the system only knows about the dasd defined in the install. By adding the DASD= statement (whith both the old and new dasd) from a rescue system and then running zipl you will be able to reipl and have the disks active.
On Tue, 2005-03-29 at 10:49 -0600, Tom Duerbusch wrote: > I think this is an easy one. > > I added some dasd a couple weeks ago. My notes show that I didn't do > it manually, I used Yast (so I should have been convered<G>). > > Then I created a LVM over the 5 volumes, again thru Yast. > > Started using LVM and everything was great. > > Yesterday, I did the first reboot of this machine since I added the > dasd. > > Well, the boot fails with: > > Activating LVM volume groups... > > No volume groups found > > ..skipped > > Checking file systems... > > fsck 1.34 (25-Jul-2003) > > Checking all file systems. > > [/sbin/fsck.reiserfs (1) -- /use] fsck.reiserfs -a /dev/dasdb1 > > Reiserfs super block in block 16 on 0x0 of format 3.6 with standard > journal > Blocks (total/free): 600816/592586 by 4096 bytes > > Filesystem is clean > > Replaying journal.. > > Reiserfs journal '/dev/dasdb1' in blocks [18..8211]: 0 transactions > replayed > Checking internal tree..finished > > [/sbin/fsck.reiserfs (1) -- /data1] fsck.reiserfs -a > /dev/system/lvmdata1 > > > Failed to open the device '/dev/system/lvmdata1': No such device or > address > > > > > Warning... fsck.reiserfs for device /dev/system/lvmdata1 exited with > signal 6. > > > A cat /proc/dasd/devices does not show the 5 volumes. > A cat /etc/zipl.conf doesn't (no longer in sles9) show the volumes > linux knows about. Apparently it is dynamically sensing the devices. > > The big difference in Sles8 vs Sles9, is now we have to "activate" dasd > prior to dasdfmt, etc. > > I think all I need to do is: > > 1. manually activate the dasd > 2. update some file to show these volumes should be activated. > > Anyway, I'm now at: > > 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. > > Give root password for login: > > Which means, my only access is via 3270 console (no IP connections have > been started). And only dasda1 is mounted. > > So, how do I manually "activate" dasd? Assuming that was the problem. > > Tom Duerbusch > THD Consulting > > ---------------------------------------------------------------------- > 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 > -- Jerry Whitteridge Safeway Inc. PH: 925 951 4184 Fax:925 951 4204 "MMS <safeway.com>" made the following annotations. ------------------------------------------------------------------------------ Warning: All e-mail sent to this address will be received by the Safeway corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain information proprietary to Safeway and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. ============================================================================== ---------------------------------------------------------------------- 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
