Custom Query (684 matches)
Results (253 - 255 of 684)
Ticket | Owner | Reporter | Resolution | Summary |
---|---|---|---|---|
#150 | fixed | Restore crashes during ext3 format of LVM | ||
Description |
Hardware: Dell PowerEdge 1855 (Blade server) OS: Fedora Core 5 (LVM based) Boot options: added "ramdisk_blocksize=1024" (fedora specific) All blades in teh chasis are exactly the same. After install on one blade, we imaged a DVD using the most recent Mondo. Using this DVD, we attempted to restore onto another of the blades. This crashed out after it started to format the LVM partitions it just created. This was first attempted on non-interractive. We then tried on interractive, then tried to mkfs.ext3 on the LVM partitions from expert mode. Each resulted in:
we could not get log files as it locked fully and needed reboot. Other errors were displayed on screen, but after about 30 seconds to 1 minute, the following was displayed:
If we can provide further information, please ask. Chris McLean |
|||
#153 | fixed | pre+post script & answer file | ||
Description |
The process of creating the restoration disks should offer the following capabilities:
|
|||
#154 | fixed | Troubleshooting with sh -x and Ubuntu, Replace == for stricter POSIX conformance with = | ||
Description |
Would be academic except for these circumstances -
Using sh -x /usr/sbin/mindi 2>&1 gives different results than mindi by itself.example: $ ./fragment TMPMODPROBE_FLAG=Y $ sh -x ./fragment 2>&1 + [ -d /etc/modprobe.d ] + cut -c1-3 + uname -r + [ 2.6 == 2.6 ] [: 1: ==: unexpected operator + echo TMPMODPROBE_FLAG=N TMPMODPROBE_FLAG=N (Yes, if one is observant one see the 'unexpected operator' message, but the script continues to run, so I was surprised by the result.) $ cat fragment #!/bin/bash # Test mindi fragment under debug - sh -x if [ -d "/etc/modprobe.d" ] && [ `uname -r | cut -c1-3` == "2.6" ] ; then echo TMPMODPROBE_FLAG="Y" else echo TMPMODPROBE_FLAG="N" fi If the == is changed to = then the result is - $ sh -x ./fragment 2>&1 + [ -d /etc/modprobe.d ] + uname -r + cut -c1-3 + [ 2.6 = 2.6 ] + echo TMPMODPROBE_FLAG=Y TMPMODPROBE_FLAG=Y Of course, this could be solved also by changing to - $ bash -x ./fragment 2>&1 + '[' -d /etc/modprobe.d ']' ++ uname -r ++ cut -c1-3 + '[' 2.6 == 2.6 ']' + echo TMPMODPROBE_FLAG=Y TMPMODPROBE_FLAG=Y So maybe the troubleshooting tip should have bash -x /usr/sbin/mindi 2>&1 ? Regards, Scott |