1 |
On Fri, Jan 26, 2007 at 07:30:56PM -0300, Mauro Maroni wrote: |
2 |
> I am not 100% sure but I believe udev had |
3 |
> been updated a couple of days before and the problem occured after that. |
4 |
> |
5 |
If you would like to confirm if udev did get upgraded, You can |
6 |
boot from CD, enter chroot (refer to the gentoo handbook, |
7 |
just don't do the fdisk or formats ;-) and emerge genlop. This is a |
8 |
great tool that reports on the emerge activity. From there you can type |
9 |
"genlop -l" and is will show you all the packages emerged and when. |
10 |
|
11 |
If you feel (or confirm) that the problem is related to udev, you may |
12 |
want to back down to the previous version you had installed. Hopefully |
13 |
it's still in the tree. If it's not, this is a good time to add the the |
14 |
--buildpkg option to EMERGE_DEFAULT_OPTS in /etc/make.conf, that way you |
15 |
will have binary packages for each package you emerge going forward, and |
16 |
can easily revert in case of emergency. |
17 |
|
18 |
> I also noticed that it only can see the root partition (in read-only |
19 |
> mode of course), but /boot (/dev/sda4) and /mnt/disk2 (/dev/sdb1) both |
20 |
> shows as if they were empty (ls shows nothing inside them) |
21 |
|
22 |
Can you see the other partitions when booting off the CD? Before you |
23 |
enter the chroot environment above, make sure you mount all your |
24 |
partitions as you did during the install. Hopefully you can see the data |
25 |
and the other partitions. If not it sounds like you have may have some |
26 |
drive corruption. |
27 |
|
28 |
Good luck! |
29 |
|
30 |
Brett |
31 |
-- |
32 |
gentoo-hppa@g.o mailing list |