[SOLVED] Diskless NFS boot

I've been struggling to get my diskless pc to boot using this guide.
It seems the kernel is loaded properly from tftp but the root filesystem fails to mount. This is what I get:
http://dl.dropbox.com/u/29192523/Screen … 044316.jpg
The server is Arch-based, it didn't work with an Ubuntu server either though.
Any help would be appreciated.
Here are some configs:
/etc/exports
/srv/nfs 192.168.1.0/24(rw,fsid=0,no_subtree_check)
/srv/nfs/disklessarch 192.168.1.0/24(rw,no_root_squash,no_subtree_check,nohide,insecure,sync)
/srv/nfs/disklessarch/boot/pxelinux.cfg/default
default linux
label linux
kernel vmlinuz-linux
append initrd=initramfs-linux.img rootfstype=nfs nfsroot="192.168.1.200:/disklessarch,rsize=16384,wsize=16384" ip=192.168.1.201:192.168.1.200:::gallifrey:eth0:none
This was also tried with root=/dev/nfs and ip=:::::dhcp
/srv/nfs/disklessarch/etc/mkinitcpio.conf
MODULES="nfs"
HOOKS="base udev net autodetect pata scsi sata filesystems usbinput fsck"
Last edited by Ram-Z (2012-09-07 17:15:04)

After some more fiddling I got it working with:
default linux
label linux
kernel vmlinuz-linux
append initrd=initramfs-linux.img rootfstype=nfs nfsroot=192.168.1.200:/srv/nfs/disklessarch ip=192.168.1.201:192.168.1.200:::gallifrey:eth0:none
/srv/nfs 192.168.1.0/24(rw,fsid=0,no_subtree_check)
/srv/nfs/disklessarch 192.168.1.0/24(rw,fsid=1,no_root_squash,no_subtree_check,nohide,insecure,sync)
I tried this before but with fsid=0 on disklessarch, which just mounted the entire /srv/nfs and the kernel could not find /sbin/init.
It looks like mkinitcpio-nfs-utils still does not support NFSv4.
Thanks for your help.

Similar Messages

  • [SOLVED] How to NFS boot?

    Dear All,
    I am trying to perform something similar to the setup presented here:
    Diskless network boot
    I have a virtual machine which I want to use in one of my projects but since the machine will be deployed on couple of computers and the disk space of these compters is limited I wanted to use NFS for root.
    Server side:
    According to the article I create on the server 138.250.86.221 an nfs export ofvm-root. I install system image there (base and base-devel). I believe I do not have to play with DNS as the computer has a fixed address in the local network. I verify that that the host machine can mount my exported folder.
    Client side:
    On my virtual machine I install mkinitcpio-nfs-utils and of course nfs-utils. I add net to HOOKS in /etc/mkinitcpio.conf and issue
    mkinitcpio -p linux
    to regenerate initramfs following what I have read in  mkinitcpio article.
    Finally, in my grub menu I hit e and edit the kernel line as suggested in the article on kernel parameters
    I tried addings
    nfsroot=138.250.86.221:/ofvm-root
    and
    root=/dev/nfs nfsroot=138.250.86.221:/ofvm-root
    The first one booted using local root and the other one didn't boot at all giving an error:
    ERROR: device '/dev/nfs' not found. Skipping fsck.
    ERROR: Unable to find root device '/dev/nfs'.
    Could you please advise what I am possibly missing or doing wrong? Please let me know. Are there any more links on Arch NFS boot setup?
    Last edited by AlmostSurelyRob (2012-10-13 11:18:30)

    Alas, I must report a regress. Due to problems with X configuration I had to redo initramfs and the system no longer boots. It replies with an error "mount: protocol not supported".
    Two things:
    1) I do not really understand which initramfs is being used on boot. On the server side there is /mnt/arch/boot and it contains initramfs based on 3.6.2 kernel. However, when I boot using my VM client I can see that it is 3.5.6 kernel that is being used (uname -a or the login prompt).
    2) Because of the problems with X I decided I want to upgrade the client to 3.6.2 and redo my initramfs. I started the installation process anew. Using pacstrap I installed only base and mkinitcpio-nfs-utils grub-bios and initscripts (in another attempt I also tried adding nfs-utils). Then I rebooted to the vm-local root. This worked fine. The kernel was already at 3.6.2 so I've made changes to mkinitcpio.conf: MODULES="nfs" and added "net" to HOOKS. I run
    mkinitcpio -p linux
    All went fine. Then I went to my VMPlayer and booted. In grub I added
    root=/dev/nfs 138.250.86.221:/mnt/arch ip=::::::dhcp
    to kernel parameters. It found the compter, but mount announced that it does not support this protocol.
    By the way, the client with initramfs based on 3.5.6 works with the above line. I must be doing something seriously wrong - I would appreciate sp,e advice. Also, is it all right if I mark the post back as "UNSOLVED"?
    Last edited by AlmostSurelyRob (2012-10-17 10:15:46)

  • [SOLVED] Diskless booting.

    I am trying to create a diskless installation of arch using the wiki article Diskless System and I am failing miserably.
    This is the section that is causing me trouble.
    This works fine:
    sed s/nfsmount/mount.nfs4/ "$root/usr/lib/initcpio/hooks/net" | tee "$root/usr/lib/initcpio/hooks/net_nfs4"
    When I try the next command I get this:
    cp "$root/usr/lib/initcpio/install/{net,net_nfs4}"
    cp: missing destination file operand after '/srv/nfs/archlinux/kiosk/usr/lib/initcpio/install/{net,net_nfs4}'
    Also this sentence is causing me quite a bit of confusion also:
    "From the base mkinitcpio.conf, replace the nfsv3 module with nfsv4, replace net with net_nfs4, and add /usr/bin/mount.nfs4 to BINARIES."
    If someone could please provide a little bit more detail about what I need to do there.
    Thank you in advance for your help!
    Last edited by dropdeadgreggie (2013-10-30 19:51:14)

    alphaniner wrote:
    dropdeadgreggie wrote:I'm still confused in regard to constructing the initramfs, I'll keep digging.
    "From the base mkinitcpio.conf, replace the nfsv3 module with nfsv4, replace net with net_nfs4, and add /usr/bin/mount.nfs4 to BINARIES."
    I wonder if the directions to 'replace' are just misleading. I'd try modifying mkinitcpio.conf as follows:
    Put nfsv4 in the MODULES array.
    Put net_nfs4 in the appropriate location in the HOOKS array. It probably needs to go in the same location the 'block' hook would normally go.
    Put /usr/bin/mount.nfs4 in the BINARIES array.
    I get the following:
    # mkinitcpio -g $root/boot/initramfs-linux.img -k $root/boot/vmlinuz-linux -c $root/etc/mkinitcpio.conf
    ==> Starting build: 3.11.6-1-ARCH
    -> Running build hook: [base]
    -> Running build hook: [udev]
    ==> ERROR: Hook 'net_nsf4' cannot be found
    -> Running build hook: [autodetect]
    ==> Generating module dependencies
    ==> Creating gzip initcpio image: /srv/nfs/archlinux/kiosk/arch/boot/initramfs-linux.img
    ==> WARNING: errors were encountered during the build. The image may not be complete.
    The file(s) exist in both /usr/lib/initcpio/hooks and /usr/lib/initcpio/install.
    However the system does boot with the "net" hook.

  • Diskless client NFS boot fails. cannot create /dev/nfs

    Hi
    I've set up a diskless laptop to boot off my server, both running Arch. I followed the wiki article: https://wiki.archlinux.org/index.php/Di … t_NFS_root
    PXE on the laptop connects with the tftpd server just fine, gets the kernel and begins booting up. At some point it begins looking for /dev/nfs, declares it does not exist, attempts to create it and and fails with the following error (from memory as I'm not at the computer now).
    "ERROR: Unable to determine major/minor number of root device root=/dev/nfs"
    my kernel param line in pxelinux.cfg/default is just like the one in the wiki article i.e
    default linux
    label linux
    kernel vmlinuz26
    append initrd=kernel26.img rootfstype=nfs root=/dev/nfs nfsroot=10.0.0.1:/disklessroot,v3,rsize=16384,wsize=16384 ip=::::::dhcp
    any help will be greatly appreciated.
    emk

    I'm assuming youve entered your own IP addresses instead of just copy&pasting from the howto, correct?
    Also, did you install all the nfs packages, and do the mkinitcpio-nfs-utils procedure?

  • Running X11 and KDEmod on a diskless NFS computer

    I have setup a server to boot another computer using this guide. Now, I have install Xorg and KDEmod, and they work just fine. I have but one problem: X11 will not accept input from either the keyboard or the mouse. Both work at the command line (mouse tested using vim), but once I start X after booting the diskless computer, they don't work. Both have power. CTRL+ALT+Bksp does not shutdown X or produce any visible effect. How should I solve this issue?
    (The xorg.conf is autogenerated by X -configure)

    Try adding this to your xorg.conf:
    Section "ServerFlags"
    Option "AutoAddDevices" "False"
    EndSection
    Or try this hotplugging

  • Diskless client boot on a blade farm

    We have a possible blade-centric architecture we are looking at whereby the chassis provides for F/C connection to a SAN and standard Ethernet (x 2) for network.
    As we are looking to use RHEL as the OS I'd be interested to know whether people think that the blades can be booted as a diskless client (is this supported by Oracle?) from a single boot image on the SAN or the network. All Oracle datafiles would be maintained on the SAN. Has anyone experience or comments on this kind of setup?
    The possible advantages of this would be the reduced admin for RHEL: When patches are applied one blade can be taken out of the cluster and booted from a secondary image against which the patches are applied. When completed, the remaining blades can be rebooted one at a time to pick up the revised image. The first boot image can be left hanging about as a fall back option before the next round of upgrades. Also, expanding the number of blades can be done (near as damn it) with zero configuration and there is little chance of version mismatches in the OS.
    I am concerned about database upgrades, the Oracle home in a shared everything environment, impact on Grid Control, so I welcome any comments/criticism/abuse.
    Best regards to all,
    Jon Mercer

    I haven't tried RAC on diskless boots, but I have used diskless boots with RHAS3. Once the system is running, you can't really tell except that all mount points are NFS based.
    But in regards to having the oracle homes shared, I would recommend against it. If you follow the normal guidelines for the diskless boots, you'll find that each node already have it's own "home" on the array; in particular paritions like /var and /tmp cannot be shared between hosts. The same goes for Oracle, as (unforunately) it puts most of it's log files in the oracle home. These would have to be different.
    I would look at OCFS2 - it has support for shared Oracle Homes - in which it can be TOLD to keep seperate copies of "common" log files - meaning seperate files for each host. This way, executables that are the same, stays as one copy but host specific data are separated out. I would be very careful before going that route and do a lot of testing; but that seems to be what the good linux guys thought of when they did the OCFS2.

  • [SOLVED] Error while booting, related to nilfs2

    I've just installed my fresh Arch and used nilfs2 inside vlm2 as my home partition. While booting, I'm getting these errors:
    fsck: fsck.nilfs2: not found
    fsck: error 2 while executing fsck.nilfs2 for /dev/mapper/TheVG-HomeLV
    Other logical volumes are getting "clean" output while checked so it's not vlm-related; they are all ext4.
    Partition is mounted and seems to work but I'm scared of just ignoring it and creating my user. ;-)
    I have nilfs-utils installed. Is there any hook or module I need to add somewhere in order to use nilfs2 properly (like reiserfs hook)? There is nothing in the Wiki about this file system...
    Edit: well, it appears that nilfs doesn't not come with check utility so I'm marking this as solved; sorry for garbage post...
    Last edited by smsware (2013-03-16 22:07:55)

    As there is no fsck utility and as it actually is planned to be created (I read that it's needed because the fs can easily crash on power loss; still, it can be recreated, as you stated)  - there is a warning while building the kernel. I deleted fsck hook to not see it as my /var and root are sub-volumes of btrfs partition which doesn't need fsck as well. I made a service to umount, fsck and mount back the /boot (ext4) and uefi partitions... just to let you know what you can expect. But it's great anyway, snapshots are really easy to mount and use. I thought it has no wiki page because it's not popular (and probably for a reason) but now I believe it's because there is nothing to write about... it just works. ;-)
    Last edited by smsware (2013-05-29 15:58:26)

  • [SOLVED] Unable to Boot Windows 7 from GRUB

    I recently reinstalled Arch onto my laptop (Lenovo Thinkpad t520) and have been having problems with Grub. For the last week I've been having trouble getting it to run grub at boot at all, only being able to run windows 7 by flagging it as the bootable drive. The other day I finally got it to boot into grub, and from grub I can boot into Arch. However, I can not boot into windows 7 through grub. When I attempt to, it throws an error:
    Invalid EFI file path
    I'm somewhat new to arch, and especially new to efi bootloading and such. Right now the only way I can get into windows is either booting from the arch install disk > boot other os and specifying partition 2 (where I have windows installed) or by pressing f12 at boot. When I do this (not sure what the term is, if anyone knows please tell me), it brings up a menu asking where I want to boot with "arch_efi" "cd drive" "Hard drive" etc. I choose hard drive and it will then boot to windows by default. Booting normally takes me to grub where I can boot into arch but not windows. If there's any more info you need please let me know and I'll try to provide it. Thanks in advance.
    Also, here is my current partition setup
    /dev/sda1 /boot/efi
    /dev/sda2 Windows7
    /dev/sda3 Extended partition containing sda 5,6, & 7
    /dev/sda4 swap
    /dev/sda5 /boot
    /dev/sda6 /
    /dev/sda7 /home
    UPDATE
    Terminator seems to be right (still on a roll!), so I wiped the partition I had grub on, removed grub, and installed syslinux. Now I have another problem that I'm hoping can be solved in the same thread to avoid another. It boots to syslinux no problem, and I can boot to windows from there all good, but when I select arch I get:
    Root device mounted successfully but /sbin/init does not exist
    I haven't been able to look for solutions too much on my own, but any help would be appreciated, thank you.
    Last edited by IamFuzzles (2012-08-22 04:20:56)

    Terminator wrote:If I understand it correctly, what you are trying is impossible: you are trying to boot windows using UEFI on a disk with MBR partitioning. Windows 7 only supports UEFI on discs with GPT partitioning but AFAIK, extended partitions only exist in MBR partitioning.
    i also saw this in the arch wiki, but i have a brand new lenovo ideapad y570 running windows 7 64-bit that i'm in the process of setting up for someone, and it has what i think is an efi system partition but the disk uses mbr partitioning.  does anyone know why this might be, or is there a way i can verify that the system is actually being booted via bios-mbr?
    Last edited by e_tank (2012-08-21 11:56:15)

  • [SOLVED]Unable to boot in UEFI mode from CD

    Hello gents!
    Here's the problem:
    According to the beginner's guide I followed the instruction to test if I am in UEFI mode:
    In case you have a UEFI motherboard, the CD/USB will launch UEFI Shell and display a message that
    startup.nsh
    script will be launched. Allow the shell to launch it. Then, to check whether you have booted into UEFI mode, load the efivars kernel module (before chrooting) and then check whether there are files in
    /sys/firmware/efi/vars/
    # modprobe efivars # before chrooting
    # ls -1 /sys/firmware/efi/vars/
    Well, the thing is that when I boot the CD no UEFI Shell is launched as well as no
    startup.nsh
    When I try to load the efivars I don't receive any message, so, I assume, the module is loaded; but the, when I invoke ls the message I receive is:
    #ls: cannot access /sys/firmware/efi/vars/: No such file or directory
    To me it looks that for some reason I am unable to access the UEFI mode when starting the CD iso.
    Thank you guys for your courteous attention.
    Have a wonderful day!!!
    P.S. I've searched already in the following posts:
    https://bbs.archlinux.org/viewtopic.php … 84#p148184
    https://bbs.archlinux.org/viewtopic.php … 55#p148155
    P.S.2
    My mobo is an ASUS Maximus V Gene with i3770K on it.
    Edit:
    Ok guys! Thanks to all of you, but everything was brought about by my scarce knowledge of the mobo. Logging into the BIOS, in the boot section, you have to choose between normal DVD and UEFI DVD. When selecting the last, everything, I mean, the startup phase at least, went well.
    Enjoy everybody
    Any idea how to close/"solved" this forum tread?
    Last edited by guidone (2012-09-11 20:34:21)

    guidone wrote:Any idea how to close/"solved" this forum tread?
    README: Forum Rules
    Simply edit the original post by clicking on the 'edit' button at the lower right corner of it and prepend [SOLVED] to the title.

  • [SOLVED] Unable to boot after update

    After full system upgrade my arch is unable to boot kernel:
    ERROR: device 'UUID=xxx...' not found, skipping fsck.
    ERROR: unable to find root device 'UUID=xxx...'
    You're being dropped to a recovery shell
    I'm pretty sure UUID of /dev/sda2 is correct (double checked with Ubuntu live cd).
    Last edited by soroush (2012-09-06 12:20:15)

    Then you need to provide more information. Bootloader? Kernel? Tried fallback initramfs?
    Edit: OK, you solved it. pacman does regenerate the initramfs if the kernel is updated. It just didn't work for you this time.
    Last edited by progandy (2012-09-06 12:21:55)

  • [SOLVED]Unable to boot from SATA, but it works from USB

    I have strange problem. I made an Arch installation in VMware virtual computer and then I copied the virtual disk to new SSD. When I install the disk into the real hardware (Intel Canoe Creek D2500CC board), i get the "ERROR: Unable to find root device '/dev/sda1'." error.
    The strange thing is, that the computer can boot correctly, when I connect the SSD using SATA->USB bridge.
    In the recovery shell there are no disk devices (/dev/sd*) so I think it is not a problem of changed device name (f.e. /dev/sdb1 instead of /dev/sda1), to me it looks like udev is not running.
    What can be the problem, that the system boots normally when SSD is connected via USB and can not boot when connected directly to SATA port?
    My mkinitcpio.conf:
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run.  Advanced users may wish to specify all system modules
    # in this array.  For instance:
    #     MODULES="piix ide_disk reiserfs"
    MODULES=""
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image.  This is run last, so it may be used to
    # override the actual binaries included by a given hook
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way.  This is useful for config files.
    FILES=""
    # HOOKS
    # This is the most important setting in this file.  The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ##   This setup specifies all modules in the MODULES setting above.
    ##   No raid, lvm2, or encrypted root is needed.
    #    HOOKS="base"
    ##   This setup will autodetect all modules for your system and should
    ##   work as a sane default
    #    HOOKS="base udev autodetect block filesystems"
    ##   This setup will generate a 'full' image which supports most systems.
    ##   No autodetection is done.
    #    HOOKS="base udev block filesystems"
    ##   This setup assembles a pata mdadm array with an encrypted root FS.
    ##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    #    HOOKS="base udev block mdadm encrypt filesystems"
    ##   This setup loads an lvm2 volume group on a usb device.
    #    HOOKS="base udev block lvm2 filesystems"
    ##   NOTE: If you have /usr on a separate partition, you MUST include the
    #    usr, fsck and shutdown hooks.
    HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
    # COMPRESSION
    # Use this to compress the initramfs image. By default, gzip compression
    # is used. Use 'cat' to create an uncompressed image.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    #COMPRESSION="lzop"
    #COMPRESSION="lz4"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    Last edited by MaVac (2014-08-15 05:55:18)

    MaVac wrote:Problem solved! :-) I made update with pacman -Su and then everything is working perfectly. :-)
    Then please mark the thread as solved as well.

  • [Solved] Unable to boot after install

    Forgive me for the lack of code tags, having to write this on my phone.
    I am unable to boot after installation. I receive an error wich has the incorrect UDID string. It doesn't even exist. I will update with error after posting so I can give grub config generation error first
    When I run:
    grub-mkconfig -o /boot/grub/grub.cfg
    I get this:
    Found Linux image : /boot/vmlinuz-linux
    Found initd image: /boot/initramfs-linux.img
    Warning: failed to connect to lvmetad: no such file or directory. falling back to internal scanning.
    No volume groups found
    [ 279.601712] SQUASHFS error: can't find a SQUASHFS superblock on sda3
    [ 279.604502] EXT4-fs (sda3):unable to read superblock
    [ 279.607266] EXT4-fs (sda3):unable to read superblock
    [ 279.609928] EXT4-fs (sda3):unable to read superblock
    Found Windows 7 (loader) on /dev/sda1
    Done
    Sda3 is an extended volume
    Edit: I just deleted the old .cfg and recreated a new one by re running the above command, uncounted and rebooted and it booted into CLI. 3rd time a charm after all. Marking this one solved
    Last edited by Kirito (2013-05-15 07:55:31)

    Oh, looking at your setup, it would seem that your system is likely still configured to boot to /dev/sdd (the windows drive).
    As a user with numerous drives, you should be aware that using /dev/sdXY to identify your disks is a bad idea.  There is no gaurantee that Arch will be /dev/sde every time, nor that windows will be /dev/sdd.  You should use either filesystem labels (LABEL= or /dev/disk/by-label) or UUIDs (UUID= or /dev/disk/by-uuid).  Though if you are using GPT, there is also the option of the PARTLABEL as well (which are the labels you create within the partitioner).

  • [SOLVED]Can't boot into OS after installation

    Hello all,
    I've ran into a few problems already all of which I could solve with somme googling etc.
    Until now the installation of arch Linux went pretty smoothly until I rebooted to get into the OS via grub (version 2), once I select Arch Linux in the menu the os starts booting but it stops at this: "a start job is running for dhcpcd on enp7s0 (x s/1m31s)" this always fails. After that 3 extra lines appear starting with a green OK all saying reached target ..........
    This is where no more progress is made, the only keys that generate a response are Ctrl+alt+Del then the system reboots.
    Here is a clear image of the status of the machine
    https://i.imgur.com/queQkEOh.jpg
    EDIT: If you guys need any extra information please ask, but I can't access the systems config files or anything due to this problem so suggestions on how to pull that data are welcome
    -- mod edit: converted img tags to url - Trilby --
    Last edited by Covati (2014-10-06 13:04:05)

    Trilby wrote:
    Welcome to the forums - please see the forum guidelines on how to post including image size restrictions.
    As for the issue - can you Alt-F2 or Alt-F3 to get to another tty?
    It worked, wow I feel dumb now.
    Anyways thank you for helping me out, I will look into the guidelines.
    Can mark this thread as solved!

  • [Solved] MSI 965P boot message ODD0:HL-DT-ST DVDRAM GSA-4167B

    My dear friends,
    I have just bought MSI 965P Neo-f and at every boot I get a message “ODD0:HL-DT-ST DVDRAM GSA-4167B. I’m absolutely sure that I have the right settings for the IDE-Cable and the Jumper setting on the DVD/RW is set to master (also I have tried the other two settings for SL and CS).
    Therefore the DVD/RW couldn’t be recognized in the BIOS , my DVD/RW works only in PIO mode(no way to force it in DMA) and I have conflicts and a really awful performance with my Windows XP SP2 ???.
    Please help if someone already solved this problem.

    I actually had a bad installation of the jmicron driver in Windows  . I have also connected my HDD on the jmicron SATA  controller ,and SiSoft Sandra reported that it’s working in UDMA-6 mode,just cannot see if my DVD/RW drive works also in DMA mode. I have tried with Nero Info tool , but since all my drives are now connected on the SCSI controller, there is no such information. Any suggestions?....

  • [SOLVED] Can only boot Arch via CD

    Hi all,
    I've installed 64 bit Arch on the 2nd hard drive of a Dell Optiplex 980.
    It works very nicely, but I have a strange boot issue:
    If I boot from the Arch CD, and select "Boot other OS", hit Tab, and manually edit the grub line to "chain.c32 hd 1 0", I am taken to the grub menu on the hard drive and can select my install which boots and runs fine.
    If I select the 2nd HD in the BIOS boot menu (instead of the CD), I get to the same grub menu, but upon selecting my install, I get an Error 17.
    Has anyone run into this before?
    Thanks in advance!
    Last edited by basementhead (2010-09-24 17:52:11)

    Turns out I misunderstood how grub works.
    When I changed my menu.lst to (hd 0,0) it works.
    I thought that the 2nd drive was (hd 1,0), which was reinforced by the boot CD working with (1,0), but I guess the drives are renumbered when you boot from CD?
    The big clues were that the partition that grub said couldn't boot was 0xde (a Dell partition), and I was sure I'd wiped the entire drive, but I knew that the 1st drive was a default Dell/Windows7 install.
    Then using grub command line menu, I typed "find /sbin/init" and it found it on (hd0,2), and the mystery was solved....
    Anyway - fixed by treating the drive as if it was /dev/sda (hd 0,0) instead of /dev/sdb (hd 1,0)
    Thanks!

Maybe you are looking for