Hi Frank, When the initrd drops you to a shell you can check what your system thinks the SD card is by typing
fdisk -l or cat /proc/partitions Then change the root=/dev/sda1 to the right device name in the kernel command line (the line starting with kernel) in /boot/grub/menu.lst Good luck, Michael. On Tue, Feb 23, 2010 at 7:45 AM, Frank Parker <[email protected]> wrote: > CC'ing conversation back to list for archiving... > > Joshua, > Thanks again. I tried the install again using voyage-current and > voyage.update didn't throw any errors. I had the SD card connected to > an Ubuntu system via a USB multicard reader during the install. Then > I plugged the multicard reader into my Foxconn device > > <http://www.foxconnchannel.com/Product/Barebones/NT330i/index.html> > > ...and it boots perfectly. I am watching the boot process on a > monitor attached to the DVI port. The USB keyboard isn't working, but > this will be a headless box anyway. So I dont care. > > However, if I move the SD card to the built-in SD card slot it loads > GRUB, decompresses the kernel and begins booting. At about 8 seconds > I see it hang at: > > ---[SNIP]-- > [8.275103] scsi 0:0:0:0: Direct-Access Generic STORAGE DEVICE 9732 PQ > : 0 ANSI: 0 > [8.406383] SD 0:0:0:0: [sda] Attached SCSI removable disk > ---[SNIP]-- > > After a minute or two, it prints: > > ---[SNIP]-- > done. > Gave up waiting for root device. Common problems: > - Boot args (cat /proc/cmdline) > - Check rootdelay= (did the system wait long enough?) > - Check root= (did the system wait for the right device?) > - MIssing modules (cat /proc/modules; ls /dev/) > ALERT! /dev/disk/by-label/ROOT_FS does not exist. Dropping to a shell! > (initramfs) _ > ---[SNIP]-- > > I cant do any troubleshooting here without a keyboard but I think I > must need to alter the GRUB settings. The built-in SD card reader > must be recognized as a different device. Maybe? > > A successful dmesg when booting via the multicard reader looks like this: > > ---[SNIP]--- > [ 8.341143] scsi 0:0:0:0: Direct-Access Multiple Card Reader > 1.00 PQ: 0 ANSI: 0 > [ 8.341759] usb-storage: device scan complete > [ 8.412496] scsi 1:0:0:0: Direct-Access Generic STORAGE DEVICE > 9732 PQ: 0 ANSI: 0 > [ 8.413113] usb-storage: device scan complete > [ 8.431027] sd 1:0:0:0: [sdb] Attached SCSI removable disk > [ 8.951749] sd 0:0:0:0: [sda] 3985408 512-byte hardware sectors: > (2.04 GB/1.90 GiB) > [ 8.953864] sd 0:0:0:0: [sda] Write Protect is off > [ 8.953986] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00 > [ 8.953992] sd 0:0:0:0: [sda] Assuming drive cache: write through > [ 8.958864] sd 0:0:0:0: [sda] Assuming drive cache: write through > [ 8.958948] sda: sda1 > [ 8.960174] sd 0:0:0:0: [sda] Attached SCSI removable disk > ---[SNIP]--- > > > My /boot/grub/menu.lst looks like this: > > ---[SNIP]--- > timeout 5 > default 0 > > title voyage-linux-22Feb10 > root (hd0,0) > kernel /vmlinuz root=LABEL=ROOT_FS > initrd /initrd.img > ---[SNIP]--- > > > I can move the SD card back to the multicard reader to make the > necessary changes but how do i determine what to change? > > > > On Sat, Feb 20, 2010 at 6:52 PM, Joshua Anhalt <[email protected]> wrote: >> Frank, >> >> Call format-cf.sh without the partition number: >> format-cf.sh /dev/sdd >> >> Joshua >> >> On Feb 20, 2010, at 2:50 PM, Frank Parker wrote: >> >>> Trying to install voyage-current onto an SD card to see if my device >>> will boot from SD card. I followed the installation steps in the >>> README using my SD card (recognized as /dev/sdd) instead of a true CF >>> card. On the last step the installer throws this error... >>> >>> >>> ---[SNIP]--- >>> Configuration details: >>> ---------------------- >>> >>> Distribution directory: /home/ubuntu/Downloads/voyage-current >>> >>> Disk/Flash Device: /dev/sdd >>> Installation Partition: /dev/sdd1 >>> Create Partition and FS: yes >>> Bootstrap Partition: /dev/sdd1 >>> >>> Will be mounted on: /mnt/cf >>> >>> Target system profile: Generic PC >>> Target console: standard >>> >>> Bootstrap installer: grub >>> Bootstrap partition: /dev/sdd1 >>> >>> OK to continue (y/n)? y >>> >>> Ready to go .... >>> Checking that no-one is using this disk right now ... >>> OK >>> >>> Disk /dev/sdd: 1020 cylinders, 63 heads, 62 sectors/track >>> Old situation: >>> Units = cylinders of 1999872 bytes, blocks of 1024 bytes, counting from 0 >>> >>> Device Boot Start End #cyls #blocks Id System >>> /dev/sdd1 0+ 1019 1020- 1992029 83 Linux >>> /dev/sdd2 0 - 0 0 0 Empty >>> /dev/sdd3 0 - 0 0 0 Empty >>> /dev/sdd4 0 - 0 0 0 Empty >>> trailing junk after number >>> >>> sfdisk: bad input >>> mount: special device /dev/sdd1 does not exist >>> Fatal Error: Failed to mount /dev/sdd1 on /mnt/cf as an ext2 partition >>> ---[SNIP]--- >>> >>> >>> I had previously used fdisk to create a single linux partition on the >>> SD card and formatted it with ext2. I verified that I can mount the >>> SD card (mount /dev/sdd1 /mnt/cf) and read/write files. Not sure why >>> the installer is having trouble. >>> >>> Then I tried the format-cf.sh helper script and it throws this error... >>> >>> >>> ---[SNIP]--- >>> # ./usr/local/sbin/format-cf.sh /dev/sdd1 >>> Press ENTER to continue to format flash memory on /dev/sdd1 >>> >>> Checking that no-one is using this disk right now ... >>> BLKRRPART: Invalid argument >>> OK >>> Warning: start=62 - this looks like a partition rather than >>> the entire disk. Using fdisk on it is probably meaningless. >>> [Use the --force option if you really want this] >>> ---[SNIP]--- >>> >>> >>> Any clues? >>> >>> _______________________________________________ >>> Voyage-linux mailing list >>> [email protected] >>> http://list.voyage.hk/mailman/listinfo/voyage-linux >>> >> >> > > _______________________________________________ > Voyage-linux mailing list > [email protected] > http://list.voyage.hk/mailman/listinfo/voyage-linux > _______________________________________________ Voyage-linux mailing list [email protected] http://list.voyage.hk/mailman/listinfo/voyage-linux
