| 1 |
On Tuesday 06 March 2007, Peter Alfredsen wrote: |
| 2 |
> On Tuesday 06 March 2007, Philip Webb wrote: |
| 3 |
> >Otherwise, my system is very stable & problem-free. |
| 4 |
> |
| 5 |
> I'm experiencing something similar at equally random intervals. |
| 6 |
|
| 7 |
Just for your information, I discovered what the problem was. My 2½ year old |
| 8 |
Maxtor hd decided to let out the magic smoke. On my next reboot (evoked by a |
| 9 |
freeze), I was told my system was unable to mount my hd. It seems a number of |
| 10 |
bad blocks had been forming on my hd for these past few months, just waiting |
| 11 |
to trap me between a rock and a hard place. Luckily, the bad blocks were |
| 12 |
contained to a single area of the hd. |
| 13 |
|
| 14 |
My method of recovery was straight-forward. I checked for bad blocks with |
| 15 |
badblocks, did a complete reiserfsck with --rebuild-tree and entered the hd |
| 16 |
and chrooted. Uhoh. /bin/bash segfault. I guess it's not called reiserfsck |
| 17 |
for nothing. A number of files had gotten little cutesie binary things |
| 18 |
embedded into them by reiserfsck, even though they weren't anywhere near the |
| 19 |
bad blocks. I had ordered a new hd by now and was waiting for it to arrive. I |
| 20 |
fixed the /bin/bash segfault by getting a quickpkg of the livecd bash. Gcc |
| 21 |
was fscked too. I downloaded a binpkg off tinderbox.gentoo.org. I did this |
| 22 |
until I had a fully functioning emerge system. |
| 23 |
|
| 24 |
I then did an emerge -e world to get the right files in place, with |
| 25 |
FEATURES="buildpkg", so I could use the binpkgs to get a working system with |
| 26 |
my new hd. I learned of a new portage location |
| 27 |
here: /var/cache/edb/dep/usr/portage/. emerge --metadata didn't work, |
| 28 |
segfaulting, and if I tried to emerge some things, it would complain of the |
| 29 |
missing "syake" dependency. This was fixed by |
| 30 |
deleting /var/cache/edb/dep/usr/portage/ and doing emerge --metadata. |
| 31 |
|
| 32 |
Yesterday morning, the emerge -e world had completed and I received my new hd |
| 33 |
later that day. Installing that was a comparative breeze. I just |
| 34 |
copied /etc/* to the new hd, emerged everything from binpkgs and was up and |
| 35 |
running. But when I emerged new stuff not from binpkgs, the configure would |
| 36 |
complain of the missing /usr/bin/as. Uhoh. It seems gcc doesn't create the |
| 37 |
necessary symlinks in /usr/bin automatically when emerging from binpkg |
| 38 |
(FIXME). I fixed this by installing the necessary symlinks from the bad hd. |
| 39 |
|
| 40 |
I am now in the process of a new emerge -e world, to get everything back in |
| 41 |
perfect order. |
| 42 |
|
| 43 |
/PA |
| 44 |
-- |
| 45 |
gentoo-user@g.o mailing list |
Archives