I finally got this to work. I had INITRD_MODULES="reiserfs" set in /etc/sysconfig/kernel but still had the problem. I issued mkinitrd ?m ?reiserfs? /mnt/to but still had the problem. However, issuing export INITRD_MODULES="reiserfs" and then issuing the mkinitrd /mnt/to worked? I do not quite know why but hey, I am up and running.
Thanks to everyone that took interest. It is always much appreciated. Peter Peter E Abresch/EP/PEP 06/10/2005 07:02 PM To Linux on 390 Port <[email protected]> cc Subject Re: MINIX-fs: blocksize too small for device I actually shutdown the Linux guest, and then performed all my activities from another Linux Guest running the same version of everything. The method I am using is the same method that used to convert the reiserfs root to ext2 to begin with. It is: From z/VM format the mini disk Logoff linux guest Logon to different Linux guest link to old root using hcp link linuxxxx ? link to new root using hcp link linuxxxx ? chccwdev ?e 0.0.015a chccwdev ?e 0.0.0155 format new root using dasdfmt ?v ?f /dev/dasdf ?d cdl ?l root01 ?b 4096 ?p add partition using fdasd /dev/dasdf mkreiserfs /dev/dasdf1 mount /dev/dasdf1 /mnt/to mount /dev/dasdk1 /mnt/from cd /mnt/from tar -clpSf - . | (cd /mnt/to ; tar -xpSf - ) change ext2 to reiserfs in /mnt/to/etc/fstab mkinitrd /mnt/to chroot /mnt/to zipl exit umount /mnt/from umount /mnt/to chccwdev ?d 0.0.015a chccwdev ?d 0.0.0155 hcp det 15a hcp det 155 logon to my linux z/VM guest det 150 det 155 link * 155 150 mr ipl 150 cl At this point, I am open to any ideas. Peter Ranga Nathan <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 06/10/2005 06:27 PM Please respond to Linux on 390 Port <[email protected]> To [email protected] cc Subject Re: MINIX-fs: blocksize too small for device Peter: Converting the root to another file system is tricky. Bring down to single user create a new partition (you did that) format it as reiserfs (you did that) mount it as /mnt/root for example (you did that) umount any file systems under the root such as /boot, /usr, /var etc. ( so we dont not copy these file systems) cp -ax /* /mnt/root to copy from current root to the new partition unmount the current root unmount /mnt/root, the new one mount the new partition as root mount /usr, /var etc Bring up to network level check everything Change the fstab Do zipl Do mkinitrd reboot and pray! __________________________________________ Ranga Nathan / CSG Systems Programmer - Specialist; Technical Services; BAX Global Inc. Irvine-California Tel: 714-442-7591 Fax: 714-442-2840 "Peter E. Abresch Jr. - at Pepco" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 06/10/2005 02:39 PM Please respond to Linux on 390 Port <[email protected]> To [email protected] cc Subject Re: MINIX-fs: blocksize too small for device Ok, now I am charting unknow teritory, how do I do that, and what am I looking for. Peter "Post, Mark K" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 06/10/2005 05:11 PM Please respond to Linux on 390 Port <[email protected]> To [email protected] cc Subject Re: MINIX-fs: blocksize too small for device You may need to force the pre-load of the reiserfs module. Try mounting the initrd on a loopback device and examining what it has included. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Friday, June 10, 2005 5:07 PM To: [email protected] Subject: Re: MINIX-fs: blocksize too small for device Yes, I already thought of that and went back, recreated it, and added the mkinitrd before the zipl. The same problem. When I mount it on other Linux systems, it looks fine, I just cannot boot from it for some reason. I am at a loss. Peter "Post, Mark K" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 06/10/2005 04:57 PM Please respond to Linux on 390 Port <[email protected]> To [email protected] cc Subject Re: MINIX-fs: blocksize too small for device Did you re-run mkinitrd before doing the zipl command? Most likely you don't have reiserfs support in the initrd, and it's seeing the reiserfs as minix file system instead. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Friday, June 10, 2005 4:02 PM To: [email protected] Subject: MINIX-fs: blocksize too small for device I wanted to convert my ext2 root filesystem to resierfs. I made a new minidisk, formatted it, put a partition on it, and then performed a mkreiserfs. I mounted it and use the following command to copy everything over. tar -clpSf - . | (cd mnt ; tar -xpSf - ) I chroot to /mnt and performed a zipl. I updated FSTAB and reboot. Here is what I get: Loading kernel/drivers/s390/block/dasd_mod.ko dasd=150-15f Loading kernel/drivers/s390/block/dasd_eckd_mod.ko dasd(eckd): 0.0.0150: 3390/0A(CU:3990/01) Cyl:3338 Head:15 Sec:224 Using cfq io scheduler dasd(eckd): 0.0.0150: (4kB blks): 2403360kB at 48kB/trk compatible disk layout dasda:VOL1/ ROOT01: dasda1 dasd(eckd): 0.0.0151: 3390/0A(CU:3990/01) Cyl:3338 Head:15 Sec:224 dasd(eckd): 0.0.0151: (4kB blks): 2403360kB at 48kB/trk compatible disk layout dasdb:VOL1/ LVM001: dasdb1 dasd(eckd): 0.0.0152: 3390/0A(CU:3990/01) Cyl:3338 Head:15 Sec:224 dasd(eckd): 0.0.0152: (4kB blks): 2403360kB at 48kB/trk compatible disk layout dasdc:VOL1/ LVM002: dasdc1 dasd(eckd): 0.0.015f: 3390/0A(CU:3990/01) Cyl:500 Head:15 Sec:224 dasd(eckd): 0.0.015f: (4kB blks): 360000kB at 48kB/trk compatible disk layout dasdp:VOL1/ SWAP01: dasdp1 Waiting for device /dev/dasda1 to appear: ok rootfs: major=94 minor=1 devn=24065 rootfs: /sys/block/dasda/dasda1 major=94 minor=1 devn=24065 MINIX-fs: blocksize too small for device. Kernel panic: VFS: Unable to mount root fs on dasda1 HCPGIR450W CP entered; disabled wait PSW 000A0000 80446B76 What does that mean? What did I miss? Thank for any info. Peter ---------------------------------------------------------------------- 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 This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. ---------------------------------------------------------------------- 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 This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. ---------------------------------------------------------------------- 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 This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. ---------------------------------------------------------------------- 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
