[SOLVED] Converted MBR- GPT: Gummiboot installation borked

I am converting an MBR installation to GPT, so I can dual-boot Win+Arch with Gummiboot.
After successfully changing the partitioning, I (1) set the BIOS to boot in EFI only; (2) booted from an arch EFI installation disk; (3) arch-chrooted in, mounted /boot to the Windows EFI partition, and installed Gummiboot. Gummiboot found the Windows EFI partition and installed correctly, I believe. I next followed the Beginners Guide and created the arch.conf and loader.conf files in the EFI partition.
When I try to boot into Arch, the bootloader reports
/vmlinuz-linux not found
or something similar.
I've clearly overlooked something along the way, but I'm not sure what. Thanks in advance for any suggestions!!
Last edited by hcra (2014-11-14 22:23:07)

Head_on_a_Stick wrote:Please post your arch.conf & loader.conf
#cat arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/sdc1 rw
# cat loader.conf
default arch
timeout 5
and the output of:
lsblk -f
sda
sda1 ntfs Recovery UUID#
sda2 vfat UUID#
sda3
sda4 ntfs UUID#
sda5 ntfs UUID#
sdc
sdc1 ext4 UUID#
sdc2 ext 4 UUID#
How did you go about converting your MBR disk to a GPT format?
I first used the Gparted (live CD) to shrink the initial and ending partitions of sdc slightly. (This may have been unnecessary.) Then, I used Rod Smith's gdisk, following the Wiki.

Similar Messages

Converting to GPT

Hello,
In a couple of days I'm going to upgrade my computer/motherboard to one with UEFI, and I thought I'd start with the preparations right now. I've think I've read up on most of it, but I'd like to make sure before I begin tinkering.
- I'd like to keep my current /boot, /, /home and (if possible) Windows partition.
- Since I'm going to try it out with BIOS at first, I'll have to configure without UEFI support for now.
Step 1
Create a 2 MiB non-formatted BIOS partition at the beginning of the drive, and set its flag "bios_grub"./*]
Create a ~200 MiB FAT32 EFI partition (for later use) after the BIOS partition.
Create a 2 MiB non-formatted partition at the end of the drive.
Run GPT fdisk to convert to GPT.
All this can be done without formatting any previous partitions (I have a 512 MiB /boot, so there's plenty of room to shrink/move).
Step 2
Boot up a Live CD and run grub-install (using grub2-bios), and grub-mkconfig.
Step 3 (When I have my UEFI computer)
Before removing HDD from my hold computer, install grub2-efi-x86_64. (So that I can bind mount and use it on Live CD)
Boot up using a Live CD, following wiki instructions in order to install to EFI partition. Run grub-mkconfig as well.
Last edited by Glaucous (2012-05-07 19:17:24)

Just wanted to add that Step 1-2 worked great so far (booting properly).

[Solved] Converting from BIOS+Grub1+MBR to UEFI+Grub2+GPT

Hello community,
my motherboard has an annoying bug, the POST sometimes taking over 20 seconds. Now I noticed that my motherboard is actually in the BIOS legacy mode, while UEFI mode is available. So I'd like to switch to UEFI in the hope that the BIOS bug won't appear there. I've read through several Wiki pages and forum posts, but still don't really know how to proceed.
The current setup is: The motherboard is in BIOS legacy mode, an HDD and an SSD are connected. The HDD contains just a big data partition while the SSD contains /, /home and swap. Grub1 is installed in the MBR of the SSD.
As far as I have understood from the Wiki, I need to change the partition table to GPT before switching to UEFI. According to https://wiki.archlinux.org/index.php/GP … MBR_to_GPT it is even possible without data loss. Since I need to free 1MiB at the end of the partition table, I'd need to boot some Live-USB and perform all the operations from there. So my first question is: If I change to GPT from Live-USB, will Grub1 still be able to boot the system afterwards?
Second thing is, I've noticed that Grub1 is neither present in the repos, nor in the AUR any more. So if I uninstall it and something goes wrong, how to get Grub1 back?
Thanks for any help,
Photon
Last edited by PhotonX (2013-03-01 12:09:16)

PhotonX wrote:my motherboard has an annoying bug, the POST sometimes taking over 20 seconds. Now I noticed that my motherboard is actually in the BIOS legacy mode, while UEFI mode is available. So I'd like to switch to UEFI in the hope that the BIOS bug won't appear there. I've read through several Wiki pages and forum posts, but still don't really know how to proceed.
Try a live-medium that starts in UEFI-mode. The easiest way would be using the latest Ubuntu. If you've switched your BIOS from legacy boot to UEFI first, Ubuntu should detect this and start in UEFI mode. So you could check if it solves your POST problem.
If you want to try it with the latest Arch-ISO just follow the wiki for creating a UEFI bootable usb device. After booting this device, check if it really has booted in UEFI-mode
PhotonX wrote:Second thing is, I've noticed that Grub1 is neither present in the repos, nor in the AUR any more. So if I uninstall it and something goes wrong, how to get Grub1 back?
You can't (unless you are using an old Mac) . If you want UEFI and Grub, use grub-efi-x86_64.

Macbook Pro 7.1 (mid 2010), nvidia blob,efi and hybrid mbr,gpt

I've recently reinstalled archlinux on named machine, and I'm currently at a loss regarding the nvidia-blob.
I'm dualbooting osx and arch, have refind installed to the ESP partition, and boot linux using efistub.
Out of the box, using nouveau, this just works.
Sadly, nouveau doesn't handle the nvidia 320m chip all that well, so I have tearing
and most problematically my system gets really hot quite fast.
So I installed the blob, rebooted, only to find that X/the blob crashes on startup of X.
Hunting around, I now know, that officially, nvidia doesn't support 'pure efi mode' with their drivers. But that info is quite old.
I've also read contradictory claims of the blob working in similar circumstances...
What is the status of this as of 27.04.2013 ?? Anybody with the mbp 7.1 out there?
Now, I've had archlinux with the blob working on this machine before, at the time though I guess I was booting in bios or csm mode,
as I was using syslinux (which was started by refit/refind).
I can't use syslinux again, because I use xfs as my root fs, and syslinux doesn't support it.
Also, as far as I've been able to figure out, the use of syslinux requires an mbr.
Now DiskUtil from osx created a hybrid-mbr for me, because I used it to repartition my disk, but as neither osx nor linux require this,
I would most gladly revert this and have just the gpt on my disk.
So do I need an mbr for syslinux/grub-legacy/other options? for booting into bios/csm-mode?
I fail to understand how exactly this works with apple machines.
Are there other things I could try, kernel args maybe?
I just don't know what to try next, any help greatly appreciated.
Last edited by hungerfish (2015-05-02 11:33:31)

CSM-mode works.
Eve if the "pure-efi" way won't be solved by the nvidia developer in a foreseeable future, the CSM-mode works very fine and that's good.
This would solve this thread HALFway, not fully but in a reasonable way.
But the cause is as clear as daylight, the Apple EFI is way too old (version 1.x), and it's API is somewhat different from the UEFI of nowadays (version 2.x). I went around and asked some fellow students who also have a Linux installed in pure EFI and they stated it works with their UEFI board on various other Laptops or PCs, with nvidia.
It's frustrating, but somehow I can't blame nvidia alone for this, now I also blame Apple for it's incompatibility in their old EFI. Something like a firmware update is out of question I afraid.. (okay, Intel based Macs are using EFI, not the Open Firmware by Power based PC of Apple)
== Short Howto to CMS ==
So, if anyone is interested in the way I do or would do, here some descriptions,
First, I made my system just like the one of Ubuntu (before I know about a separated BIOS partition). Yeah, some of you would think "no, that's no good", but that makes no harm to me, since I won't change anything on it after the installation anymore.
Well then, I have an EFI partition with 200MB, an MacOS partition with approximately 70GB and the rest with Linux.
I assume you have already partitioned your harddisk as you wish. In my case I reinstalled Arch after the following step one. Maybe you don't want to sacrifice your Arch installation, then try the following:
1. Remove the link to the EFI partition in the fstab by deleting the line with the EFI partition.
2. Delete the arch-grub or grub folder inside the EFI folder on the EFI partition. (any way is fine)
3. Do the "Step one" (hybrid MBR)
4. uninstall the efi-grub and install bios-grub
5. Do the "Step two" without installing Arch (write GRUB into partition)
I THINK this should do the same, but I'm not sure.
Whatever you do, be sure to make a complete backup of your system before you do this steps, because I won't be responsible for the mess, if something is going wrong. The steps I'll describe did it for me.
Step one, to have a hybrid MBR partition, you should start the system with an arch cd or USB and make a hybrid table with gdisk
# gdisk /dev/sda
Follow this Wiki from gdisk and you'll obtain your hybrid mbr. Now I'm going into detail.
Type from one to three GPT partition numbers, separated by spaces, to be
added to the hybrid MBR, in sequence: 2 3
I choose 2 and 3, because 2 is my MacOS partition and 3 Linux. No need more. You can even just do 3, as srs5694 said, it's only for us to enable BIOS-mode booting on the particular partition.
Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): y
Be sure to choose "yes", because if not, the EFI will be listed at last and the Macbook will have to search for it, which takes almost half a minute EVERY start.
Then it will ask you for every partition, which MBR code you want and if there should be a bootable flag to set. Choose the default MBR for all the partitions, but for the linux partition, set the bootflag with "y".
Unused partition space(s) found. Use one to protect more partitions? (Y/N):
Do as you want, I choosed "n" no, but that shouldn't be that relevant for a successful boot of the bios-grub.
After that, type "o" again to see, what it looks like, and with "w" you get a warning, if you really want to do this, which you actually want with "y".
With this, you should have a "clean" hybrid MBR.
Step two, now boot again with an Arch cd or USB.
If not already done this, follow the How do I install Arch on Mac? guide.
At the point of GRUB install boot files, you can choose between the way to install in on a separated BIOS-GRUB partition or on the linux partition. Of course it's not recommened, but it works, but well, do what you like.
For the chance you really want to install in into the partition as I did, don't be irritated by the error and warnings, as long as you can see this in the last line:
Installation finished. No error reported.
Then, even if it looks nasty, it's fine.
== Short Howto to nvidia and powersave stuffs ==
Well then, if you get here, then you did it (hopefully)!
You can start with installing your favourite Window Manager, mine was and still is XFCE. Pacman or Yaourt will ask you, which driver you want to install, like mesa, nvidia-304 or nvidia. Of course we choose nvidia.
Make sure you have the xorg-server and int utils installed, and xorg-server-devel, this prevents the "no screen found" error of nvidia.
Then it's done, your system should last about 30%-60% longer with batteries than with nouveau. I recommend you to stick with nvidia, because the nvidie-beta still drains too much batterie as I tested both of them.
For more power saving I suggest you have a look at Laptop, power saving.
For my part, I have powertop and the Laptop Mode Tools installed.
Since then, if I want to get the maximum power saving by reducing the brightness to one and let it idle for a while, I can see a consumption of ~7,4 W, that result for me in 6-7 hours batterie life. For normal work it'll last ~4 hours.
But it's important that the system won't heat up too much anymore. It's stays cool for the most time like now as I write this while listening to music and browse some website.
== Maybe some hints to correct errors ==
There are chances that GRUB won't find the /dev/sdaX by label or UUID, in this situation you have to redo the "hybrid MBR" step, then it should work again.
If this won't work, then you maybe did something wrong about fstab or the generating of grub.
Since I use nvidia (currently 313.something), the brightness steps to dim and lighten up is too wide. As we know the brightness do not rise in a linear manner, but it's exponential. That's the cause why the steps can be really large, if the brightness is near zero, but is small at almost full brightness. by the way, the power manager are making 10 steps for brightness.
The brightness panel doesn't work for me too, it'll crash if I want to add it to the xfce panel.
I had the problem, that 0 is too dark (obviously), but 10 is still to bright.
That's because there are still 8 steps betwee 0 and 10.
For this, just use xbacklight,
xbacklight -set <something between 1-100, 0 means black screen or just off>
For mor information, look for xbacklight, I made extra shortcuts, so that I can dim it in -+1 steps.
I heard, with xfce 4.12, this problem will be solved. So stay alert.
Hope this will help anyone out there and hopefully this doesn't miss the main topic of this thread (I afraid it does ^^")
Last edited by JohnWinkerbelt (2013-05-09 16:44:41)

Bootcamp vs rEFIt & rEFInd, mbr, gpt

I've been trying to install Windows 8.1 on Yosemite via Boot Camp Assistant, but got an error:
Windows cannot be installed to this disk. The selected disk has a mbr partition table, On EFI system window can only be installed to GPT disks.
After fighting with rEFIt and rEFInd to overcome the issue (which I then deleted by deleting its folders and its StartupItems file), I came across the instructions how to change the partition tables to GTP via gdisk. So I did that and voila - Windows let me to choose that partition for the installation. My joy lasted as long as the last step of Win setup process when I received an error saying the windows can't modify the boot information. It's now throwing me below error:
Recovery
Your PC needs to be repaired.
The Boot Configuration Data file is missing some required information:
File: \BCD
Error code: 0xc0000034
I've tried few command prompt solutions suggested by Microsoft, which didn't work, like
BCDboot x:\windows /s c: /l en-us
Bootrec /fixmbr
Bootrec /fixboot
Bootrec /scanos
Bootrec /rebuildbcd
The last two commands gave an error "Windows installations found: 0".
I'm lost at that point. There is cleary an issue with remainings of rEFIt / rEFInd, as my computer doesn't boot correctly - it throws an error "No bootable devices found". However, if I press an option key during chime it allows me to pick my OS X SSD, which is now called EFI Boot instead of it's name (EVO SSD).
How can I bring the boot back to normal? Could that be an issue when trying to install Windows?

Yes, I did use EFI boot. Also, what I meant earlier on is that I have created a fresh protective MBR on that disk using gdisk.
Here is the output:
[quote]
Disk: /dev/disk0 geometry: 30401/255/63 [488397168 sectors]
Signature: 0xAA55
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
1: EE 1023 254 63 - 1023 254 63 [         1 - 488397167] <Unknown ID>
2: 00    0   0   0 -    0   0   0 [         0 -          0] unused
3: 00    0   0   0 -    0   0   0 [         0 -          0] unused
4: 00    0   0   0 -    0   0   0 [         0 -          0] unused
[/quote]

New iMac - 10.8.3 - Windows 8 - Bootcamp error EFI - MBR - GPT - Bios won't let me select Bootcamp partition

iMac late 2012 - Bought - Updated 10.8.3
W8 ISO downloaded (tried with 2) > Bootcamp > USB Booteable created
Bootcamp > Install Windows7 (8) > Partition disk (gave W8 75gb), all fine. After it's ready the iMac restarts.
It restarts and remains in a black screen. I have to force power off, restart manually.
Holding 'Alt' I DO GET into the booteable menu:
I see:
[Macintosh HD]
[Windows]
[EFI Boot]
If I select [Windows] I get to that same black screen I initially got before by bootcamp assistant
BUT WHEN I SELECT [Efi] I DO GET THE WINDOWS 8 INSTALLATOR!!
From there, all fine, language selection > Next > Serial Key > Next... BUT WHEN THE PARTITION/DRIVE INSTALLATION WINDOW SHOWS UP
IT WONT LET ME SELECT THE BOOTCAMP PARTITION
"The selected disk has a MBR partition table. On EFI sistems, Windows can only be installed on GPT disks"
"You can't install Windows in this disk. It is possible that the Hardware is not able to boot in this disk. Make sure he dis controller is able in the system BIOS"
I try from there to FORMAT THE DRIVE (it gives you a chance) But still theres NO WAY I CAN GO "NEXT" in the next installation step.
It has been 3 days trying and trying, PLEASE HELP BOOTCAMP GURUS!

From my experience last week installing Windows 8 on a 15" MacBook Pro (Mid 2010).using 10.8.3 OSX.
I used BootCamp Assistant to partition the OSX drive.
I have a Full Version Windows 8 x64 DVD and inserted that into the Internal DVD of the MBPro on reboot after BootCamp was finished.
I restarted and got nothing but a Black Screen.
I powered off and restarted using the Option Key.
Three Icons appeared MacintoshHD, Windows DVD Icon, and EFI Boot
I thought the DVD might be FU'd so I tried EFI Boot which did nothing.
Before burning another Windows 8 DVD I tried to hook up my LaCie FireWire external DVD with the Win 8 Install DVD inserted.
Again nothing.
So I removed the Win 8 Install DVD from the external La Cie and inserted it back into the Internal MBPro DVD.
Did a Power Off Reboot with the Option Key depressed at the chime.
Again the three icon choices.
This time selected the Windows DVD Icon and got a Black Screen agian.
BUT THIS TIME I JUST PATIENTLY WAITED!
After about 20 minutes the Windows 8 Installation Process started and I got to Install everything to the new BootCamp Partition.
I had to format the BOOTCAMP Partition to NTFS using the advanced option and had to choose NEW installaltion NOT UPGRADE.
Windows 8 installed perfectly and I installed the drivers after installation completed from the Internal DVD from another DVD I had burnt with just the Windows 8 Support Software..
I was surprised that that the MBPro took so long to recognize the Internal Win 8 Installation DVD but it did eventually recognize it and installed flawlessly.
Try the PATIENT approach and let us know if we may have found a clue here.
BTW I used System Recovery Boot Disk Utility to both Repair Hard Drive and Repair Permissions before attempting any of the above and also made a Full Time Machine Backup.
Better Safe than wiping your drive.

[SOLVED] Black Screen in new Installation (Intel GMA 3650)

Hi everybody,
I installed Arch on my new DN2800MT system using the Archboot installer (2012.04-2) for UEFI boot support. GRUB2 is running fine after all. The only problem is, that the screen turns black/completely off during the boot process. The installation seems to work in principle: if I wait a while, log in and type "shutdown -h now" or "reboot" the system shuts down or reboots. Just the output seems to be broken.
A video can be found on YouTube. A screenshot immediately before it turns black:
The last lines are
:: Waiting for UDev uevents to be processed
[ 6.444167] gma500 0000:00:02.0: GPU: power management timed out.
Interestingly the boot of the Archboot DVD also starts with the screen turning black. Some time later the the boot process seems to fix the issue at hand: the screen comes back alive. I also posted a video of that process on YouTube. The messages on the screen when it turns back on:
This behavior of Archboot indicates that this problem can be solved somehow. I would appreciate every hint on what's wrong a lot. For modification of the installed system I can boot Archboot, mount the installation and chroot into it.
Thanks a lot guys!
Alphasix
Last edited by alphasix (2012-06-25 21:43:00)

alphasix wrote:
Yeah you're right: it's totally hopeless. I now basically have two options: using an old AIF to install an older version of arch with a local repo, kernel <= 2.6.37 and Xorg <= 1.9 to get the old Intel poulsbo driver running or using Windows 7. I think the latter is the better choice.
There is only one very faint hope for a crazy solution: in the dependencies of the old pulsbo driver itself the kernel version isn't mentioned. What do you think of the idea of using the new gma500_gfx module with fbdev for xorg and the old binary driver just for VAAPI? VAAPI is in principle independent of xorg. So in theory this works, right?
[EDIT] This crazy idea has one flaw: the old drivers are i686-only (because of the binary blobs). At that time all systems with poulsbo graphics controller were 32-bit so that is reasonable. I impudently asked Intel support for the two binary blobs compiled for 64-bit. I mean: they sell a fully integrated system incompatible with their own binary driver for linux. Let's wait for the answer. If they turn me down, it means bye-bye to Linux .
I just received (today) a CedarTrail Netbook (Atom N2800) and discovered with horror that the graphic chipset is not supported. Please let me know if Intel will give you an answer since I was thinking of directly contact them too.
Btw, how did you contact them, can you give me a mail/website/other?
Thanks

Windows 8 install problem MBR-GPT

So I wanted ti install windows 8 by using bootcamp. I have an iMac mid 2011 21,5'' and Lion. Everything goes ok until I have to pick the disk I want to instal windows. I get the message "Windows cannot be installed to this disk. The selected disk has an MBR partition table. Pn EFI systems Windows can only be installed to GPT disks. Windows cannot be installed to this disk. This computer's hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer's BIOS menu" If I try to erase the disk and format it from windows setup I get an error. If I just reformat it I still get the above message abou GPT
Here's a screenshot.... PLEASE HELP ME!!!!

yours sounds like it has two disk drives present and that is why.
details details - one drive for OS X and Windows partitions works / one drive for Windows only and you have to pull the other.
Anyone with a Mac Pro with 4 hard drives knows, but is very easy to slide out and remove drive trays, to only have one drive present - the one where Windows will be installed.
You can unplug a drive. You can backup and format a drive to MBR w/ FAT while you install on another.
Windows 8 does support UEFI, and EFI requires GPT, but not have Apple and OS X on another drive, and Apple EFI is proprietary variant.

[SOLVED] Unable to boot Arch installer

Hello everyone.
I am no experienced Linux user (I'm just about one year and a half), but I think that dealing with things is the way to learn about them. I'm using Debian and want to switch to Arch.
I have an USB drive, and would like to put the installer (sorry? I'm not sure if that's the correct name. Please excuse me if I am not too concise) on it, without using a CD. I also have an Internet connection through ethernet, and I guess the "installer" will be able to use it to download any needed files.
So, as explained in the wiki and some external guides, I have copied the ISO I downloaded to the USB drive (with dd), just after formatting it as FAT32 with MBR.
I rebooted, with the USB plugged in, entered the BIOS menu and set the USB floppy as the first boot device. Then I exited from BIOS. I saw the LED of my pendrive flicking but no more, the BIOS stayed there (Press ESC to enter BIOS setup menu) and the light always flicking. (I waited about half an hour and nothing happened.)
I have tried it many times, and nothing has changed. I'm now a bit scared: is there anything wrong with my motherboard? Maybe with the filesystem on the external drive? I was wondering if there were any other choices to install Arch from within another Linux distro (Debian "Squeeze" in this case). I know nothing about chroot and other advanced techniques, but (if this helps) I don't want to save anything from my hard drive, i.e., I want a clean install.
Thank you, and, as I said, sorry if this question is very weird, or if I'm missing something important. I'm sure I've looked through many places in the web -too many, I guess; my eyes now hurt me. I'm also not very good at English so, sorry again.
P.S.: I have just tried with a CD-R burning the ISO with Brasero, and it didn't work. The same: freezing. I have UEFI disabled in my BIOS. I'm now wondering what's happening with my computer. It has about five years, and it looks like packed rubbish, but ...
Last edited by Kalrish (2013-03-02 18:46:23)

It sounds like you're mixing up the methods for creating the USB install media. You mention formatting with FAT32, that's from the Without overwriting the USB drive method. But you also mention copying the iso with dd, which is from the Overwrite the USB drive method.
You should follow one method or the other from the wiki only, and pay attention to the output for any errors. Then, if things go wrong again, you will be able to provide better detail.

[Solved] Pacman message after interrupted installation... persists

As you can see I'm still a bit of a newbie. Yesterday I was installing TeX live, but while installing someone unplugged a USB stick and all went stuck... it all just freeze the system, I guess it was a hardware problem. Anyway, I restarted and when I came back to resume the installation (downloading of packages was already finished), pacman sent me a lot of error messages, but apparently TeX live installed fine. Well, I checked my TeX system and works fine. The problem is every time I try to install something, I always get this error message:
error: could not open file /var/lib/pacman/local/texlive-bin-2010.1-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/texlive-bin-2010.1-4/depends: No such file or directory
How do I repair this? I didn't want to clean the cache, but... would this do fine? what else do I have to do?
Thanx in advance.
Last edited by joe74 (2010-10-23 22:33:20)

Well, solved by myself.
What I had to do after a lot of mess was
1. uninstall everything that was causing errors
sudo pacman -Rs texmaker texlive-most texlive-core texlive-bin
2. and clear the cache of files not installed
sudo pacman -Sc texmaker texlive-most texlive-core texlive-bin
This solved the entire problem. Dialectical theory still functioning in my brains

[SOLVED] Several problems after fresh installation

Hi guys,
i just did a fresh installation of arch and every times i must do something i get this error:
cannot remove, read, edit and etc : read-only file system
So i searched for a workaround.. but i must do this after every boot
This is it:
mount -oremount,rw /
There's a way to fix this forever?
Often when i need to edit some files, like /etc/pacman.conf or xorg config file, arch tell me: You do not have write permission to modify... that file
Searched another workaround.. and also this i must do every time after each boot:
sudo chown -R black /directory of file that i'm trying to edit/
I hope to fix this annoying problems, with your help.
Thanks guys,
Gabriele.
Last edited by Lilith (2012-09-28 13:18:46)

Ok guys,
think solved by change my /sda6/ (root) by /mnt to / and adding a slash / before home, boot, var.
Rebooted and try to edit the same file /etc/fstab and no warnings
Now is like this:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmps nodev,nosuid 0 0
#UUID=blablablabla
/dev/sda6 / ext4 rw,relatime 0 1
#UUID=blablabla
/dev/sda9 /home ext4 rw,relatime 0 2
#UUID=blablabla
/dev/sda5 /boot ext2 rw,relatime 0 2
#UUID=blablabla
/dev/sda7 /var reiserfs rw,relatime 0 2
#UUID=blablabla
/dev/sda8 none swap defaults 0 0
Thanks to everyone i also fixed my 2nd problem that i think is related to the first
Last edited by Lilith (2012-09-28 13:15:43)

[SOLVED]Booting into Arch after installation.

Good evening,
after getting a new harddrive (SSD) I've decidet to do a fresh install of Arch (it was already installed on the HDD I've used before).
The only difference made while installing is that I'm using a GPT-table and that I've configured grub for EFI.
After selecting Arch linux from the Grub menue I've get the message that there is a startup job running for sdb1, sdb2 and sdb3.
My Partition table:
gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 246162672 sectors, 117.4 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 6C1A58C8-7F1C-4E26-BD81-AB4BFB99F930
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 246162638
Partitions will be aligned on 2048-sector boundaries
Total free space is 2831 sectors (1.4 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 4196351 2.0 GiB EF00 Boot
2 4196352 239871182 112.4 GiB 8300 System
3 239872000 246162638 3.0 GiB 8200 Swap
and here my grub.cfg
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 13b889fb-a445-493a-afc7-2e342f381012
else
search --no-floppy --fs-uuid --set=root 13b889fb-a445-493a-afc7-2e342f381012
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=1366x768
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 14A9-1329
else
search --no-floppy --fs-uuid --set=root 14A9-1329
fi
insmod gfxmenu
loadfont ($root)/grub/themes/Duet/SegoeWP-20.pf2
loadfont ($root)/grub/themes/Duet/SegoeWP-22.pf2
loadfont ($root)/grub/themes/Duet/SegoeWP-24.pf2
insmod jpeg
insmod png
set theme=($root)/grub/themes/Duet/theme.txt
export theme
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-13b889fb-a445-493a-afc7-2e342f381012' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 14A9-1329
else
search --no-floppy --fs-uuid --set=root 14A9-1329
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=13b889fb-a445-493a-afc7-2e342f381012 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-13b889fb-a445-493a-afc7-2e342f381012' {
menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-13b889fb-a445-493a-afc7-2e342f381012' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 14A9-1329
else
search --no-floppy --fs-uuid --set=root 14A9-1329
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=13b889fb-a445-493a-afc7-2e342f381012 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-13b889fb-a445-493a-afc7-2e342f381012' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 14A9-1329
else
search --no-floppy --fs-uuid --set=root 14A9-1329
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=13b889fb-a445-493a-afc7-2e342f381012 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
I'm a bit confused because in one point of the wiki it says that the efi partition is the /boot partition and on another it says that it only has to be about 1M big (but a kernel is a lot bigger (especially because I want to create some custom kernel's)).
I'm sorry if someone already asked something similar but I didnt find anything.
Thank's for the support in advance ^^.
Last edited by theblackdog (2014-10-25 22:28:49)

Output of lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 117.4G 0 disk
├─sda1 8:1 0 2G 0 part /mnt/boot
├─sda2 8:2 0 112.4G 0 part /mnt
└─sda3 8:3 0 3G 0 part
sdb 8:16 0 7.5G 0 disk
├─sdb1 8:17 0 559M 0 part /run/archiso/bootmnt
└─sdb2 8:18 0 31M 0 part
sr0 11:0 1 1024M 0 rom
loop0 7:0 0 241.3M 1 loop /run/archiso/sfs/airootfs
loop1 7:1 0 32G 1 loop
└─arch_airootfs 254:0 0 32G 0 dm /
loop2 7:2 0 32G 0 loop
└─arch_airootfs 254:0 0 32G 0 dm /
Contents of /etc/fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=13b889fb-a445-493a-afc7-2e342f381012
/dev/sdb2 / ext4 rw,relatime,data=ordered 0 1
# UUID=f094290d-4114-4ba1-9afc-c96858ab99a6
/dev/sdb1 /boot ext4 rw,relatime,data=ordered 0 2
# UUID=bd37b9d2-865a-4b19-aee9-7ff14cc7f959
/dev/sdb3 none swap defaults 0 0
Let me guess my UUID's don't match?

[SOLVED] Archboot UEFI SSD+HDD Installation

Hi all,
This week I have installed Archlinux + Windows 7 x64 Prof. in UEFI-mode with the use of the latest Archboot.
I'm posting this to help others, and to check if everything is installed correctly.
THIS WILL ERASE YOUR DATA!! SO DO THIS AT YOUR OWN RISK! MAKE A BACKUP!
I'M NOT RESPONSIBLE FOR ANY DAMAGE OR PROBLEMS THAT CAN OCCUR!
READ THE INSTRUCTIONS BEFORE DOING THIS!
Specs:
ASUS P8H67M PRO v3.0
Intel i5-2400K
8GB DDR3
OCZ Vertex 2
Samsung Spinpoint F3 1TB
The steps I have done:
- Copied the Archboot iso contents to an USB-stick
- Boot from USB-stick with UEFI mode
- Use GPT as schema, create the partitions: (No 1M BIOS partition needed)
/dev/sda1 - 200M - Boot/EFI - code: ef00
/dev/sda2 - 4G - Swap
/dev/sda3 - 30G - /
/dev/sda4 - *G - Windows (if needed)
On the HDD I have created the partitions:
/dev/sdb1 - 12G - /var
/dev/sdb2 - 8G - /home
/dev/sdb3 - *G - data
- Format the created partitions:
/dev/sda1 - vfat - mount point: /boot/efi
/dev/sda2 - swap
/dev/sda3 - btrfs/ext4 - mount point: /
/dev/sdb1 - btrfs/ext4 - mount point: /var
/dev/sdb2 - btrfs/ext4 - mount point: /home
- Use as source Internet
- When asked for bootloader use grub2-efi-x86_64 or i386. (Depends on your architect)
- Reboot
- You should now have GRUB added in your Boot-list and can boot Arch *without any problems*.
- You can now install Windows, use the following guide.
- When installed Windows, you should have a new Boot-option Windows Boot Manager, switch back to GRUB to boot Arch again.
- You can switch between them, or add Windows to grub.cfg > check the grub2 wiki. - If this is not working, plugin your UEFI Windows usb-stick and choose startup-repair and try again.
Thanks.
Last edited by beta990 (2012-08-25 13:40:06)

Can someone please help me?
After the installation, and running (kernel) updates, I get the following errors on grub boot:
error: cannot read the Linux header.
error: you need to load the kernel first.
I cannot boot right now.
See my specs above + installation.
Help please...

Converting a local SAP installation into a domain SAP installation

Hello,
We plan to convert a local installed SAP system into a domain installed SAP system. Is it just enough to change the user from the services SAPOSCOL and SAP<SID>_nn from local to domain users? If not, what else do I have to do or do we have to do this by a system copy ;-( We use SAP ECC6.0 EHP4.
Thanks in advance
Peter

Hi,
Would also suggest to check this thread:
Change from local to domain installation
We have tried this approach and works fine - saved quite some time and effort. However if you want to go the safe way, please go for a system copy as Sunny suggested. Either way, I recommend a complete backup first
Regards,
Srikishan

[SOLVED]Keyboard not working at installation (so, I can't install)

Hello,
When I execute the installation program (from a CD or USB), keyboard works when the GRUB shows up, but when I press enter to run archiso, after the kernel and module loading, I arrive to "archiso login:_" screen with a non-working keyboard, neither my PS2 nor USB keyboard, so I can't login in and, of course, install arch.
I've been trying to collect some rare data from the kernel loading screen in order to ease finding a solution:
(after archiso kernel module loaded) -> ohci_hcd 0000:00:04.0: Unlink after no-IRQ? Controller is probably using the wrong IRQ.
(after setting clock) -> select() to /dev/rtc to wait for clock tick timed out.
As I said, I tried from a CD and a USB with the same result. I've md5 the images I'd downloaded and they are correct.
Greetings
Last edited by Davigetto (2009-09-10 18:47:41)

Please, is there any workaround to this problem? I would wish to install arch on my PC.
Maybe installing an older version CD could work, but i am not sure if older versions of arch offer support for ext4...
EDIT: Ok I solved it, it was a very strange option in Bios, called "Installer OS Select", where the options to choose were Windows or Others, and I choose others and voilà!, Keyboard working.
Strange, right?
Last edited by Davigetto (2009-09-10 18:48:46)

[SOLVED] Converted MBR- GPT: Gummiboot installation borked

Similar Messages

Maybe you are looking for