Boot from floppy and install arch from flash stick - NO CDR - USB 1.1

MY PREVIOUS POST BELOW BECAME A HARD DRIVE INSTALL POST WHICH HAS HELPED THOUGH ISN'T ON SUBJECT CURRENTLY AND I STILL NEED SOLUTION  - Now at day 3 :-) - sorry!
I have old laptop with a very broken CDR... so just a floppy and a hard drive and 2 USB 1.1 ports.
[Need commands and which floppy is best]
The USB install WIKI
http://wiki.archlinux.org/index.php/Ins … _USB_stick
says to write the .img file to flash stick...
--- that I can do!
Though trying a similar process:
I've had no luck with a hard drive install (also on wiki) as I believe that once I write the .img file to the hard drive it WILL boot though can't create mount points as the drive's in use!
Anyways...
IF I have the flash stick with the .img file on it as per the wiki instructions
what commands would I use and what boot floppy would work for:
- booting from floppy
- mounting? the flash stick with arch core on it
- then installing from there to single hard drive partition.
thing is I'm just barely ok with using
dd   fdisk and mke2fs
So: I need to know what command to mount USB stick... then HOW do I get arch installer on the img file to boot up??
Any guru tips really needed ....thank you!
Last edited by yvonney (2009-01-28 08:44:59)

nice Kirurgs
doesn't boot from usb... and CDR very broken... good though as I've learned a lot....
dell inspiron 2500 1 ghz pentium III
method 1) used puppy after booting off wakepup2 floppy ....very handy that wakepup flopppy though be advised there's several versions of wakpup2 and try the second boot option on the aug or sept 2008 version it WILL find your USB device even if like me I had an old 128 meg one.  also, Crash, a guy at the puppy forums has a 3 floppy set that's specific to whatever puppy version you're running... try that as a last resort
UN-NECESSARY BLATHER COMMENT: The way those puppys are created weird me out., the more I looked around, Yes, I've read a wee bit about Aufs, and what goes into the whole persistent thing.... seems like lotsa almost impossible  to ever 'really' know stuff is going on it there.... Consider the source of that comment of course... I have huge blank spots in my knowledge and skill and am actually only a relentless year one linux'r... [not counting 6 years of hum and haw] though I'd wanna build my own live arch usb with tips from here before I ever tried to REALLY figure out what goes into creating puppy. I'm saying that at one or two points I thought.. hmnmm... perhaps puppy on this old laptop.... though concluded that ARCH for ALL things is really the only option. puppy's a great boot and hunt around thing though (for me, and in my current opinion).
method 2) eldamar and eldamar's guide which started me towards success .. which I basically now just do the dd command to an empty partition after booting from puppy .... THEN thrown in a supergrub floppy .... have it 'bring alive' the partition I've just dd'd the arch .img to.... and reboot.... oh, and from puppy I can create partitions as well.. gparted I think.
method 3) untested also can use plop floppy  it's a boot loader... you may be able to get slitaz distro to create one for you through the 'bootfloppybox' terminal command... not sure if it uses the old floppy linux version of PloP or the win version or what.... dunnno dunno!!! gotta go! :--)
crazy busy so writing to say... pretty much all fine! :--)
for me this move was 3-4 days of lots of WONDERFUL bad luck... with everything from puppy hell, my partial-dumbness and back..
thing is.... I'm real good at it now.... hehehehe
gotta love problems!
Last edited by yvonney (2009-02-03 17:27:56)

Similar Messages

  • 6500 booting from flash

    I need to boot my 6500 from external flash, and I put the command "boot system flash s72033-adventerprisek9_wan-mz.122-33.SXI13.bin" to set the boot variable. But still the switch is booting from flash sup-bootdisk: and also the boot variable is set to flash sup-bootdisk:  .  Can any one please tell me how to solve this issue
    this is the show run
    boot-start-marker
    boot system flash sup-bootdisk:s72033-ipservicesk9_wan-mz.122-33.SXH4.bin
    boot system flash s72033-adventerprisek9_wan-mz.122-33.SXI13.bin
    boot-end-marker
    and 
    Router#sho bootvar
    BOOT variable = sup-bootdisk:s72033-ipservicesk9_wan-mz.122-33.SXH4.bin,1;
    CONFIG_FILE variable does not exist
    BOOTLDR variable does not exist
    Configuration register is 0x2102

    Hello
    i would suggest to change the boot variable to contain both old and new iOS but have the new iOS try to boot first
    Conf t
    no boot system
    r
    boot system flash:s72033-adventerprisek9_wan-mz.122-33.SXI13.bin
    boot system flash sup-bootdisk:s72033-ipservicesk9_wan-mz.122-33.SXH4.bin
    Sh boot
    wr
    res
    paul

  • I have uninstalled and installed the latest Flash Player 17 many times.  I am currently working on a yearbook site that gets locked every time I try to add photos.  I have also received a plug in error even though the plug in box is checked.  I have a Mac

    I have uninstalled and installed the latest Flash Player 17 many times.  I am currently working on a yearbook site that gets locked every time I try to add photos.  I have also received a plug in error even though the plug in box is checked.  I have a MacBook Pro.  Please help!!!

    To give you any useful advice, I'm going to need to know more about your computer and browser:
    https://forums.adobe.com/message/5249945#5249945

  • [Solved] Boot process hangs for installed Arch and installation usb

    Hi. I've been using Arch Linux for around 6 months now and I'm in love with it. It is now my primary OS. However, I might have done something or performed some update, and I can no longer boot into Arch. The boot process hangs right before it should show the login screen (I'm using Gnome 3.6 with GDM). I see the following messages on the screen:
    Loading Linux core repo kernel ...
    Loading initial ramdisk ...
    /dev/sda3: recovering journal
    /dev/sda3: clean, 330610/1749664 files, 5585671/6996827 blocks
    And then it hangs right there. I have to hard-reboot after this.
    I then tried to boot using the Arch Linux Installation USB (archlinux-2012.12.01-dual.img), which also hangs at a particular point, before it should show me the prompt. I took a picture of the screen where it hangs: Screen Capture. This is an issue with just my laptop, because the USB boots just fine on another laptop I tried.
    I also have Windows 7 and Ubuntu 12.10 installed on my system, and I'm able to boot into both of them.
    I have 2 hard drives: /dev/sda is a 120GB SSD, and /dev/sdb is a 500GB hard disk. My partitions are as follows:
    sda1 - Windows 7 100MB System Reserved Partition (boot flag enabled)
    sda2 - Windows 7 OS
    sda3 - ArchLinux (boot flag enabled)
    sdb1 - Ubuntu 12.10 (boot flag enabled)
    sdb2 - Just data
    I ran bootinfoscript and below is the output:
    Boot Info Script 0.61 [1 April 2012]
    ============================= Boot Info Summary: ===============================
    => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
    the same hard drive for core.img. core.img is at this location and looks
    in partition 99 for .
    => Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 1 of
    the same hard drive for core.img. core.img is at this location and looks
    in partition 99 for .
    sda1: __________________________________________________________________________
    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files: /bootmgr /Boot/BCD
    sda2: __________________________________________________________________________
    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System: Windows 7
    Boot files: /Windows/System32/winload.exe
    sda3: __________________________________________________________________________
    File system: ext4
    Boot sector type: -
    Boot sector info:
    Mounting failed: mount: /dev/sda3 already mounted or sda3 busy
    sdb1: __________________________________________________________________________
    File system: ext4
    Boot sector type: -
    Boot sector info:
    Operating System: Ubuntu 12.10
    Boot files: /boot/grub/grub.cfg /etc/fstab
    sdb2: __________________________________________________________________________
    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files:
    ============================ Drive/Partition Info: =============================
    Drive: sda _____________________________________________________________________
    Disk /dev/sda: 120.0 GB, 120034123776 bytes
    255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    Partition Boot Start Sector End Sector # of Sectors Id System
    /dev/sda1 * 2,048 206,847 204,800 7 NTFS / exFAT / HPFS
    /dev/sda2 206,848 178,466,084 178,259,237 7 NTFS / exFAT / HPFS
    /dev/sda3 * 178,466,085 234,440,703 55,974,619 83 Linux
    Drive: sdb _____________________________________________________________________
    Disk /dev/sdb: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    Partition Boot Start Sector End Sector # of Sectors Id System
    /dev/sdb1 * 63 20,948,759 20,948,697 83 Linux
    /dev/sdb2 20,964,824 976,771,071 955,806,248 7 NTFS / exFAT / HPFS
    "blkid" output: ________________________________________________________________
    Device UUID TYPE LABEL
    /dev/mmcblk0p1 6665-3162 vfat
    /dev/sda1 CA6A20CC6A20B75B ntfs System Reserved
    /dev/sda2 1EE242D5E242B137 ntfs
    /dev/sda3 65db0c59-9f04-46f1-975d-8a4c28132137 ext4
    /dev/sdb1 bb9818db-ce7c-43a4-8ad5-8d3702001aed ext4
    /dev/sdb2 3C2E3A4E2E3A0206 ntfs
    ================================ Mount points: =================================
    Device Mount_Point Type Options
    /dev/mmcblk0p1 /media/dhaval/6665-3162 vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks2)
    /dev/sdb1 / ext4 (rw,errors=remount-ro)
    =========================== sdb1/boot/grub/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 ###
    if [ -s $prefix/grubenv ]; then
    set have_grubenv=true
    load_env
    fi
    set default="0"
    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 recordfail {
    set recordfail=1
    if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; 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_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    font="/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    set locale_dir=$prefix/locale
    set lang=en_US
    insmod gettext
    fi
    terminal_output gfxterm
    if [ "${recordfail}" = 1 ]; then
    set timeout=-1
    else
    set timeout=10
    fi
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/05_debian_theme ###
    set menu_color_normal=white/black
    set menu_color_highlight=black/light-gray
    if background_color 13,37,73; then
    clear
    fi
    ### END /etc/grub.d/05_debian_theme ###
    ### BEGIN /etc/grub.d/10_linux ###
    function gfxmode {
    set gfxpayload="${1}"
    if [ "${1}" = "keep" ]; then
    set vt_handoff=vt.handoff=7
    else
    set vt_handoff=
    fi
    if [ "${recordfail}" != 1 ]; then
    if [ -e ${prefix}/gfxblacklist.txt ]; then
    if hwmatch ${prefix}/gfxblacklist.txt 3; then
    if [ ${match} = 0 ]; then
    set linux_gfx_mode=keep
    else
    set linux_gfx_mode=text
    fi
    else
    set linux_gfx_mode=text
    fi
    else
    set linux_gfx_mode=keep
    fi
    else
    set linux_gfx_mode=text
    fi
    export linux_gfx_mode
    if [ "${linux_gfx_mode}" != "text" ]; then load_video; fi
    menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    recordfail
    gfxmode $linux_gfx_mode
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
    initrd /boot/initrd.img-3.5.0-21-generic
    submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    menuentry 'Ubuntu, with Linux 3.5.0-21-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.0-21-generic-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    recordfail
    gfxmode $linux_gfx_mode
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    echo 'Loading Linux 3.5.0-21-generic ...'
    linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-3.5.0-21-generic
    menuentry 'Ubuntu, with Linux 3.5.0-21-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.0-21-generic-recovery-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    recordfail
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    echo 'Loading Linux 3.5.0-21-generic ...'
    linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro recovery nomodeset
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-3.5.0-21-generic
    menuentry 'Ubuntu, with Linux 3.2.0-29-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.2.0-29-generic-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    recordfail
    gfxmode $linux_gfx_mode
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    echo 'Loading Linux 3.2.0-29-generic ...'
    linux /boot/vmlinuz-3.2.0-29-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-3.2.0-29-generic
    menuentry 'Ubuntu, with Linux 3.2.0-29-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.2.0-29-generic-recovery-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    recordfail
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    echo 'Loading Linux 3.2.0-29-generic ...'
    linux /boot/vmlinuz-3.2.0-29-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro recovery nomodeset
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-3.2.0-29-generic
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###
    ### BEGIN /etc/grub.d/20_memtest86+ ###
    menuentry "Memory test (memtest86+)" {
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    linux16 /boot/memtest86+.bin
    menuentry "Memory test (memtest86+, serial console 115200)" {
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    linux16 /boot/memtest86+.bin console=ttyS0,115200n8
    ### END /etc/grub.d/20_memtest86+ ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry 'Windows 7 (loader) (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-CA6A20CC6A20B75B' {
    insmod part_msdos
    insmod ntfs
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 CA6A20CC6A20B75B
    else
    search --no-floppy --fs-uuid --set=root CA6A20CC6A20B75B
    fi
    chainloader +1
    ### END /etc/grub.d/30_os-prober ###
    ### BEGIN /etc/grub.d/30_uefi-firmware ###
    ### END /etc/grub.d/30_uefi-firmware ###
    ### 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 ###
    =============================== sdb1/etc/fstab: ================================
    # /etc/fstab: static file system information.
    # Use 'blkid' to print the universally unique identifier for a
    # device; this may be used with UUID= as a more robust way to name devices
    # that works even if disks are added and removed. See fstab(5).
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc nodev,noexec,nosuid 0 0
    # / was on /dev/sdb1 during installation
    UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed / ext4 errors=remount-ro 0 1
    =================== sdb1: Location of files loaded by Grub: ====================
    GiB - GB File Fragment(s)
    4.564525127 = 4.901121536 boot/grub/grub.cfg 1
    5.130507946 = 5.508840960 boot/initrd.img-3.2.0-29-generic 2
    5.851592541 = 6.283099648 boot/initrd.img-3.5.0-21-generic 2
    6.317649364 = 6.783524352 boot/vmlinuz-3.2.0-29-generic 1
    4.965751171 = 5.331934720 boot/vmlinuz-3.5.0-21-generic 2
    5.851592541 = 6.283099648 initrd.img 2
    5.851592541 = 6.283099648 initrd.img.old 2
    4.965751171 = 5.331934720 vmlinuz 2
    4.965751171 = 5.331934720 vmlinuz.old 2
    I tried adding nomodeset and acpi=off to the boot parameters, but the boot process still hangs. Please let me know if I should provide any other information.
    Last edited by dhavalparmar (2012-12-30 11:45:25)

    Ok.. So my Arch Linux randomly decided to work. I'm sure I didn't do anything between my last "not working" state and my current "working" state. Below are a few things I tried:
    I thought of trying an earlier build of ArchLinux, and downloaded archlinux-2012.11.01-dual.iso and made a bootable USB out of it. It still hung.
    I was getting error messages during Arch boot that the last access time for the disks was at a future date. I found out that Ubuntu was using localtime instead of UTC and screwing up my hardware clock. I fixed it, and thought maybe the time issues were causing the boot problem. But fixing time didn't solve my problem.
    I chrooted into Arch from my Ubuntu install, ran 'sudo pacman -Syyu' and updated my Arch install.
    I thought maybe GDM isn't starting up. I re-enabled the service using 'systemctl enable gdm.service'.
    I removed OpenNTPd and installed NTPd. Enabled the daemon using 'systemctl enable ntpd'
    None of the above solved the problem, and rebooting to Arch still hung the system. So I stopped fiddling with it yesterday. Today, as usual, I just tried logging into Arch.. And it just worked out of the blue. The solution to me is as mysterious as the problem.
    I told this to my friend who introduced me to Arch, and this is what he said:
    Damn it computers, you were supposed to be deterministic!

  • Booting from hard disks 2TB - bootable USB flash drive GRUB (w/o OS)?

    Hi,
    I'm thinking about setting up a hardware supported RAID on a Debian-server (Proxmox) with lots of HDD-space. Therefore, my RAID-array will be >2TB, but I've read that the BIOS of the system will not be able to boot from such. Do you have a solution for this?
    I was thinking about installing a bootable GRUB on an USB flash drive, which would then chainload the RAID's GRUB for booting. Is this even possible? I couldn't find any tutorial on how to create/boot only a (customizable) GRUB from the flash drive.
    Another option would be to create multiple disks by the RAID-controller, but i'm not sure what happens with the chunks, if i would add another disk to the RAID to expand it.
    A third solution, that came to my head, is simply installing Proxmox on a separate disk and detach it from the RAID. But in case of a disk failure, it would not be protected and i would rely on snapshot-backups - so i rather would not like to go with that solution.
    Let me know what you think!
    VR

    I don't know about the answers to your issues, as I have never tried any disks that large.  But it would probably be wise not to mention that you are trying to do this on a non Arch system, as now I am pretty sure you will not recieve the help you desire.
    I don't mean to say that I encourage you to try to dupe our community into helping you with your debian system by not mentioning it.  But it seems pretty silly to come to the Arch threads looking for debian support, even if it is a universal (os independent) issue.

  • Boot from flash, then run Diskwarrior

       Every so often, I want to run Diskwarrior for directory repair – either for maintenance, or after a hard crash – on my 2011 MacBook Pro. Diskwarrior falls out of date everytime Apple updates the OS. I'm currently running Lion. I downloaded the free updater to 4.4, (I have a 4.2) but it still does not boot my mac.
        I (sort of) solved the problem by installing a full-blown Lion OS on an external firewire hard-drive, booting from it and then running Diskwarrior. Older versions of DW will do directory repair, they just aren't bootable if out of date.
        What I want to do is to boot from a Flash drive, and then run Diskwarrior.
        I have created a bootable flash drive, which works, but boots into the Mac OS X Utilities window (the same window you get when you boot into Recovery mode. Even though I'm booted from the flash drive, this window does not let me access Diskwarrior.  Help.
    P.S. I  also have a 2T Time Capsule attached, can I put a copies of Lion and Diskwarrior on that to solve the problem?

    Instead of the instructions specified, use the Disk Utility or another product to clone your existing system to a drive large enough to hold it, or install a minimal Mac OS X system onto that drive. The Time Capsule can't be used for this purpose.
    (64539)

  • Booting from Flash Memory in MS-6368

    Hello all,
      we are having problems to boot from a 128Mb Flash Memory. Until now we are booting from a 64Mb Flash Memory and all were ok.
    When we boot from this Memory, we execute a start manager (grub): We choose a option in the start menu: for change the bios with "awfl789.exe"(in a MS-Dos Partition) or for run the machine (in another partition: Linux).
    When we boot from 64Mb Flash Memory all it´s ok, but when we boot from 128Mb Flash Memory only work the Linux partition; the MS-Dos partition can´t execute the "autoexec.bat".
    The program into both memories is exactly the same.
    ¿Anybody knows if exist problem booting or working with this sizes of Flash Memory?
    My computer:
    Main Board: MS-6368 v5.0
    Bios Version: 5.9
    Flash Memory 64Mb: PNY (manufacturer)
    Flash Memory 128Mb: PNY (manufacturer)
    Microprocesor: C3 800MHz

    jakobm wrote:
    Are you selecting the right partition with grub's 'root' parameter?
    Can you provide us with the partition table and the grub configuration?
    Sure. Not-commented out lines from /boot/grub/menu.lst:
    timeout   5
    default   0
    color light-blue/black light-cyan/blue
    # (0) Arch Linux
    title  Arch Linux
    root   (hd1,0)
    kernel /vmlinuz26 root=/dev/disk/by-uuid/b6526d0b-875d-46b7-8448-7beb2608c544 ro
    initrd /kernel26.img
    # (1) Arch Linux
    title  Arch Linux Fallback
    root   (hd1,0)
    kernel /vmlinuz26 root=/dev/disk/by-uuid/b6526d0b-875d-46b7-8448-7beb2608c544 ro
    initrd /kernel26-fallback.img
    hd0 is a hard drive. Partitions are:
        Name        Flags      Part Type  FS Type          [Label]        Size (MB)
        sdb1        Boot        Primary   Linux ext2                         131.61
        sdb2                    Primary   Linux ext3                       10001.95
        sdb3                    Primary   Linux ext3                        5000.98
        sdb4                    Primary   Linux swap / Solaris              1093.97
    I have tried grub>find /[tab] to be sure a root is appropriate. Both img are there.
    Last edited by student975 (2011-03-05 23:01:01)

  • Boot from flash drive

    Is T400s capable of booting from a flash drive?  Some Linux vendors have their live versions on flash drives and I would like to try them out.  I have a Linux live CD but the drive makes too much noise and is relatively slow when I use it.

    My trusty old T400 certainly is.  Hit F12 during boot and see if your flash drive shows up in the boot menu.
    Z.
    The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc.  The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • Router was not booting from flash

    hi
    my 2811 router was not able to from flash
    while it booting it was showing below message. please find the image.
    after this using tftp i was uploaded the ios after uploading it was booting sucessfully. after booting when i reload the router
    the above message was showing. then i have to reload the ios. config reg is 0x2102, ios is c2800nm-adventerprisek9-mz.124-24.T.bin
    and 15T. bot the ios. on this i have to configure mgcp for fxs ports.
    please help me.
    thankq.

    Remove all the network modules and/or HWIC from the router and reboot again.
    Can you please cut-and-paste the entire bootup process (please don't post a photo taken from your mobile phone because  you might miss out some important details).

  • Booting From External DVD Drive Thru USB to install OS Tiger DVD

    Hi,
    I would like to reformat my iBook G4 from Panther to Tiger. I dont have DVD drive internally. I've got the DVD ROM of Tiger and external USB DVD Drive. Tell me the possible ways to do the installation beside Firewire connection.
    Please help me.

    Hi Nik,
    AFAIK you cannot boot from USB devices. You could give it try by inserting the Tiger DVD into the external drive and rebooting your Mac while holding the "alt" key. If your DVD drive was bootable then -after a while- the DVD should come up as an option to boot from. But this is not likely to happen.
    The best way to get Tiger on your iBook - unless you have anothet Mac with a DVD drive lying around - is to get the Media Exchange form from this website and to exchange your DVD for a set of CDs (minus a handling fee).
    -Petra

  • Cannot create bootcamp, cannot boot from Windows DVD or Bootcamp USB.

    2011 Mac Mini, running 10.9 Attempting to create a bootcamp installation. Note that I have done this many times with other Macs, including similar Mac Minis.
    I get through the Bootcamp assistant process of downloading windows support files and creating a USB drive for the install, I partition the internal 500gig hard drive in half. On reboot all I get is a black screen. Not a Black screen with flashing cursor, no error of any kind, just completely black, I have waited for over 45 minutes and it never changes. I have repeated this process several times, letting bootcamp assistant remove the partition in between, with several versions of the .iso file. I have recreated it from an original Windows 7 Pro 64bit. I have downloaded an iso of the same from Microsoft. None give any different results. I have reset the PRAM. I have a external Apple superdrive and have booted up to startup disk manager and can see that the USB is a valid boot, the Windows DVD is valid and there is an option for EFI Boot. None work, all give the exact same black screen with nothing. When booting from the Windows DVD, you can hear it spin up and read for a short while, then is stops. I have read and tried all the related posts here and on any web site I can find, although there are few and most just point back to the same articles here.
    Help, tis is driving me crazy! I know it can be done, but there is something at work here I can't figure out.

    You need to use a USB2 flash drive for BC Drivers/Windows ISO, not a USB3 stick. Windows installers do not support USB3 out-of-the-box. On Macs, BC drivers will later add support for USB3.

  • Will the late 2013 Mac Pro boot from an external drive (4Tb, USB 3) with a cloned Win7 x64 partition on it?

    Hello all,
    I ordered a CTO Mac Pro for heavy rendering and animating work, and I am planning on using bootcamp to install a windows partition (for 3DsMax). As I am now using a HP Elitebook 8770W that has several valuable files and projects on it, I have bought a Seagate 4Tb external Desktop Drive that uses USB 3.0 to use as a backup drive. Now, as I saw that Bootcamp Assistant only supports installing a x64 version of Windows 8, my question is:
    Will a late 2013 Mac Pro using bootcamp assistant boot from an external USB drive with a cloned partition running x64 win7? Or do I really have to buy Windows 8 and install that to my internal SSD, and then use the migration assistant to copy over my projects?
    Thanks!

    Posted? or found in new builds?
    BCA should really just pull whatever the latest drivers are when run. 
    If it is with how it partitions and sets up nMP and its partition for Windows that is another matter and makes sense.
    Some people want UEFI native booting in Windows, and my experieince with that on PCs has been that it boots faster and runs well, but has different partitions that it wants. For one thing, there is now a backup "system reserved" partition, just as Apple GUID has some volume information blocks and backup and areas that were once optional (and if format erase was not able to, it would not create one) are now mandatory.
    Windows 8.1 is req'd, reason a backup should be a big must - is it might overwrite and use another OS's  partition table entries.  Especially when doing UEFI install.
    There was something about which linux OS was safe and how they would each add entries in the table, but one would not place nice.  That one had to be done first or not at all.

  • Boot Camp "Quit and install later" corrupted the BOOTCAMP partition

    I just had my new iMac delivered.
    The first things I did was to run Software Update to install 10.6.8, then I installed 10.7.1 Lion and ran Software Update again just to be sure I got everything up to date as it should be. After installing a couple of applications via App Store and the web I set about to create a Boot Camp partition for my Win7 needs. When the assistant was finished (a new partition created and drivers saved to a USB memory stick) and told me it was ready to install Windows, but I choose Quit and install later (and oh, what I now regret that choice) because my Windows DVD was nowhere to be found (I should have looked a little harder).
    Then when I later found the Windows 7 install DVD I launched Boot Camp Assistant again, but lo and behold when it tells me that I need to reformat my partions and start over from scratch. Boot Camp Assistant refuses to let me install Windows because I choose Quit and install later.
    I have tried the following things to solve the problems:
    Repair permissions and repairing the disk.
    Start with the bundled OSX DVD to run fsck -fy followed by Disk Utility.
    Re-format the BOOTCAMP partition.
    Boot from the Windows 7 DVD (which claims something along the lines that the partition does not support Windows installations).
    Nothing works! Why? How do I solve this?

    The past and having used whatever. FWB HDToolkit, Silverlining, $10K worth of scsi means??
    windows requires that the partition table and format (GUID) has full functional MBR that Windows and Mac can work with.
    Ever heard of take your best guess and double it for how much space to allocate? or no matter how good your partitions will always need to be changed.
    Apple (that pdf guide?) is quite clear about one thing, which I usually but not here, take with grain of salt, that Boot Camp Assistant is a one trick pony to do the job of setting aside unfragmented free space for Windows.
    ie, you can't use FWB Toolkit of SoftRAID 4.0 (excellent though it is!). Though Paragon CampTune (the company is rare, supports Boot Camp etc) and can be used.
    If you created it now, but then you had 10.7 and Boot Camp 4, I could possibly get my head to imagine there could be an issue. And that is because every OS version has new changed partition table changes, making for this old (65 and going) mainframer to re-initialize drives whenever there is a change.
    You can clone your system, format, and restore nice and clean with SuperDuper in a Jiffy. So why bother now? can't see it.
    I understand people wanting 3 or more partitions. Wanting Windows to boot off external drive. Or use GPT and UEFT (that may happpen as 3TB drives and is beginning to be supported, but so far Apple and EFI are closed, proprietary, and GPT booting and EFI go hand in hand) but extra partitions is just... wishful.

  • Can't Boot from bootable CD/DVD or USB.

    I'm trying to install a new OS from a bootable DVD that I created. However, my T530 will not boot up from the DVD. I checked the boot order in the BIOS settings, and even explicitly tried to force to boot from my DVDROM usint the F12 boot menu. I've been able to boot from this DVD on my other computer.
    Any way to diagnose whether my DVDROM is faulty, or is there perhaps some BIOS setting to fix this? I am able to read the disc from Windows, just can't boot from it. The laptop is brand new, just opened it up today, so I don't know why something as simple as this wouldn't just work.
    Solved!
    Go to Solution.

    ThorsHammer wrote:
    dreachem wrote:
    I took a DVD drive from another Thinkpad and swapped that in. I still could not boot from the disc. 
    Next, I copied the ISO image to a USB stick and tried to boot from that instead. But it hung. I was able to boot from the same USB stick on another laptop.
    All the signs seems to suggest the laptop is simply defective, which is extremely disappointing considering it is brand new and I waited for about a month to receive it.  Is there anything else I can/should try (some diagnostic utility, perhaps?), or do I just send it in for a replacement?  
    Is you used the tool at http://www.microsoftstore.com/store/msstore/html/pbPage.Help_Win7_usbdvd_dwnTool to take the .ISO file and create the USB stick, I'd say you are right and have an issue with the system.
    Did the system ship with Windows 8 and is safe boot turned on?
    Yes, it is Windows 8 with Secure Boot on by default. I tried it both with it enabled and disabled, and it didn't work either way.

  • Booting from an external drive over usb

    Hey, has anyone else had any problems booting from an external? I have an external lacie drive that I keep a clone backup on (using superduper) and usually have it connected with firewire400. I know it works because i've accidently booted using it before, but recently the firewire port on it died so i've been using usb instead.
    Now the problem, holding option on my macbook starting, I get no options to choose from. If i have the mac osx dvd in, it pops up so I know it's not a problem with my macbook. It is possible to boot from usb correct? Everything i've read has said it's possible... I'm not sure why my external drive isn't coming up. I know it works over usb because I've used it alot since the firewire port died on it. I checked in the disk utility and it does say it's bootable, and afterall it's cloned using superduper like i said before...
    I have 2 partitions on the drive, is that a problem? It never was before, I've booted off it many times before using firewire though. Can someone help me out here? Very annoying as I'm replacing the HD in my macbook and neeeeeeed to get on my external.
    When I asked the guy at the genius bar awhile ago he just said it was probably a problem because my old internal HD died and he said sometimes it causes the macbook to not even be able to get as far as the point to boot from another source. Well now I have a new working drive in it, so I know that's not the problem. It just doesn't show up to boot from anymore, ugh.

    Sounds like your clone isn't bootable. Have you tried the following:
    Repairing the Hard Drive and Permissions
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
    If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger, and 4.1 for Leopard) and/or TechTool Pro (4.6.1 for Leopard) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

Maybe you are looking for