Just went through all this a while ago!
Here's my instructions for my 101 -> 201 move
2. Enlarge the 101 disk if not already 1000 cyl (non LVM)
# Allocate a 1000 cyl disk at address 201
vmcp link \* 201 201
chccwdev -e 201
# Lsdasd - get new disk letter
dasdfmt -f /dev/dasd? -b 4096
fdasd -a /dev/dasd?
mke2fs -j -b 4096 /dev/dasd?1
mount /dev/dasd?1 /mnt
cd /mnt
rsync -lPprvtaxS / .
cd /
for fs in dev proc sys; do mount --bind /$fs /mnt/$fs; done
chroot /mnt
mount -a
zipl
exit
# Edit directory entry and switch the 101 and 201 disks
-----Original Message-----
From: Linux on 390 Port <[email protected]> On Behalf Of Csaba Polgar
Sent: Thursday, September 12, 2019 8:06 AM
To: [email protected]
Subject: [LINUX-390] Replacement the root disk with a larger disk (without LVM)
Hello,
We have many system with SLES 11 SP4, and would like to upgrade these to
SLES 12 SP4.
The the root filesystem (/, on dasd 201, with ext3, and without LVM, simple
dasd) has the OS (itself the Linux, without the applications).
But this root filesystem is too small for the upgrade. So, I did the
following steps;
- I requested a new and larger disk (on 209 address)
- after the shutdown, I formatted the new disk (209) as ext3 (from another
Linux system)
- copied the full content from the small disk (201) to the larger disk
(209, with "rsync -avxHAX --progress /sourcepath/ /targetpath/" command,
with the other Linux)
- I changed the addresses of the disks in the Guest definition:
from 201 -> to 1201
from 209 -> to 201
- And I started the new guests, but the boot failed.
After it I compared the successful and unsuccessful boot logs, and I think
the below lines show the root cause of the fail;
in the successful log:
dasdb:VOL1/ LBX201: dasdb1
in the unsuccessful log:
dasdb:VOL1/ LBX209: dasdb1
In the unsuccessful log show, the 209 dsk address, but I use the new 201
dasd, and the 209 should not be important for the boot.
Somebody knows, what should be changed/updated for the usage of larger and
replaced root disk ?
FYI, the last error messages:
devtmpfs: error mounting -2
Freeing unused kernel memory: 396k freed
Kernel panic - not syncing: No init found. Try passing init= option to
kernel.
See Linux Documentation/init.txt for guidance.
CPU: 0 Not tainted 3.0.101-108.87.1.tux4vm-default #1
Process swapper (pid: 1, task: 0000000007d82038, ksp: 0000000007d87700)
0000000000000000 0000000007d87d68 0000000000000002 0000000000000000
0000000007d87e08 0000000007d87d80 0000000007d87d80 000000000062a032
0000000000000011 0000000000000000 0000000000000000 0000000000000000
000000000000000d 0000000000000000 0000000007d87dd0 000000000000000e
000000000063a978 0000000000100ac4 0000000007d87d68 0000000007d87db0
Call Trace:
([<00000000001009ca>] show_trace+0xe6/0x138)
[<0000000000629d80>] panic+0xcc/0x288
[<0000000000100300>] init_post+0x104/0x16c
[<000000000096b34c>] kernel_init+0x1fc/0x248
[<000000000062dfde>] kernel_thread_starter+0x6/0xc
[<000000000062dfd8>] kernel_thread_starter+0x0/0xc
HCPGIR450W CP entered; disabled wait PSW 00020001 80000000 00000000
001130E4
Regards / Mit freundlichen Grüßen / Üdvözlettel,
Csaba Polgar
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www2.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://www2.marist.edu/htbin/wlvindex?LINUX-390
