Loading ...
Sorry, an error occurred while loading the content.
 

Re: Unslung 4.20-beta: Unslung, but rootfs isn't on the hard disk

Expand Messages
  • jrstueve47
    Answering my own question: I reflashed and then re-unslinged again. All is well. I noticed that there were both: .ramdisk .sda1boot in the roots for /,
    Message 1 of 2 , May 25, 2005
      Answering my own question:

      I reflashed and then re-unslinged again. All is well.

      I noticed that there were both:
      .ramdisk
      .sda1boot

      in the roots for /, /initrd and /share/hdd/data

      I tried renaming .ramdisk to .rmdsk in all three parts, and that
      resulted in a boot where the ready/status light never lit. Rebooted
      to a Redboot> telnet session, and then put in upgrade mode, and then
      upslugged the image again.

      Unsling per the ReadMe instructions, and finally booted to a good disk
      structure:
      # df
      Filesystem 1k-blocks Used Available Use% Mounted on
      rootfs 195843204 191120 193662436 0% /
      /dev/sda1 6528 5292 1236 81% /initrd
      /dev/sda1 195843204 191120 193662436 0% /
      /dev/sda1 195843204 191120 193662436 0% /share/hdd/data
      /dev/sda2 116661 4143 111314 4% /share/hdd/conf

      After rebooting to the unslung disk, .rmdsk was still there. I think
      that was a pervious problem, and resulted in multiple re-flashing, so
      long as .ramdisk is present it will boot with rootfs in ramdisk, not
      the sda1.

      Peace,

      Jon.



      --- In nslu2-general@yahoogroups.com, "jrstueve47" <j.stueve@c...> wrote:
      > I have a Maxtor 200GB on Disk1 port (/dev/sda)
      >
      > This is the results of df:
      >
      > # df
      > Filesystem 1k-blocks Used Available Use% Mounted on
      > rootfs 11895 10078 1817 85% /
      > /dev/ram0 6528 5308 1220 81% /initrd
      > /dev/ram0 11895 10078 1817 85% /
      > /dev/sda1 195843204 44064 193809492 0% /share/hdd/data
      > /dev/sda2 116661 4142 111315 4% /share/hdd/conf
      >
      > This ia after a complete wipe of the hard drive, repartitioned using
      > the Linksys interface, and then re-flashing using UpSlug, wiping
      > sysconf in RedBoot. Getting a clean boot, and then turning on the
      > drive, then unslinging per the readme:
      >
      > /sbin/unsling disk1
      >
      > Repeated reboots gets the same df report. I don't want to fill up the
      > flash so I'm not using ipkg.
      >
      > uname -a returns:
      > # uname -a
      > Linux SLUG 2.4.22-xfs #1 Wed May 11 03:50:16 PDT 2005 armv5b unknown
      >
      >
      > Thanks for your help!
      >
      > Jon
    Your message has been successfully submitted and would be delivered to recipients shortly.