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

initrd getting full...

Expand Messages
  • jim_nslu
    I m trying to set up my slug with Raid1, as per the instructions at http://www.nslu2-linux.org/wiki/HowTo/Raid1onUnslung6 Currently, I ve not got much
    Message 1 of 3 , Jul 2, 2007
    • 0 Attachment
      I'm trying to set up my slug with Raid1, as per the instructions at
      http://www.nslu2-linux.org/wiki/HowTo/Raid1onUnslung6

      Currently, I've not got much installed - OpenSSH is basically it.

      I've got a pair of 320Gb WD Essential drives attached, and I have
      unslung to Disk1 (sdb).

      Running df reports the following disk usage:

      # df
      Filesystem 1k-blocks Used Available Use% Mounted on
      rootfs 307426936 58556 304245104 0% /
      /dev/sdb1 6528 6368 160 98% /initrd
      /dev/sdb1 307426936 58556 304245104 0% /
      /dev/sda1 1185768 77652 1047880 7% /share/flash/data
      /dev/sdb1 307426936 58556 304245104 0% /share/hdd/data
      /dev/sdb2 116661 4144 111313 4% /share/hdd/conf
      /dev/sdb2 116661 4144 111313 4% /share/flash/conf

      So initrd appears to only have about 6Mb of disk space allocated to
      it, and it is 98% full, meaning that there's not sufficient space to
      copy in the files necessary to run Raid1.

      The only way that I have differed from the Raid1 instructions (above)
      is to have unslung to sdb instead of sda, and I presume that doen't
      require me to make any changes to the /dev/md4, /dev/md3 /dev/md2 and
      /dev/md1 paths.

      Has anybody else had this problem, and is there any simple way that I
      can deal with this?

      Thanks.


      Jim
    • creisor
      ... /share/flash/data ... /share/flash/conf ... Sorry if this is a repeat...I replied on Nabble before realizing it forwards to this list, so I joined this
      Message 2 of 3 , Nov 14, 2007
      • 0 Attachment
        --- In nslu2-general@yahoogroups.com, "jim_nslu" <jim_nslu@...> wrote:
        >
        > I'm trying to set up my slug with Raid1, as per the instructions at
        > http://www.nslu2-linux.org/wiki/HowTo/Raid1onUnslung6
        >
        > Currently, I've not got much installed - OpenSSH is basically it.
        >
        > I've got a pair of 320Gb WD Essential drives attached, and I have
        > unslung to Disk1 (sdb).
        >
        > Running df reports the following disk usage:
        >
        > # df
        > Filesystem 1k-blocks Used Available Use% Mounted on
        > rootfs 307426936 58556 304245104 0% /
        > /dev/sdb1 6528 6368 160 98% /initrd
        > /dev/sdb1 307426936 58556 304245104 0% /
        > /dev/sda1 1185768 77652 1047880 7%
        /share/flash/data
        > /dev/sdb1 307426936 58556 304245104 0% /share/hdd/data
        > /dev/sdb2 116661 4144 111313 4% /share/hdd/conf
        > /dev/sdb2 116661 4144 111313 4%
        /share/flash/conf
        >
        > So initrd appears to only have about 6Mb of disk space allocated to
        > it, and it is 98% full, meaning that there's not sufficient space to
        > copy in the files necessary to run Raid1.
        >
        > The only way that I have differed from the Raid1 instructions (above)
        > is to have unslung to sdb instead of sda, and I presume that doen't
        > require me to make any changes to the /dev/md4, /dev/md3 /dev/md2 and
        > /dev/md1 paths.
        >

        Sorry if this is a repeat...I replied on Nabble before realizing it
        forwards to this list, so I joined this list and will re-post:

        Did you ever get your answer? I have the *exact* same setup, even the
        same brand and size of drives. I unslung to drive 1, just like you.
        My initrd size varies from yours by 1%, but like you, there's not
        enough room to copy md.o, raid1.o, and mdadm to /initrd/unslung:

        bash-3.2# df -k
        Filesystem 1k-blocks Used Available Use% Mounted on
        rootfs 307426936 53704 304249956 0% /
        /dev/sdb1 6528 6332 196 97% /initrd
        /dev/sdb1 307426936 53704 304249956 0% /
        /dev/sdb1 307426936 53704 304249956 0% /share/hdd/data
        /dev/sdb2 116661 4144 111313 4% /share/hdd/conf
        /dev/sdb2 116661 4144 111313 4% /share/flash/conf

        I'll keep plugging away at this and reply back if I come up with the
        answer.
      • Robert Hammond
        In message , creisor writes ... Firstly, the Older Unslung version 5.5 firmware is smaller, on my machine takes
        Message 3 of 3 , Nov 15, 2007
        • 0 Attachment
          In message <fhgkv0+nuqv@...>, creisor <creisor@...> writes
          >--- In nslu2-general@yahoogroups.com, "jim_nslu" <jim_nslu@...> wrote:
          >>
          >> I'm trying to set up my slug with Raid1, as per the instructions at
          >> http://www.nslu2-linux.org/wiki/HowTo/Raid1onUnslung6
          >>
          >> Currently, I've not got much installed - OpenSSH is basically it.
          >>
          >> I've got a pair of 320Gb WD Essential drives attached, and I have
          >> unslung to Disk1 (sdb).
          >>
          >> Running df reports the following disk usage:
          >>
          >> # df
          >> Filesystem 1k-blocks Used Available Use% Mounted on
          >> rootfs 307426936 58556 304245104 0% /
          >> /dev/sdb1 6528 6368 160 98% /initrd
          >> /dev/sdb1 307426936 58556 304245104 0% /
          >> /dev/sda1 1185768 77652 1047880 7%
          >/share/flash/data
          >> /dev/sdb1 307426936 58556 304245104 0% /share/hdd/data
          >> /dev/sdb2 116661 4144 111313 4% /share/hdd/conf
          >> /dev/sdb2 116661 4144 111313 4%
          >/share/flash/conf
          >>
          >> So initrd appears to only have about 6Mb of disk space allocated to
          >> it, and it is 98% full, meaning that there's not sufficient space to
          >> copy in the files necessary to run Raid1.
          >>
          >> The only way that I have differed from the Raid1 instructions (above)
          >> is to have unslung to sdb instead of sda, and I presume that doen't
          >> require me to make any changes to the /dev/md4, /dev/md3 /dev/md2 and
          >> /dev/md1 paths.
          >>
          >
          >Sorry if this is a repeat...I replied on Nabble before realizing it
          >forwards to this list, so I joined this list and will re-post:
          >
          >Did you ever get your answer? I have the *exact* same setup, even the
          >same brand and size of drives. I unslung to drive 1, just like you.
          >My initrd size varies from yours by 1%, but like you, there's not
          >enough room to copy md.o, raid1.o, and mdadm to /initrd/unslung:
          >
          >bash-3.2# df -k
          >Filesystem 1k-blocks Used Available Use% Mounted on
          >rootfs 307426936 53704 304249956 0% /
          >/dev/sdb1 6528 6332 196 97% /initrd
          >/dev/sdb1 307426936 53704 304249956 0% /
          >/dev/sdb1 307426936 53704 304249956 0% /share/hdd/data
          >/dev/sdb2 116661 4144 111313 4% /share/hdd/conf
          >/dev/sdb2 116661 4144 111313 4% /share/flash/conf
          >
          >I'll keep plugging away at this and reply back if I come up with the
          >answer.
          >
          Firstly, the Older Unslung version 5.5 firmware is smaller, on my
          machine takes up only 82% but to be aware that with version 5.5 there
          seems to be an upper fill limit of about 95%, filling the flash more
          than this seem to make the NSLU2 freeze during the boot process, only
          recoverable by re-flashing.


          /initrd is the Slugs internal flash ram where the firmware is stored.
          I have seen some posts some time back that seem to show which files in
          this folder tree can be safely delete to free up more room when using
          Unslung version 6. From memory I think that the relevant messages had
          something to do with the weather station project so you may want to try
          searching for messages on this theme.
          --
          Robert Hammond
          PGP:0x154144DA
        Your message has been successfully submitted and would be delivered to recipients shortly.