In article <200605290202.k4T22Hru010565@multics.mit.edu>,
Carl Alexander <xela@MIT.EDU> wrote:
>I've been around this circle twice in the past hour; I'd be glad
>to stop now.
>
>Old celeron machine I'm in the middle of preparing for a second
>life; currently has two old but lightly used HDs configured as a
>raid 1 with raidframe.  It lost parity due to a flakey cable on
>one disk; I rebuilt it with raidctl -R and all looked fine.  
>
>I rebooted it and booting hung with the message
>
>/lib/libedit.so.2: Undefined symbol "rl_completionWappend_character"
>(symnum = 190)
>
>I let it sit like that for about 20 minutes and hit the reset switch.
>It came back up with the RAID dirty:  wd1 had lost parity.  It repaired
>itself, and reported itself to be fine.  I rebooted, and it hung at that
>same error again.  (The complete output to the serial console from
>that reboot is below, under "Console Messages 1".)
>
>I then rebooted again (via the reset switch), and again the RAID
>came up dirty ("Console Messages 2", below).  The RAID proceeded
>to rebuild itself:  from a few minutes after the reboot:
>
>
>freshmeat:~# raidctl -v -s raid0
>Components:
>           /dev/wd0a: optimal
>           /dev/wd1a: optimal
>No spares.
>Component label for /dev/wd0a:
>   Row: 0, Column: 0, Num Rows: 1, Num Columns: 2
>   Version: 2, Serial Number: 2006051901, Mod Counter: 152
>   Clean: No, Status: 0
>   sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
>   Queue size: 100, blocksize: 512, numBlocks: 8448128
>   RAID Level: 1
>   Autoconfig: Yes
>   Root partition: Yes
>   Last configured as: raid0
>Component label for /dev/wd1a:
>   Row: 0, Column: 1, Num Rows: 1, Num Columns: 2
>   Version: 2, Serial Number: 2006051901, Mod Counter: 152
>   Clean: No, Status: 0
>   sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
>   Queue size: 100, blocksize: 512, numBlocks: 8448128
>   RAID Level: 1
>   Autoconfig: Yes
>   Root partition: Yes
>   Last configured as: raid0
>Parity status: DIRTY
>Reconstruction is 100% complete.
>Parity Re-write is 26% complete.
>Copyback is 100% complete.
>
>And appeared to finish just fine:  from abou a half-hour in:
>
>freshmeat:~# raidctl -v -s raid0
>Components:
>           /dev/wd0a: optimal
>           /dev/wd1a: optimal
>No spares.
>Component label for /dev/wd0a:
>   Row: 0, Column: 0, Num Rows: 1, Num Columns: 2
>   Version: 2, Serial Number: 2006051901, Mod Counter: 152
>   Clean: No, Status: 0
>   sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
>   Queue size: 100, blocksize: 512, numBlocks: 8448128
>   RAID Level: 1
>   Autoconfig: Yes
>   Root partition: Yes
>   Last configured as: raid0
>Component label for /dev/wd1a:
>   Row: 0, Column: 1, Num Rows: 1, Num Columns: 2
>   Version: 2, Serial Number: 2006051901, Mod Counter: 152
>   Clean: No, Status: 0
>   sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
>   Queue size: 100, blocksize: 512, numBlocks: 8448128
>   RAID Level: 1
>   Autoconfig: Yes
>   Root partition: Yes
>   Last configured as: raid0
>Parity status: clean
>Reconstruction is 100% complete.
>Parity Re-write is 100% complete.
>Copyback is 100% complete.
>
>
>So then I rebooted.  And once more around the loop.  (See
>"Console Messages 3", below.)  Then I hit the reset switch
>again, and it came up dirty and began rebuilding itself
>again.  Lather, rinse, repeat.
>
>If anyone has a clue what's going on here and how to stop it from
>happening over and over, I'd sure appreciate it.  I think it's
>extremely unlikely there's actually anything wrong with the
>disk at wd1.  But I suspect replacing it may make the problem
>disappear anyway, so if nobody has a better idea, that's what 
>I'm most likely going to try next.

sh is linked with libedit so you are getting stuck... Try booting with -a
and use /rescue/sh

christos