Tag Info

Hot answers tagged

12

You start at the beginning, square one. I'm sorry but you wiped everything, that's a brutal command. Not only did you wipe out the linux install, but you took the windows data with it. What you did didn't just wipe stuff in the partitions (/dev/sda1, 2, etc.), it wiped the partition table too because it matched /dev/sda which is the drive device itself. ...


9

Boot from a LiveCD, then mount the / harddrive partition. You can now chroot into your harddrive and just run passwd as root there changing the root pw. That's also the way to change to grub password.


8

First method: Ok, I booted up my UEFI box to check. First clue, near the top of dmesg. This shouldn't appear if you're booted via BIOS: [ 0.000000] efi: EFI v2.31 by American Megatrends [ 0.000000] efi: ACPI=0xd8769000 ACPI 2.0=0xd8769000 SMBIOS=0xd96d4a98 [ 0.000000] efi: mem00: type=6, attr=0x800000000000000f, ...


7

Check for currently-installed kernels: $ dpkg --get-selections | grep linux-image linux-image-2.6.38-2-686-bigmem install linux-image-2.6.32-5-686 install Check what current kernel you are running: $ uname --all Linux debian 2.6.38-2-686-bigmem #1 SMP Thu Apr 7 06:05:53 UTC 2011 i686 GNU/Linux Remove the kernel(s) you are ...


7

I had the same problem with my wireless keyboard (and running Puppy too, even if it's not related...) you have to enable in your BIOS USB Device Legacy Support. Find it in some submenu, for example Integrated Peripherals.


6

When Windows installs itself, it puts a bootloader (NTLDR in NT through XP; winboot after that) in the master boot record that reads boot.ini to show you the boot list. Once you pick something from that list, the bootloader's job is done, and the appropriate kernel is started from an actual partition on your drive. Grub does the same thing; the bootloader ...


6

The ultimate goal is to restore the Master Boot Record (MBR) to the hard drive, removing Grub, so you can boot to your Windows partition in the future without stopping at the Grub command line. The easiest way to achieve this is to boot from your Windows 7 installation media. Use the Repair computer link and choose Command Line. At the command line, enter ...


6

You can use grep on your MBR to figure out: sudo dd if=/dev/sda bs=512 count=1 2>&1 | grep GRUB sudo dd if=/dev/sda bs=512 count=1 2>&1 | grep LILO Only one of those should return a match. For more information and other ways to figure out, check this answer in askubuntu.


6

Here is the problem in your understanding: My understanding is that the bootloader GRUB2, is mounted to /boot. GRUB is not "mounted" on boot. GRUB is installed to /boot, and is loaded from code in the Master Boot Record. Here is a simplified overview of the modern boot process, assuming a GNU/Linux distribution with an MBR/BIOS (not GPT/UEFI): The ...


5

Here are some instructions on reinstalling grub2 in recent versions of Ubuntu. I'd recommend following the chroot method as I think that will be the easiest and safest way to restore your system. Additionally, the next time that you want to clean up drive space on /boot, you can use synaptic or apt-get to remove old kernels. For example: $ sudo ...


5

SysLinux/IsoLinux is a passable and popular choice for booting off El Torito-compliant optical media. But if your needs are somewhat non-standard, the most flexible solution is definitely GRUB (doesn't get more flexible than that without it being a full operating system). It's also the least easy to make an El Torito loader out of, but this may have changed ...


5

GRUB can't pass over the CD drive; this is something setup in BIOS. Either your Windows installation media isn't bootable for some reason or the laptop BIOS is set to try booting from the hard drive before the CD drive. When your laptop is first turned on a message will appear, something like "Press XXX to enter Setup", where XXX is some key sequence. Use ...


5

This uuid "EFc551-(...)" probably is your 2TB disk (namely encrypted PV on it). You need to tell somehow your initramfs about this second PV. Probably update-initramfs will do it, something like (from knoppix): (assuming you've mounted your disk in /mnt/disk) cp -a /dev/* /mnt/disk/dev/ chroot /mnt/disk mount /proc mount /sys update-initramfs -u ...


5

You can't boot Windows from a grub rescue prompt, unless the partition with the grub modules is available. That's why you get the unknown command error. Your best solution is to reinstall the Windows bootloader. To do this boot from a Windows 7 repair CD or the Windows Installation DVD to a repair prompt and run: bootrec /fixmbr If you don't have a ...


5

I'm assuming you're using GRUB2 as your bootloader. You can disable the timeout by opening the file /etc/default/grub and changing the value of GRUB_TIMEOUT: GRUB_TIMEOUT=-1 will disable the timeout feature. See here for more information and settings.


5

It depends on what kind of signature you're talking about. If you have an EFI system, you can have signed EFI executables (*.efi) and force your EFI firmware to only execute those with a known signature. This is known as Secure Boot. To check an EFI binary for a signature you can use the tool sbverify: $ sbverify --no-verify signed-binary.efi Signature ...


5

If the Ubuntu installation is still present (and only GRUB was lost), sure, you can use any distro that has live booting to do so. chroot into the Ubuntu installation and install and update Grub. If /dev/sda5 is the Ubuntu partition: mount /dev/sda5 /mnt mount -o bind /dev /mnt/dev mount -t proc none /mnt/proc mount -t sysfs none /mnt/sys mount -t devpts ...


4

There are only two versions of grub listed there, the 1x series (most recent being 0.97) and the 2x series (most recent being 1.99). Both can be customized and used for your purpose. The 1x series has more standard compatibility with old hardware and distros, but we the 2x series is coming along nicly and many major distros are switching to it. 32bit vs 64 ...


4

That password hash is salted. The salt is randomly generated and stored with the hash. The field delimiter between the salt and hash is the dollar sign ($). http://en.wikipedia.org/wiki/Salt_%28cryptography%29


4

In addition to what uther suggests, you can also attempt to boot Windows directly from GRUB. You're using GRUB 0.97 (i.e. Grub ‘legacy’), so try this: chainload (hd0,0)+1 This will boot the first sector (+1) of the first partition (,0) of the first HD (hd0). Your partition layout may be different. Press Tab once or twice after typing the opening ...


4

chainloader(hd0,0)+1 did the job.


4

You probably don't want to skip grub and boot direct to Windows - that will prevent you from booting into linux. Instead, you want to make Windows the default boot entry. The following works on debian (and derivatives like ubuntu). The procedure is conceptually similar but differs significantly in the details on RH/Centos and other distros. apt-get ...


4

You don't seem to have a separate home partition. /dev/sda3 is an extended partition (hence the "Étendue" in fdisk -l), you will not be able to mount it and it will not contain your /home. Unless you have a 2nd hard disk, it appears you deleted your /home partition while installing Windows. The only partitions in sda are the Windows one (sda1), what I ...


4

It sounds like your grub (the bootloader) config got messed up somehow. Try the following: Use your Mint CD to boot into a live system. Just as though you were going to install. Backup your existing configuration (just in case): cp /boot/grub/grub.cfg grub.cfg.old Open a terminal and mount your / (/dev/sdb2/ in your case) partition: mkdir tmp_root sudo ...


4

(I'm adapting this answer from http://unix.stackexchange.com/a/11431/73, because it happens to work the same even though the question is different) First you need to do some prep work in /boot/grub/grub.conf. Change default to saved. In every OS block, add savedefault 0, where 0 is the index of whichever kernel you want it to default to unless told ...


4

Did you update on your 2TB hdd the /etc/fstab to point to the correct UUID of the encrypt volume? In case you don't know what is the UUID of the encrypt volume you can check by issuing the cmd: cryptsetup -v status /dev/ After you need to update your /etc/fstab and the grub configuration to point to the correct UUID. This should solve your question ...


4

You can't change the current installation's header or footer. This is because those functions are inside the source code of Grub. What you can do is compile grub from source, which will give you access to the C files, where these functions exist. I will attempt to provide a guide on how to do this using something from a different SE. I am going to ...


4

If the order of your boot menu is important (and not just that Windows boots by default), and you don't have anything bootable besides Linux Mint and Windows (like OSX, BSD) you can do: cd /etc/grub.d mv 30_os-prober 09_os-prober as the alphabetical order of the files in /etc/grub.d, determines in what order they are processed. Then you run sudo ...


4

If you've booted using the UEFI firmware as opposed to using BIOS firmware then your system should make the EFI NVRAM variables available in: /sys/firmware/efi/vars/ or /sys/firmware/efi/efivars/ When booting using a BIOS (or the BIOS emulation mode of UEFI firmware) then these variables aren't available.


4

bootx64.efi doesn't get started first. Most of the time, it doesn't get started at all. The EFI firmware has its own "boot menu", analogous to the menu presented by GRUB but at an earlier stage in the boot process. Just as GRUB lets you choose which Linux kernel to run, the EFI boot menu lets you choose which EFI boot program to run — choices being things ...



Only top voted, non community-wiki answers of a minimum length are eligible