Page 1 of 1

WOW and System Crash (FIXED) With how I did it

PostPosted: Thu Apr 22, 2010 7:31 pm
by DarkSoul_DST
Was playing WOW its setup how Black Wolf explained how to do it.Been working good for the last 3 day till a crash 3 hours ago.What happened was I was at a vendor selling stuff when screen froze .Had no problems till today Im on live CD now .Need to know how I get an error report so I can see what happened.And how to access the hard drive to try nand fix.The computer tries to boot then all it says is grub loader error no numbers or anything.Thanks in advance for any help.Just want to get it back up and running.Im new to this so make fixes easy please.

Re: WOW and System Crash

PostPosted: Thu Apr 22, 2010 10:04 pm
by DarkSoul_DST
After a lot of looking and trying different things.Seems like there is a lot of ways to to it .The way I did it that worked is listed below.


METHOD 3 - CHROOT

This method of installation uses the chroot command to gain access to the broken system's files. Once the chroot command is issued, the LiveCD treats the broken system's / as its own. Commands run in a chroot environment will affect the broken systems filesystems and not those of the LiveCD.

1. Boot to the LiveCD Desktop (Ubuntu 9.10 or later).
2.

Open a terminal - Applications, Accessories, Terminal.
3. Determine your normal system partition - (the switch is a lowercase "L")

sudo fdisk -l
* If you aren't sure, run

df -Th. Look for the correct disk size and ext3 or ext4 format.
4. Mount your normal system partition:
* Substitute the correct partition: sda1, sdb5, etc.

sudo mount /dev/sdXX /mnt # Example: sudo mount /dev/sda1 /mnt
5.

Only if you have a separate boot partition:
* sdYY is the /boot partition designation (for example sdb3)
*

sudo mount /dev/sdYY /mnt/boot
6. Mount the critical virtual filesystems:

sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys
7. To ensure that only the grub utilities from the LiveCD get executed, mount /usr

sudo mount --bind /usr/ /mnt/usr
8. Chroot into your normal system device:

sudo chroot /mnt
9. If there is no /boot/grub/grub.cfg or it's not correct, create one using

update-grub
10. Reinstall GRUB 2:
*

Substitute the correct device - sda, sdb, etc. Do not specify a partition number.

grub-install /dev/sdX
11.

Verify the install (use the correct device, for example sda. Do not specify a partition): sudo grub-install --recheck /dev/sdX
12.

Exit chroot: CTRL-D on keyboard
13. Unmount virtual filesystems:

sudo umount /mnt/dev
sudo umount /mnt/proc
sudo umount /mnt/sys
* If you mounted a separate /boot partition:

sudo umount /mnt/boot
14. Unmount the LiveCD's /usr directory:

sudo umount /mnt/usr
15. Unmount last device:

sudo umount /mnt
16. Reboot.

sudo reboot

Post-Restoration Commands

Once the user can boot to a working system, try to determine why the system failed to boot. The following commands may prove useful in locating and/or fixing the problem.

*

To refresh the available devices and settings in /boot/grub/grub.cfg
o

sudo update-grub
To look for the bootloader location.
o

grub-probe -t device /boot/grub

To install GRUB 2 to the sdX partition's MBR (sda, sdb, etc.)
o

sudo grub-install /dev/sdX
To recheck the installation. (sda, sdb, etc.)
o

sudo grub-install --recheck /dev/sdX

Common Problem You May Have In Golf

PostPosted: Tue Sep 14, 2010 5:38 am
by Prande99
Common Problem You May Have In Golf

A second common problem is actually unhinging the wrists too early in an attempt for you to add energy for you to the swing with your golf equipment. Should you want for you to achieve a lot involving energy, your entire wrists and correct shoulder must wait their turn to produce their rate ishiner!