Hi,
I didn't get this right..
Have you got to the shell prompt after the crash?
If so, did you tried to run "fsck /dev/rwd0a"? Try it, it may show some
problems, or in the boot after the crash the system will show you what
partition have been compromised.
Just run the fsck /dev/rwd0X for all partitions, if there's many errors
and you wanna to take some risks, try "fsck -y /dev/rwd0a" or any other
dev, this will answer yes on all question on fsck, but be careful.Send more information so we can help you,
Regards,
ViniciusPeter_APIIT wrote:
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
| Nick Piggin | [patch] my mmu notifier sample driver |
| Sean | Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching |
| Arjan van de Ven | [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in |
git: | |
| Antonio Almeida | HTB accuracy for high speed |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| Jens Axboe | Re: [BUG] New Kernel Bugs |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
