[magmagal]

Hi all,

I'm running F8 dual-boot with XP on a Dell Inspiron 6000. Yesterday, Fedora ran fine all day - no sign of problems. Last night I switched over to the Win side for a few hours, and then shut the computer down for the night. This morning, I tried to boot into Fedora, and it hung on "Enabling local filesystem quotas". Left it for an hour or so, nothing happened. Tried rebooting into both available kernels several times, same thing. Windows still boots fine.

I booted into text mode and found an error "getpwnam failed for roota" at "Enabling local filesystem quotas". I can't find any information on this problem and 'roota' seems very strange to me. Any ideas??

Thanks in advance for any help you can provide.

[magmagal]

*Bump*

Still haven't resolved this problem. A few more pieces of information.

1. If I change the entry for root in /etc/passwd to roota (after booting into the system with the rescue CD), I then get a message of "getpwnam failed for root" during bootup at the same point, and the same freeze.

2. Also, looking at lastlog shows only one entry. The full text of lastlog is below:

Username Port From Latest
root **Never logged in**

This strikes me as strange since I have certainly logged in as root and I usually login with another account on this machine (e.g., magmagal, which I still see a line for in the /etc/passwd file).

Is is possible that some file went corrupt? That I got hacked or got a virus somehow?? Any thought or suggestion would be appreciated.

[magmagal]

Well, I still have no idea what caused the problem, despite spending lots of time trying to figure it out, but I solved it. Running fsck manually and answering yes to all prompted changes solved whatever was wrong.

Here's what I did:

1. Boot from Rescue CD
2. Answer no to prompt about mounting the filesystem ('Skip')
3. At the command line, enter the following sequence of commands:
> lvm pvscan
> lvm vgscan
> lvm lvscan
> lvm -lvchange -ay /dev/VolGroup00/LogVol00 (using information from previous commands)

4. Run fsck and answer 'y' to all prompts:
> fsck /dev/VolGroup00/LogVol00

After fsck finished I rebooted and the system appears to be completely back to normal. There were lots of changes made by fsck, but I did not document them.