[Solved] Syslinux + GPT on SSD

Hello all,
I've been trying to install arch for the past 3 days without success. I have a thinkpad x230 with an M4 SSD on which I want to install the configuration stated in the title. I've managed to install Windows and LMDE on this disk in less than 30 min. But I don't want these.
So the steps I take are:
- Use gdisk to create the GUID partition. 'o' option, then two 'n' options to create the /boot (sdc1) - around 100mb-, and / (sdc2) -around 118GB- partitions. Both as Linux Filesystem.
- Format them with the ext4 filesystem.
- Mount sdc2 on /mnt and sdc1 on /mnt/boot
-Install the base base-devel filesystem.
- Generate fstab.
- Arch-chroot.
- Create an initial ramdisk environment (I skip all the language, locale and network config for now).
- pacman S syslinux. And edit the config file.
- sgdisk /dev/sdc1 --attributes=1:set:2 *here is where I think it fails
- dd bs=440 conv=notrunc count=1 if=/usr/lib/syslinux/gptmbr.bin of=/dev/sdc1
And then I reboot, and it won't boot syslinux at all. No idea what am I missing...
Edit: forgot to mention. The BIOS works both as UEFI or Legacy. THe first two days I tried the UEFI route without success, now I'm trying the normal BIOS option since it seems simpler.
Last edited by kemoryan (2012-08-16 01:13:01)

So the SSD is now in the first SATA slot? Great. Then it will show up as "/dev/sdb" from a LiveUSB and as "/dev/sda" when you're booting from the drive. Ok, so the boot flag and the MBR boot code are set. What about the files? Were they ever installed? Because I don't see any indication of it in the initial post. Maybe you just forgot. Pop in the Arch install media and run:
# mount /dev/sdb2 /mnt
# mount /dev/sdb1 /mnt/boot
# arch-chroot /mnt
# mkdir /boot/syslinux
# extlinux --install /boot/syslinux
This is congruent with the manual install, btw. Basically: files, legacy_boot flag and gptmbr.bin.
Screenshot from Parted Magic 2012.05.30:
If you're booting with BIOS compatibility you should definitely use this flag.
https://wiki.archlinux.org/index.php/GP … er_Support
Syslinux requires the /boot partition to be marked as "Legacy BIOS Bootable" GPT attribute (legacy_boot flag in GNU Parted) to identify the partition containing the syslinux boot files by its MBR boot code gptmbr.bin.

Similar Messages

Syslinux, GPT, RAID 0/1, LVM: Successfully boots, then hangs/crashes

I have a system with two hard drives that were initially zeroed-out (sda and sdb). I'm trying to do an Arch install with Syslinux, GPT partitioning, RAID1 (/boot and swap), and RAID0 (LVM for / and /home). I can get my install to boot successfully but after I enter my username (root) and password (hunter2) it's completely usable until it seems to hang (sometimes shifting the display) moments later.
Here's my best recreation of my installation steps. Hopefully you can tell me what I'm doing wrong or how I can troubleshoot further.
# Partitioning
gdisk /dev/sda
gdisk /dev/sdb
# I configure the partition table identically on sda and sdb:
# # Flags Type Size
# 1 Boot FD00 128 MB # /boot
# 2 FD00 2 GB # swap
# 3 FD00 Remaining space (~ 253 GB) # LVM for / and /home
# Load kernel modules
modprobe dm-mod
modprobe raid0
modprobe raid1
## RAID
mdadm --create /dev/md1 --level=1 --raid-devices=2 --metadata=1.0 /dev/sd[ab]1 # Create RAID1 for /boot
mdadm --create /dev/md2 --level=1 --raid-devices=2 /dev/sd[ab]2 # Create RAID1 for swap
mdadm --create /dev/md3 --level=0 --raid-devices=2 /dev/sd[ab]3 # Create RAID0 for LVM for / and /home
## LVM
pvcreate /dev/md3 # Initialize /dev/md3 for LVM
vgcreate VolGroup00 /dev/md3 # Create VolGroup00 VG
lvcreate -L 10G VolGroup00 -n lvroot # Create LV for /
lvcreate -L 10G VolGroup00 -n lvhome # Create LV for /home
# Formatting
mkfs.ext2 /dev/md1 # Create ext2 file system for /boot
mkswap /dev/md2 # Create swap device
mkfs.ext4 /dev/mapper/VolGroup00-lvroot # Create ext4 file system for /
mkfs.ext4 /dev/mapper/VolGroup00-lvhome # Create ext4 file system for /home
# Mount the partitions
mount /dev/mapper/VolGroup00-lvroot /mnt
mkdir /mnt/boot
mount /dev/md1 /mnt/boot
mkdir /mnt/home
mount /dev/mapper/VolGroup00-lvhome /mnt/home
# Connect to the internet (skip; DHCP worked)
# Install the base system
pacstrap /mnt base base-devel vim
# Install a bootloader
arch-chroot /mnt pacman -S syslinux
# Configure the system
genfstab -pU /mnt >> /mnt/etc/fstab
arch-chroot /mnt /bin/bash
echo swamp > /etc/hostname
ln -s /usr/share/zoneinfo/America/Chicago /etc/localtime
locale > /etc/locale.conf
# I fix a few minor things in /etc/locale.conf so they are all set like LC_ALL="en_US.UTF-8"
echo "KEYMAP=us" > /etc/vconsole.conf
# I uncomment en_US.UTF-8 UTF-8 in /etc/locale.gen
locale-gen
# I make these changes to /etc/mkinitcpio.conf:
# MODULES="ext2 ext4 raid0 raid1 dm_mod"
# HOOKS="base udev autodetect modconf block mdadm_udev lvm2 filesystems keyboard fsck shutdown"
mkinitcpio -p linux
syslinux-install_update -iam
# I change the APPEND lines in /boot/syslinux/syslinux.cfg from:
# APPEND root=/dev/sda3 ro
# ... to:
# APPEND root=/dev/mapper/VolGroup00-lvroot ro
# Unmount and reboot
exit
umount /mnt/boot
umount /mnt/home
umount /mnt
vgchange -an
mdadm --stop /dev/md3
mdadm --stop /dev/md2
mdadm --stop /dev/md1
reboot
Last edited by roknir (2013-02-20 04:50:18)

WonderWoofy wrote:Can you chroot and find out what is in the journal? You may not even have to chroot, as I think you can simply use the -D option.
Interesting. I didn't know about the systemd logging. I'm glad it's on by default. Here is the excerpt:
Feb 19 21:39:40 swamp systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
Feb 19 21:39:40 swamp systemd[1]: Starting Permit User Sessions...
Feb 19 21:39:40 swamp systemd[1]: Started Login Service.
Feb 19 21:39:40 swamp systemd[1]: Started Permit User Sessions.
Feb 19 21:39:40 swamp systemd[1]: Starting Getty on tty1...
Feb 19 21:39:40 swamp systemd[1]: Started Getty on tty1.
Feb 19 21:39:40 swamp systemd[1]: Starting Login Prompts.
Feb 19 21:39:40 swamp systemd[1]: Reached target Login Prompts.
Feb 19 21:39:40 swamp systemd[1]: Starting Multi-User.
Feb 19 21:39:40 swamp systemd[1]: Reached target Multi-User.
Feb 19 21:39:40 swamp systemd[1]: Starting Graphical Interface.
Feb 19 21:39:40 swamp systemd[1]: Reached target Graphical Interface.
Feb 19 21:39:40 swamp systemd[1]: Starting Update UTMP about System Runlevel Changes...
Feb 19 21:39:40 swamp systemd[1]: Started Update UTMP about System Runlevel Changes.
Feb 19 21:39:40 swamp systemd[1]: Startup finished in 1s 201ms 384us (kernel) + 1s 125ms 388us (userspace) = 2s 326ms 772us.
Feb 19 21:39:42 swamp login[357]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Feb 19 21:39:42 swamp systemd-logind[353]: New session 1 of user root.
Feb 19 21:39:43 swamp login[357]: ROOT LOGIN ON tty1
Feb 19 21:39:45 swamp kernel: usb 2-1.2.2: new full-speed USB device number 5 using ehci_hcd
Feb 19 21:39:45 swamp kernel: input: Logitech G9x Laser Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.2/2-1.2.2:1.0/in
Feb 19 21:39:45 swamp kernel: hid-generic 0003:046D:C066.0003: input,hidraw2: USB HID v1.11 Mouse [Logitech G9x Laser Mouse] on usb-000
Feb 19 21:39:45 swamp kernel: input: Logitech G9x Laser Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.2/2-1.2.2:1.1/in
Feb 19 21:39:45 swamp kernel: hid-generic 0003:046D:C066.0004: input,hiddev0,hidraw3: USB HID v1.11 Keyboard [Logitech G9x Laser Mouse]
Feb 19 21:39:56 swamp kernel: Console: switching to colour frame buffer device 128x48
Feb 19 21:39:56 swamp kernel: fb0: astdrmfb frame buffer device
Feb 19 21:39:56 swamp kernel: drm: registered panic notifier
Feb 19 21:39:56 swamp kernel: [drm] Initialized ast 0.1.0 20120228 for 0000:06:05.0 on minor 0
Feb 19 21:39:56 swamp kernel: nouveau ![ DEVICE][0000:01:00.0] unknown Kepler chipset
Feb 19 21:39:56 swamp kernel: nouveau E[ DEVICE][0000:01:00.0] unknown chipset, 0x0e6060a1
Feb 19 21:39:56 swamp kernel: nouveau E[ DRM] failed to create 0x80000080, -22
Feb 19 21:39:56 swamp kernel: nouveau: probe of 0000:01:00.0 failed with error -22
Feb 19 21:39:56 swamp systemd-udevd[217]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 19 21:39:56 swamp systemd-udevd[217]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 19 21:40:34 swamp systemd-logind[353]: Power key pressed.
Feb 19 21:40:34 swamp systemd-logind[353]: Powering Off...
Feb 19 21:40:34 swamp systemd-logind[353]: System is powering down.
Feb 19 21:40:34 swamp systemd[1]: Stopping Sound Card.
Feb 19 21:40:34 swamp systemd[1]: Stopped target Sound Card.
Feb 19 21:40:34 swamp systemd[1]: Stopping LVM2 metadata daemon...
I think these are the pertinent errors:
Feb 19 21:39:56 swamp kernel: nouveau ![ DEVICE][0000:01:00.0] unknown Kepler chipset
Feb 19 21:39:56 swamp kernel: nouveau E[ DEVICE][0000:01:00.0] unknown chipset, 0x0e6060a1
Feb 19 21:39:56 swamp kernel: nouveau E[ DRM] failed to create 0x80000080, -22
Feb 19 21:39:56 swamp kernel: nouveau: probe of 0000:01:00.0 failed with error -22
Feb 19 21:39:56 swamp systemd-udevd[217]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 19 21:39:56 swamp systemd-udevd[217]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Where do I go from there?

[SOLVED] Trouble installing on SSD with GPT partitioning

Hi there!
I'm trying to install Arch on my brandnew SSD. As per the wiki, I've set the SSD up to use GPT partitioning. I've created a first 1MB partition of type BIOS boot partition, and in the mobo's BIOS I've set the SATA controllers to AHCI mode. I've manually created an ext4 filesystem on the 2nd partition before running arch's installer. In the installer, I chose not to install a boot loader, cause this is said to install GRUB, while GPT partitioning requires GRUB2. So, after installation, I've chrooted into the installation, cause there doesn't seem to be any other way to get GRUB2 installed. I've pacman -Sy'd grub2 and left the chroot. I've tried to run
grub-install --recheck --no-floppy --root-directory=/mnt /dev/sda
, but got
Probing devices to guess BIOS drives. This may take some time.
The file /mnt/boot/grub/stage1 not read correctly
What's the matter? How am I supposed to get a working boot loader onto my new SSD?
Best wishes,
Rufus
Last edited by RufusD (2010-12-19 17:07:21)

Check whether grub-install belongs to grub package or grub2 package. Try to install these updated grub2 packages from here
http://dl.dropbox.com/u/9710721/skodabe … pkg.tar.xz - for x86_64
http://dl.dropbox.com/u/9710721/skodabe … pkg.tar.xz - for i686
http://dl.dropbox.com/u/9710721/skodabe … pkg.tar.xz - any arch
and then follow the post_install instructions from grub2-bios package.
You might have to 'bind' mount /dev into your <chroot>/dev though or install the above packages and install grub2 from outside the chroot.
Last edited by skodabenz (2010-12-13 13:32:51)

Solaris 11.2 x86 installation problem on GPT partitioned SSD

I recently bought a new computer with Windows 8.1 pre-installed on it. I want to install Solaris 11.2 as dual-boot together with the pre-installed windows 8.1.
The computer has a 128 GB SSD which is GPT partitioned. The SSD has 5 GPT partitions which are in use. I used a partition manager in Windows to shrink the size of the 5th partition (the windows system partition) so that i now have about 31 GB of unpartitioned, unused space after the 5 used partitions where i want to install Solaris into.
For installation, I downloaded the Solaris text installer ISO and burned it onto a CD-R. Now, whenever the installation menu shows me the GPT partitions of my SSD and i choose "Use a GPT partition of the disk" it always goes back to the first menu screen where it says "Welcome to the Oracle Solaris installtion menu".
Also, the installation menu shows the 5 used GPT partitions correctly, but then it shows me not one, but two partitions as "unused" with a size of 0.0 MB.
What am i doing wrong?

If you have support, then you will be better served by opening a support case.
Assuming you don't, or you would have gone there already... There may well be bugs with supporting multiple OS's under GPT partitions. I have no idea how much testing we did for such cases, and to be totally honest we put little effort into dual-booting systems these days, as using VM's in VIrtualBox or other VM managers is a better answer for 90i+% of people.
That said, posting the output from prtvtoc for the disk would give someone a chance to see if there's an obvious bug.

[SOLVED] Syslinux : Missing OS

Hello
On booting, Syslinux show me this error message : `Missing OS`
After, the BIOS displays its `Operating System not found` error message.
Syslinux is is properly installed (MBR right, /boot (/dev/sda1) is flagged bootable, with Syslinux on it, all this tested with HDT).
I have NOT a GPT :
# fdisk -l
Disk /dev/sda: 60.0 GB, 60022480896 bytes, 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 * 63 64259 32098+ 83 Linux
/dev/sda2 64260 3968054 1951897+ 82 Linux swap / Solaris
/dev/sda3 3968055 117231407 56631676+ 83 Linux
Disk /dev/mapper/arch_root-image: 1490 MB, 1490026496 bytes, 2910208 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
`syslinux-install_update -im` worked well.
I have a Phoenix BIOS.
Thanks for your help
Last edited by xcodexif (2013-11-01 16:52:38)

Done, but nothing more.
Here is my syslinux.cfg
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 0 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda1 rw
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/sda1 rw
INITRD ../initramfs-linux-fallback.img
#LABEL windows
# MENU LABEL Windows
# COM32 chain.c32
# APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL poweroff
MENU LABEL Poweroff
COM32 poweroff.c32

[SOLVED] Syslinux, how to change colors?

I have successfully installed syslinux, however I would like to change its colors, especially the background color and I like it black.
I have already visited the syslinux wiki and off course the arch's wiki and I have a proper syslinux.cfg, but the "MENU COLOR screen 30;40 #ffffffff #ffffffff none" option does not change the background to black.
Am I doing anything wrong?
EDIT: I marked this solved because my problem was this white block and now I fixed by just appending a vga=current in the kernel line.
Last edited by twilight0 (2011-10-31 23:45:43)

Sorry for the delay, I was pretty occupied earlier this week.
I tested your setting by changing UI to menu.c32 and replace my MENU section with the one you gave me.
Haven't tried the resolution you have so changed MENU VSHIFT to 10 and removed MENU HSHIFT still a bit
"off the screen" with the menu but I get a black background behind the blue menu.
I'm running syslinux-git from aur: http://aur.archlinux.org/packages.php?ID=44890

[SOLVED]SYSLINUX - dual bot arch and gento - fail

Hi
I am experimenting with gentoo (well not just yet and i can not boot the gentoo kernel. Gentoo is on partition /dev/sda6 and doesn't have a boot flag. Partitinon /dev/sda1 has a boot flag. I don't have a separate boot partition. Gentoo kernel was compiled with genkernel. When i choose gentoo from syslinux menu nothing happens. Menu just refreshes. If i press ESC and write down gentoo then it complains about not finding image ...
I didn't install syslinux on gentoo.
Here is my syslinux.cfg:
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=UUID=9f8eadcf-69e5-4786-869c-94cafcfff567 ro
INITRD ../initramfs-linux.img
LABEL gentoo
MENU LABEL gentoo
LINUX /boot/kernel-genkernel-x86-3.8.13-gentoo
APPEND root=UUID=9ea3ac89-3b72-458a-95fc-61095ea52cc4 ro
INITRD /boot/initramfs-genkernel-x86-3.8.13-gentoo
I have also followed arch wiki about chainloading and this is my syslinux.cfg from gentoo partition:
timeout 10
ui menu.c32
label gentoo
linux /boot/kernel-genkernel-x86-3.8.13-gentoo
initrd /boot/initramfs-genkernel-x86-3.8.13-gentoo
append root=UUID=9ea3ac89-3b72-458a-95fc-61095ea52cc4 ro quiet
label MAIN
com32 chain.c32
append hd0 0
EDIT:
SOLVED by this config changes:
syslinux.cfg on /dev/sda1 (arch)
LABEL gentoo
MENU LABEL gentoo
COM32 chain.c32
APPEND hd0 6
syslinux.cfg on /dev/sda6 (gentoo):
TIMEOUT 10
UI menu.c32
LABEL gentoo
MENU LABEL gentoo
LINUX /boot/kernel-genkernel-x86-3.8.13-gentoo
INITRD /boot/initramfs-genkernel-x86-3.8.13-gentoo
APPEND root=UUID=9ea3ac89-3b72-458a-95fc-61095ea52cc4 ro quiet
LABEL MAIN
COM32 chain.c32
APPEND hd0 0
Any ideas?
Last edited by Shark (2013-06-16 19:37:45)

Sorry, I actually just fixed it on my own, it turns out my BIOS settings were a bit... weird. For some reason I didn't have my windows drive listed and it tried to boot a USB drive I had plugged into my computer. I just had to fix the drive order and it worked fine. Sorry about starting a fairly useless discussion.

[SOLVED] syslinux-install_update -a failed, err3

Hi folks
I've tried to install Archlinux. This works fine until where syslinux has to be installed. The installer cannot install syslinux cause it fails with: "Failde to set boot flag(s). syslinux-install_update -a failed with Error Code - 3"
Appropriate configuration and log files can be found here: http://sprunge.us/IZIh
Any idea why? Did I configure something wrong?
Before installing Arch I had Fedora with Grub2 installed.
Last edited by lasombra (2011-09-08 17:32:43)

I followed the arch installer and did a manual preparation of the disks. I had to do this with parted, as a GPT was detected. I did as follows:
sda1, boot, Primary, ext4 , 106.93 MB
sda2, , Primary, crypto_LUKS, 640000.82 MB
And I let some free space in the end of the disk as I've read, that this is used by the GPT. Then I followed the installer step by step and all went fine except the installation of the bootloader. I've exited the installer and as suggested, I've run
/mnt/usr/sbin/syslinux-install_update -i -c /mnt
by hand. this returns "Syslinux install successful".
Then running
syslinux-install_update -a
fails with "FAILED to Set boot flag on /dev/mapper/arch_root-image. Mhh ok, so I assume I have to do chroot on /mnt. Running the command again complains
Could not find /proc/self/mountinfo
Areu you running a kernel greater than 2.6.24?
Ok, back again with exit, and checking the options for syslinux-install_update
syslinux-install_update -m -c /mnt
returns
Installed MBR (/mnt/usr/lib/syslinux/gptmbr.bin) to /dev/sda
That seems better. So I reboot the machine but i get Missing OS
According http://www.syslinux.org/wiki/index.php/Common_Problems this problem can be overcome executing
sgdisk /dev/sda --attributes=1:set:2
but this returns
Invalid partition data!
I am getting frustrated!
Last edited by lasombra (2011-09-04 10:18:36)

[SOLVED] syslinux menu just keeps looping

The computer boots, the syslinux menu shows up, and selecting the Arch partition nothing happens. Syslinux counts down to zero and just keeps looping.
syslinux.cfg
DEFAULT arch
PROMPT 0 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=UUID=55f7071d-93b2-4b34-9119-d41bc3c33225 ro
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=UUID=55f7071d-93b2-4b34-9119-d41bc3c33225 ro
INITRD ../initramfs-linux-fallback.img
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL off
MENU LABEL Power Off
COMBOOT poweroff.com
Last edited by boast (2012-10-23 23:37:27)

If you solved it, it would be nice to post what you did for the benefit of others.

[SOLVED] Samsung 840 Evo SSD poor performance

I'm posting this as [SOLVED] just in case anyone else comes across this issue. This isn't a linux problem but it may affect linux users and the cause isn't obvious. Mods feel free to delete this topic but it may be useful for people searching in the future.
Samsung have identified a problem with this model of SSD which causes data access to become slower over time. They have released a "Performance restoration tool" that upgrades the firmware and restores the performance of the drive (essentially by re-writing the data to it).
The tool is available here: http://www.samsung.com/global/business/ … tAodanEAIg
As of today (27/10/2014) the tool is only for Windows but a linux version is due "At the end of October"

I thought I'd already posted my experience, but I guess it's better late than never. I tried to update with the bootable cd.iso but the update failed with an error saying something like "I AM AN ERROR" which I found to be quite amusing. Luckily the error happened before starting the update process so nothing was broken. Next up was the FreeDos method mentioned by Slizzered and everything worked just fine. So just to play safe, go with the bootable usb stick method which has been confirmed to be working.

Syslinux & GPT: no boot

I have followed the instructions on the wiki to install syslinux manually and configure it as such, for use with GPT. I received no errors in my configuration, including the 'dd' step. I verified that the boot flag was set and that the syslinux.cfg file contained the correct partition for root. I installed the bootloader to /dev/sda.
I also tried doing it the 'automatic' way (with compensation for GPT, I did install gptfdisk for both methods) with the bash script syslinux-install_update -iam. This also 'succeeded' but I still have no usable bootloader.
Someone please help me out, I have tried both methods multiple times and I still can not boot to my hard drive.
Laptop I'm installing on is a Lenovo IdeaPad Z575, uses BIOS but not EFI.
TIA.
- gdea73 -

syslinux-install_update -iam
will in fact fail at the second step (-a), which is setting the boot flag. Use
syslinux-install_update -im
instead and just set the Legacy BIOS Bootable bit yourself.
Edit, as it's nothing important:
DSpider wrote:msthev, it uses the gptfdisk package to set the boot flag. Edit "/usr/sbin/syslinux-install_update" and see for yourself.
Yes, but it will fail if gptfdisk it's not installed, which isn't impossible, since you can set the attribute using gdisk. I had a similarly looking problem and the solution was to omit -a.
Last edited by msthev (2012-10-26 16:23:41)

[Solved] Boot only from SSD

Hello
I have installed arch about 10 months ago (on a HP laptop), and the idea was like so:
- SSD - kernel, home, and stuff
- HDD - stuff (and some bindings)
I got it working,but if I remove the HDD, I can't boot. I get the message "no drives detected" (or something like that)
So I'd like to boot from the SSD only.
Both drives are GPT, ext4 partitions (no swap), see:
http://imgur.com/8C6UPGk
Any hints on what I can do to fix that?
Also, afaik I'm not using UEFI, i'll upload a pic of the bios in a minute.
EDIT:
http://imgur.com/lCsvBib
Thank you all.
Cheers.
EDIT-SOLUTION:
This is a Pavilion Ultrabook 14-b006sa
2 hard drives (ssd and hdd), they're united if they are under secure boot (if i'm not mistaken), but it CAN run only on SSD. It was a tricky thing, but got it working with Gummiboot, EFI. the partitionning scheme was not the best one for grub, so I settled with a 512 MiB space for FAT32, and do the thing.
Last edited by ubunchu (2014-02-20 15:34:11)

alphaniner wrote:
It's simply that the bios (computer) itself doesn't see the SSD drive alone. If the other HDD is present, no problems.
You're saying the SSD doesn't show up at all if the HDD isn't present? Are you sure about this? It's not a matter of having installed your bootloader on the HDD or something?
I have grub installed on the SSD. And yes, I just removed the HDD again, went into the boot menu, and I only had "boot from EFI file" and the live usb i inserted.
Neburski wrote:
ubunchu wrote:I got it working,but if I remove the HDD, I can't boot. I get the message "no drives detected" (or something like that)
Maybe a stupid question but are you sure that you don't have a hybrid drive (SSD + HDD) and thus when you disconnect the HDD you actually also disconnected the SSD?
I'm going of the fact that you seem to be using a laptop and to me it makes sense that laptops would be using a hybrid drive to preserve space.
Anyway in case I'm wrong. You should post the output that ANOKNUSA asked for.
I just re-checked, it's "boot device not found, please install an operating system on your hard disk. gard disk <3F0>
The SSD isn't being detected, so it might be a hybrid thing... Or maybe it's just a wrong partitioning for grub.
WonderWoofy wrote:
I am thinking that this is an mSATA SSD that the windows environment would have used as a cache for the HDD. If that is the case, there may be no way around it. I too have one of these mSATA slots, though I have never tried to boot with that as the only thing in the machine.
I think this may just be in the firmware design.
Edit: On second thought... if you aren't using that ~30GB ESP to boot the machine, are you sure that grub is actually installed to the SSD? If it is, then the machine should at least be able to get to the grub prompt I would think. Even then though, you still don't have anything on the SSD to get yourself any further, so I'm not entirely sure what the point of this excercise is.
When I got this laptop, it merged both HDD's into RAID.
It is installed on the SSD, I just re-checked from a live environment, mounted it, and /boot is there.
I'm quite sure there is a problem with the grub-mbr-gpt setup....
What info would be relevant to post?

[SOLVED] SysLinux Not Found on MacbookAir

Hello,
As you probably can guess from the title, I cannot get syslinux to be picked up by the bios on my Macbook Air. On boot-up Syslinux cannot be detected by the bios as at all.
I have installed arch on more computers then I can count but never on a macbook or a gpt disk so maybe it may have something to do with my partitioning or something.
Here is a screenshot of my partition layout:
https://dl.dropboxusercontent.com/u/116 … okDisk.png
I also installed syslinux by installing gptfdisk and then using the automatic installer and no errors occurred.
Any Suggestions?
Regards
DoctorZeus
Last edited by doctorzeus (2014-12-11 17:57:33)

ackt1c wrote:
Sorry I don't keep irc logs.
But you can toggle bootable devices in
cfdisk
Make sure to write.
Thanks for the reply but I tried before but it doesn't allow me to set any partitions on the drive as bootable as the option isn't even available (I assumed it was because it has a gpt disk)?
DoctorZeus
Last edited by doctorzeus (2014-12-09 17:15:05)

[solved] Best Practice for SSDs with crypto on it regarding TRIM

Hi,
I was doing some research on this matter but did not find too much information on that that's more useful than confusing.
The setup is the following: I have an SSD (Crucial, Marvell-Controller) with two partitions: a small one for /boot and a bigger one for the rest, which is a LUKS-Container. I left some unpartitioned space at the end of the SSD. I'd like to *not* enable TRIM on the LUKS-device for security purposes.
I was wondering now:
I read that TRIM does reduce the write amplification of garbage collection. But shouldn't the garbage collection do not write at all, but just erase cells with no information on it?
If TRIM helps keeping up performance: do I need to explicitly trim the unpartitioned space? Or does this area behave like the spare area?
If TRIM of the unpartitioned space is necessary: what's the most elegant way to do so?
If someone could shed a little light on this matter, that would help a lot and would be greatly appreciated.
Last edited by Ovion (2015-03-09 19:20:13)

I have the same setup. Crucial SSD, LUKS, TRIM (cron.weekly fstrim). A full hexdump (minus gigabytes of random data) looks like this: https://bpaste.net/raw/505157 (tell me about it)
There is no issue with security. At least, none I care about. So the attacker can see how much free space there is [and where]. The where part is important since lots of small files give a different picture [lots of small free spaces in between] than a single very large file would [no free space in between], assuming there is no fragmentation worth mentioning [which Linux filesystems are usually good at]. So an attacker could probably make some guesses about your amount of data and file sizes. On the other hand I don't see how that's important, in ecryptfs you get this kind of info for free, and I have all sorts of files in all sorts of sizes either way, so it's not a big secret.
The question is, when all it takes to crack your encryption setup is a keylogger or a $5 encryption wrench, does it really matter?
Don't use TRIM on your SSD if you don't want to (there are lots of reasons not to TRIM... like better data recovery chances if you delete something by accident). But don't fool yourself thinking it's somehow really important for your security...
As for unpartitioned space, if it ever was in use before, you need to trim it once. Create a partition on it, then blkdiscard the partition, then delete the partition. That way it's good until it's "in use" again because you dd all over it or had it resynced in a RAID.
Apart from that, TRIM does all the things you said (reduce write amplification, performance, etc. etc.) but it's not like the SSD can't take it if you're not writing 24/7 because it's a database server burning up or something.
Last edited by frostschutz (2015-03-09 19:19:16)

[SOLVED] Syslinux.cfg changes not taking effect

When I first switched from grub to syslinux, I discovered that my system won't boot properly without a nomodeset command in the boot line (actually I knew that; it was also in grub but I installed that 5 years ago and long since forgot). It worked great.
A few weeks later, I had some trouble with the virtual terminal after X started, and someone suggested adding vga={x} to the boot command. I did that, but as it turns out the one I picked wasn't supported by my graphics card/monitor: Whenever I boot, it says to press {enter} to choose from available modes.
I found one that worked well, and added it to syslinux.cfg, saved my work, and rebooted. It *still* complains about the previous mode and makes me choose a proper one. I have rechecked that my new value is in syslinux.cfg and rebooted countless times since then, and the new values just won't take.
Is there something else I need to do after editing syslinux.cfg? The man page and wiki page are extremely thorough on initial installation and configuration, but not so much on making later changes.
Last edited by WyoPBS (2013-05-15 17:18:15)

When I change label values in syslinux.cfg the new label appears, so I am 100% positive I'm editing the right file on the right partition.
However, I found the answer -- When the list of modes pops up and I key in 313, the boot console is reading that as 0x313. When I have "vga=313" in the cfg file, syslinux reads that as 313 decimal which is 0x139, an invalid mode. It just never occurred to me that the mode menu was presenting hex values... Just had to change it to vga=0x313 and all is well.

[Solved] Syslinux + GPT on SSD

Similar Messages

Maybe you are looking for