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

Input/output error when unslinging v.5.5

Expand Messages
  • driesie2000
    Hi, I previously successfully unslung my nslu2 to version 3.18, and I now tried to update to 5.5 because I wanted to install some packages. Everything goes
    Message 1 of 13 , Jul 5, 2005
    • 0 Attachment
      Hi,

      I previously successfully unslung my nslu2 to version 3.18, and I now
      tried to update to 5.5 because I wanted to install some packages.
      Everything goes fine up to the point I try to unsling it
      (/sbin/unsling disk1). Then I get the following output:
      Target disk is /share/hdd/data
      Copying the complete rootfs from / to /share/hdd/data.
      /usr/bin/cpio:
      /share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb:
      Input/output error
      /usr/bin/cpio: cannot make directory
      `/share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb':
      Input/output error
      /usr/bin/cpio:
      /share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb/kaweth.o: No
      such file or directory
      /usr/bin/cpio: cannot make directory
      `/share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb':
      Input/output error
      ...

      This continues for all the files.
      I'm not sure what is going on, or how to fix this.
      The only "un-standard" part of my setup is that the drive I attached
      has a FAT partition (setup using guidance on:
      http://www.nslu2-linux.org/wiki/HowTo/AttachAFAT32FormattedDrive).
      This worked find in 3.18, but I don't the FAT partition doesn't seem
      to be mounted anymore after the upgrade.

      Does anybody have any ideas?

      Cheers,

      Dries.
    • Gerald L. Clark
      ... You have to wait for the drive to be mounted rw before you unsling. -- nslu-linux - glc
      Message 2 of 13 , Jul 5, 2005
      • 0 Attachment
        driesie2000 wrote:
        > Hi,
        >
        > I previously successfully unslung my nslu2 to version 3.18, and I now
        > tried to update to 5.5 because I wanted to install some packages.
        > Everything goes fine up to the point I try to unsling it
        > (/sbin/unsling disk1). Then I get the following output:
        > Target disk is /share/hdd/data
        > Copying the complete rootfs from / to /share/hdd/data.
        > /usr/bin/cpio:
        > /share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb:
        > Input/output error
        > /usr/bin/cpio: cannot make directory
        > `/share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb':
        > Input/output error
        > /usr/bin/cpio:
        > /share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb/kaweth.o: No
        > such file or directory
        > /usr/bin/cpio: cannot make directory
        > `/share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb':
        > Input/output error
        > ...
        >
        > This continues for all the files.
        > I'm not sure what is going on, or how to fix this.
        > The only "un-standard" part of my setup is that the drive I attached
        > has a FAT partition (setup using guidance on:
        > http://www.nslu2-linux.org/wiki/HowTo/AttachAFAT32FormattedDrive).
        > This worked find in 3.18, but I don't the FAT partition doesn't seem
        > to be mounted anymore after the upgrade.
        >
        > Does anybody have any ideas?
        >
        > Cheers,
        >
        > Dries.
        >
        You have to wait for the drive to be mounted rw before you unsling.

        --
        nslu-linux - glc
      • driesie2000
        ... I have waited for a while (probably 15-20 minutes) before trying to unsling. I can at this stage see the drive through the interface. One thing I just
        Message 3 of 13 , Jul 6, 2005
        • 0 Attachment
          --- In nslu2-linux@yahoogroups.com, "Gerald L. Clark"
          <gerald_clark@m...> wrote:
          > driesie2000 wrote:
          > > Hi,
          > >
          > > I previously successfully unslung my nslu2 to version 3.18, and I now
          > > tried to update to 5.5 because I wanted to install some packages.
          > > Everything goes fine up to the point I try to unsling it
          > > (/sbin/unsling disk1). Then I get the following output:
          > > Target disk is /share/hdd/data
          > > Copying the complete rootfs from / to /share/hdd/data.
          > > /usr/bin/cpio:
          > > /share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb:
          > > Input/output error
          > > /usr/bin/cpio: cannot make directory
          > > `/share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb':
          > > Input/output error
          > > /usr/bin/cpio:
          > > /share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb/kaweth.o: No
          > > such file or directory
          > > /usr/bin/cpio: cannot make directory
          > > `/share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb':
          > > Input/output error
          > > ...
          > >
          > > This continues for all the files.
          > > I'm not sure what is going on, or how to fix this.
          > > The only "un-standard" part of my setup is that the drive I attached
          > > has a FAT partition (setup using guidance on:
          > > http://www.nslu2-linux.org/wiki/HowTo/AttachAFAT32FormattedDrive).
          > > This worked find in 3.18, but I don't the FAT partition doesn't seem
          > > to be mounted anymore after the upgrade.
          > >
          > > Does anybody have any ideas?
          > >
          > > Cheers,
          > >
          > > Dries.
          > >
          > You have to wait for the drive to be mounted rw before you unsling.

          I have waited for a while (probably 15-20 minutes) before trying to
          unsling. I can at this stage see the drive through the interface.
          One thing I just noticed though is that I can't write to the drive via
          smb anymore. I definitly could do this before the upgrade. When I now
          try to create folder for example, in windows, I get the following
          error: "The request could not be performed because of an I/O device
          error". I can however happily read from the drive from windows.
          Not sure if this is usefull information, but when I do a
          fdisk -l /dev/sda

          I get the following result:


          Disk /dev/sda: 255 heads, 63 sectors, 10011 cylinders
          Units = cylinders of 16065 * 512 bytes

          Device Boot Start End Blocks Id System
          /dev/sda1 1 428 3437878+ 83 Linux
          /dev/sda2 9863 10004 1140615 83 Linux
          /dev/sda3 10005 10011 56227+ 82 Linux swap
          /dev/sda4 429 9862 75778605 f Win95 Ext'd (LBA)
          /dev/sda5 429 9862 75778573+ b Win95 FAT32

          Partition table entries are not in disk order

          Do you think the problem is the drive itself? How could the upgrade
          have affected that?

          Cheers,

          Dries.


          > --
          > nslu-linux - glc
        • driesie2000
          ... I have waited plenty time before trying to unsling it. The drive is ready , and I can see and read any files from it, but I just noticed that I can t
          Message 4 of 13 , Jul 6, 2005
          • 0 Attachment
            --- In nslu2-linux@yahoogroups.com, "Gerald L. Clark"
            <gerald_clark@m...> wrote:
            > driesie2000 wrote:
            > > Hi,
            > >
            > > I previously successfully unslung my nslu2 to version 3.18, and I now
            > > tried to update to 5.5 because I wanted to install some packages.
            > > Everything goes fine up to the point I try to unsling it
            > > (/sbin/unsling disk1). Then I get the following output:
            > > Target disk is /share/hdd/data
            > > Copying the complete rootfs from / to /share/hdd/data.
            > > /usr/bin/cpio:
            > > /share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb:
            > > Input/output error
            > > /usr/bin/cpio: cannot make directory
            > > `/share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb':
            > > Input/output error
            > > /usr/bin/cpio:
            > > /share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb/kaweth.o: No
            > > such file or directory
            > > /usr/bin/cpio: cannot make directory
            > > `/share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb':
            > > Input/output error
            > > ...
            > >
            > > This continues for all the files.
            > > I'm not sure what is going on, or how to fix this.
            > > The only "un-standard" part of my setup is that the drive I attached
            > > has a FAT partition (setup using guidance on:
            > > http://www.nslu2-linux.org/wiki/HowTo/AttachAFAT32FormattedDrive).
            > > This worked find in 3.18, but I don't the FAT partition doesn't seem
            > > to be mounted anymore after the upgrade.
            > >
            > > Does anybody have any ideas?
            > >
            > > Cheers,
            > >
            > > Dries.
            > >
            > You have to wait for the drive to be mounted rw before you unsling.

            I have waited plenty time before trying to unsling it.
            The drive is "ready", and I can see and read any files from it, but I
            just noticed that I can't actually write to it from windows either (I
            get a "The request could not be performed because of an I/O device
            error" message).

            So it kind of looks like there is a problem with the disk itself, but
            it definitly worked before the update.

            I'm not sure if this is usefull information, but when I do a:
            fdisk -l /dev/sda
            I get the following result:

            Disk /dev/sda: 255 heads, 63 sectors, 10011 cylinders
            Units = cylinders of 16065 * 512 bytes

            Device Boot Start End Blocks Id System
            /dev/sda1 1 428 3437878+ 83 Linux
            /dev/sda2 9863 10004 1140615 83 Linux
            /dev/sda3 10005 10011 56227+ 82 Linux swap
            /dev/sda4 429 9862 75778605 f Win95 Ext'd (LBA)
            /dev/sda5 429 9862 75778573+ b Win95 FAT32

            Partition table entries are not in disk order



            > --
            > nslu-linux - glc
          • Robert Hammond
            In message , driesie2000 writes ... My disk partitions are similar to yours, I modified the partition before
            Message 5 of 13 , Jul 6, 2005
            • 0 Attachment
              In message <dahfk4+5u50@...>, driesie2000 <yahoo@...>
              writes
              >--- In nslu2-linux@yahoogroups.com, "Gerald L. Clark"
              ><gerald_clark@m...> wrote:
              >> driesie2000 wrote:
              >> > Hi,
              >> >
              >> > I previously successfully unslung my nslu2 to version 3.18, and I now
              >> > tried to update to 5.5 because I wanted to install some packages.
              >> > Everything goes fine up to the point I try to unsling it
              >> > (/sbin/unsling disk1). Then I get the following output:
              >> > Target disk is /share/hdd/data
              >> > Copying the complete rootfs from / to /share/hdd/data.
              >> > /usr/bin/cpio:
              >> > /share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb:
              >> > Input/output error
              >> > /usr/bin/cpio: cannot make directory
              >> > `/share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb':
              >> > Input/output error
              >> > /usr/bin/cpio:
              >> > /share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb/kaweth.o: No
              >> > such file or directory
              >> > /usr/bin/cpio: cannot make directory
              >> > `/share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb':
              >> > Input/output error
              >> > ...
              >> >
              >> > This continues for all the files.
              >> > I'm not sure what is going on, or how to fix this.
              >> > The only "un-standard" part of my setup is that the drive I attached
              >> > has a FAT partition (setup using guidance on:
              >> > http://www.nslu2-linux.org/wiki/HowTo/AttachAFAT32FormattedDrive).
              >> > This worked find in 3.18, but I don't the FAT partition doesn't seem
              >> > to be mounted anymore after the upgrade.
              >> >
              >> > Does anybody have any ideas?
              >> >
              >> > Cheers,
              >> >
              >> > Dries.
              >> >
              >> You have to wait for the drive to be mounted rw before you unsling.
              >
              >I have waited plenty time before trying to unsling it.
              >The drive is "ready", and I can see and read any files from it, but I
              >just noticed that I can't actually write to it from windows either (I
              >get a "The request could not be performed because of an I/O device
              >error" message).
              >
              >So it kind of looks like there is a problem with the disk itself, but
              >it definitly worked before the update.
              >
              >I'm not sure if this is usefull information, but when I do a:
              >fdisk -l /dev/sda
              >I get the following result:
              >
              >Disk /dev/sda: 255 heads, 63 sectors, 10011 cylinders
              >Units = cylinders of 16065 * 512 bytes
              >
              > Device Boot Start End Blocks Id System
              >/dev/sda1 1 428 3437878+ 83 Linux
              >/dev/sda2 9863 10004 1140615 83 Linux
              >/dev/sda3 10005 10011 56227+ 82 Linux swap
              >/dev/sda4 429 9862 75778605 f Win95 Ext'd (LBA)
              >/dev/sda5 429 9862 75778573+ b Win95 FAT32
              >
              >Partition table entries are not in disk order
              >
              >
              My disk partitions are similar to yours, I modified the partition
              before unslinging some time back by adding a fourth fat32. Note that
              I have had no problems during the unslining to ver 5.5

              My output using the above command is :-

              Disk /dev/sda: 255 heads, 63 sectors, 19929 cylinders
              Units = cylinders of 16065 * 512 bytes

              Device Boot Start End Blocks Id System
              /dev/sda1 1 11516 92502238+ 83 Linux
              /dev/sda2 19659 19922 2120580 83 Linux
              /dev/sda3 19923 19929 56227+ 82 Linux swap
              /dev/sda4 11517 19658 65400615 c Win95 FAT32 (LBA)

              Partition table entries are not in disk order



              Suggest that you try the following command and post up the results. I
              think that either one of your mounded drives is ro or it could be that
              the conf partition is not mounting for some reason :-

              cat /proc/mounts

              --
              Robert Hammond
              PGP:0x154144DA
            • Gerald L. Clark
              ... You have to use the mount command to check the drive, not fdisk. If the drive shows as not mounted, or mounted ro, then you cannot unsling.
              Message 6 of 13 , Jul 6, 2005
              • 0 Attachment
                driesie2000 wrote:
                > --- In nslu2-linux@yahoogroups.com, "Gerald L. Clark"
                > <gerald_clark@m...> wrote:
                > > driesie2000 wrote:
                > > > Hi,
                > > >
                > > > I previously successfully unslung my nslu2 to version 3.18, and I now
                > > > tried to update to 5.5 because I wanted to install some packages.
                > > > Everything goes fine up to the point I try to unsling it
                > > > (/sbin/unsling disk1). Then I get the following output:
                > > > Target disk is /share/hdd/data
                > > > Copying the complete rootfs from / to /share/hdd/data.
                > > > /usr/bin/cpio:
                > > > /share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb:
                > > > Input/output error
                > > > /usr/bin/cpio: cannot make directory
                > > > `/share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb':
                > > > Input/output error
                > > > /usr/bin/cpio:
                > > > /share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb/kaweth.o: No
                > > > such file or directory
                > > > /usr/bin/cpio: cannot make directory
                > > > `/share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb':
                > > > Input/output error
                > > > ...
                > > >
                > > > This continues for all the files.
                > > > I'm not sure what is going on, or how to fix this.
                > > > The only "un-standard" part of my setup is that the drive I attached
                > > > has a FAT partition (setup using guidance on:
                > > > http://www.nslu2-linux.org/wiki/HowTo/AttachAFAT32FormattedDrive).
                > > > This worked find in 3.18, but I don't the FAT partition doesn't seem
                > > > to be mounted anymore after the upgrade.
                > > >
                > > > Does anybody have any ideas?
                > > >
                > > > Cheers,
                > > >
                > > > Dries.
                > > >
                > > You have to wait for the drive to be mounted rw before you unsling.
                >
                > I have waited for a while (probably 15-20 minutes) before trying to
                > unsling. I can at this stage see the drive through the interface.
                > One thing I just noticed though is that I can't write to the drive via
                > smb anymore. I definitly could do this before the upgrade. When I now
                > try to create folder for example, in windows, I get the following
                > error: "The request could not be performed because of an I/O device
                > error". I can however happily read from the drive from windows.
                > Not sure if this is usefull information, but when I do a
                > fdisk -l /dev/sda
                >
                > I get the following result:
                >
                >
                > Disk /dev/sda: 255 heads, 63 sectors, 10011 cylinders
                > Units = cylinders of 16065 * 512 bytes
                >
                > Device Boot Start End Blocks Id System
                > /dev/sda1 1 428 3437878+ 83 Linux
                > /dev/sda2 9863 10004 1140615 83 Linux
                > /dev/sda3 10005 10011 56227+ 82 Linux swap
                > /dev/sda4 429 9862 75778605 f Win95 Ext'd (LBA)
                > /dev/sda5 429 9862 75778573+ b Win95 FAT32
                >
                > Partition table entries are not in disk order
                >
                > Do you think the problem is the drive itself? How could the upgrade
                > have affected that?
                >
                > Cheers,
                >
                > Dries.
                >
                >
                > > --
                > > nslu-linux - glc
                >
                You have to use the mount command to check the drive, not fdisk.

                If the drive shows as not mounted, or mounted ro, then you cannot unsling.
              • driesie2000
                ... I now ... /share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb/kaweth.o: No ... attached ... seem ... Thanks for the help!! The result of the above
                Message 7 of 13 , Jul 7, 2005
                • 0 Attachment
                  --- In nslu2-linux@yahoogroups.com, Robert Hammond <rob.hammond@n...>
                  wrote:
                  > In message <dahfk4+5u50@e...>, driesie2000 <yahoo@d...>
                  > writes
                  > >--- In nslu2-linux@yahoogroups.com, "Gerald L. Clark"
                  > ><gerald_clark@m...> wrote:
                  > >> driesie2000 wrote:
                  > >> > Hi,
                  > >> >
                  > >> > I previously successfully unslung my nslu2 to version 3.18, and
                  I now
                  > >> > tried to update to 5.5 because I wanted to install some packages.
                  > >> > Everything goes fine up to the point I try to unsling it
                  > >> > (/sbin/unsling disk1). Then I get the following output:
                  > >> > Target disk is /share/hdd/data
                  > >> > Copying the complete rootfs from / to /share/hdd/data.
                  > >> > /usr/bin/cpio:
                  > >> > /share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb:
                  > >> > Input/output error
                  > >> > /usr/bin/cpio: cannot make directory
                  > >> > `/share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb':
                  > >> > Input/output error
                  > >> > /usr/bin/cpio:
                  > >> >
                  /share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb/kaweth.o: No
                  > >> > such file or directory
                  > >> > /usr/bin/cpio: cannot make directory
                  > >> > `/share/hdd/data/lib/modules/2.4.22-xfs/kernel/drivers/usb':
                  > >> > Input/output error
                  > >> > ...
                  > >> >
                  > >> > This continues for all the files.
                  > >> > I'm not sure what is going on, or how to fix this.
                  > >> > The only "un-standard" part of my setup is that the drive I
                  attached
                  > >> > has a FAT partition (setup using guidance on:
                  > >> > http://www.nslu2-linux.org/wiki/HowTo/AttachAFAT32FormattedDrive).
                  > >> > This worked find in 3.18, but I don't the FAT partition doesn't
                  seem
                  > >> > to be mounted anymore after the upgrade.
                  > >> >
                  > >> > Does anybody have any ideas?
                  > >> >
                  > >> > Cheers,
                  > >> >
                  > >> > Dries.
                  > >> >
                  > >> You have to wait for the drive to be mounted rw before you unsling.
                  > >
                  > >I have waited plenty time before trying to unsling it.
                  > >The drive is "ready", and I can see and read any files from it, but I
                  > >just noticed that I can't actually write to it from windows either (I
                  > >get a "The request could not be performed because of an I/O device
                  > >error" message).
                  > >
                  > >So it kind of looks like there is a problem with the disk itself, but
                  > >it definitly worked before the update.
                  > >
                  > >I'm not sure if this is usefull information, but when I do a:
                  > >fdisk -l /dev/sda
                  > >I get the following result:
                  > >
                  > >Disk /dev/sda: 255 heads, 63 sectors, 10011 cylinders
                  > >Units = cylinders of 16065 * 512 bytes
                  > >
                  > > Device Boot Start End Blocks Id System
                  > >/dev/sda1 1 428 3437878+ 83 Linux
                  > >/dev/sda2 9863 10004 1140615 83 Linux
                  > >/dev/sda3 10005 10011 56227+ 82 Linux swap
                  > >/dev/sda4 429 9862 75778605 f Win95 Ext'd (LBA)
                  > >/dev/sda5 429 9862 75778573+ b Win95 FAT32
                  > >
                  > >Partition table entries are not in disk order
                  > >
                  > >
                  > My disk partitions are similar to yours, I modified the partition
                  > before unslinging some time back by adding a fourth fat32. Note that
                  > I have had no problems during the unslining to ver 5.5
                  >
                  > My output using the above command is :-
                  >
                  > Disk /dev/sda: 255 heads, 63 sectors, 19929 cylinders
                  > Units = cylinders of 16065 * 512 bytes
                  >
                  > Device Boot Start End Blocks Id System
                  > /dev/sda1 1 11516 92502238+ 83 Linux
                  > /dev/sda2 19659 19922 2120580 83 Linux
                  > /dev/sda3 19923 19929 56227+ 82 Linux swap
                  > /dev/sda4 11517 19658 65400615 c Win95 FAT32 (LBA)
                  >
                  > Partition table entries are not in disk order
                  >
                  >
                  >
                  > Suggest that you try the following command and post up the results. I
                  > think that either one of your mounded drives is ro or it could be that
                  > the conf partition is not mounting for some reason :-
                  >
                  > cat /proc/mounts


                  Thanks for the help!!

                  The result of the above command is:
                  # cat /proc/mounts
                  rootfs / rootfs rw 0 0
                  /dev/root / jffs2 rw 0 0
                  /proc /proc proc rw 0 0
                  usbdevfs /proc/bus/usb usbdevfs rw 0 0
                  /dev/root /dev.state jffs2 rw 0 0
                  ramfs /dev ramfs rw 0 0
                  /dev/root /var.state jffs2 rw 0 0
                  ramfs /var ramfs rw 0 0
                  none /tmp ramfs rw 0 0
                  /dev/sda1 /share/hdd/data ext3 rw 0 0
                  /dev/sda2 /share/hdd/conf ext3 rw,sync 0 0


                  Sorry, I'm don't know much about linux, so I have no idea what that means.
                • Gerald L. Clark
                  ... Your drives are now mounted rw (read/write). You should be able to : unsling disk1
                  Message 8 of 13 , Jul 7, 2005
                  • 0 Attachment
                    >
                    > Thanks for the help!!
                    >
                    > The result of the above command is:
                    > # cat /proc/mounts
                    > rootfs / rootfs rw 0 0
                    > /dev/root / jffs2 rw 0 0
                    > /proc /proc proc rw 0 0
                    > usbdevfs /proc/bus/usb usbdevfs rw 0 0
                    > /dev/root /dev.state jffs2 rw 0 0
                    > ramfs /dev ramfs rw 0 0
                    > /dev/root /var.state jffs2 rw 0 0
                    > ramfs /var ramfs rw 0 0
                    > none /tmp ramfs rw 0 0

                    > /dev/sda1 /share/hdd/data ext3 rw 0 0
                    > /dev/sda2 /share/hdd/conf ext3 rw,sync 0 0
                    Your drives are now mounted rw (read/write).
                    You should be able to :
                    unsling disk1
                    >
                    >
                    > Sorry, I'm don't know much about linux, so I have no idea what that means.
                    >
                  • Gerald L. Clark
                    ... I/O errors are usually hardware problems. Your drive may be bad, or your file system may be pointing to blocks past the end of the drive.
                    Message 9 of 13 , Jul 8, 2005
                    • 0 Attachment
                      driesie2000 wrote:
                      > --- In nslu2-linux@yahoogroups.com, "Gerald L. Clark"
                      > <gerald_clark@m...> wrote:
                      > >
                      > > >
                      > > > Thanks for the help!!
                      > > >
                      > > > The result of the above command is:
                      > > > # cat /proc/mounts
                      > > > rootfs / rootfs rw 0 0
                      > > > /dev/root / jffs2 rw 0 0
                      > > > /proc /proc proc rw 0 0
                      > > > usbdevfs /proc/bus/usb usbdevfs rw 0 0
                      > > > /dev/root /dev.state jffs2 rw 0 0
                      > > > ramfs /dev ramfs rw 0 0
                      > > > /dev/root /var.state jffs2 rw 0 0
                      > > > ramfs /var ramfs rw 0 0
                      > > > none /tmp ramfs rw 0 0
                      > >
                      > > > /dev/sda1 /share/hdd/data ext3 rw 0 0
                      > > > /dev/sda2 /share/hdd/conf ext3 rw,sync 0 0
                      > > Your drives are now mounted rw (read/write).
                      > > You should be able to :
                      > > unsling disk1
                      >
                      > I still am not able to though. I get the Input/output error when I try
                      > to do so.
                      >

                      I/O errors are usually hardware problems. Your drive may be bad, or your
                      file system may be pointing to blocks past the end of the drive.

                      > I've been thinking maybe I should get a 256Mb flash memory stick as my
                      > unslung drive instead. Then I can just mount my FAT32 HD not having to
                      > wory about trying to unsling on a partition of that drive. Does that
                      > sound like a good idea?
                      >
                    • driesie2000
                      ... I still am not able to though. I get the Input/output error when I try to do so. I ve been thinking maybe I should get a 256Mb flash memory stick as my
                      Message 10 of 13 , Jul 8, 2005
                      • 0 Attachment
                        --- In nslu2-linux@yahoogroups.com, "Gerald L. Clark"
                        <gerald_clark@m...> wrote:
                        >
                        > >
                        > > Thanks for the help!!
                        > >
                        > > The result of the above command is:
                        > > # cat /proc/mounts
                        > > rootfs / rootfs rw 0 0
                        > > /dev/root / jffs2 rw 0 0
                        > > /proc /proc proc rw 0 0
                        > > usbdevfs /proc/bus/usb usbdevfs rw 0 0
                        > > /dev/root /dev.state jffs2 rw 0 0
                        > > ramfs /dev ramfs rw 0 0
                        > > /dev/root /var.state jffs2 rw 0 0
                        > > ramfs /var ramfs rw 0 0
                        > > none /tmp ramfs rw 0 0
                        >
                        > > /dev/sda1 /share/hdd/data ext3 rw 0 0
                        > > /dev/sda2 /share/hdd/conf ext3 rw,sync 0 0
                        > Your drives are now mounted rw (read/write).
                        > You should be able to :
                        > unsling disk1

                        I still am not able to though. I get the Input/output error when I try
                        to do so.

                        I've been thinking maybe I should get a 256Mb flash memory stick as my
                        unslung drive instead. Then I can just mount my FAT32 HD not having to
                        wory about trying to unsling on a partition of that drive. Does that
                        sound like a good idea?
                      • Rod Whitby
                        ... The only time I had I/O errors with Unslung was when my 2.5inch USB enclosure was not getting enough power from the slug. Once I powered it independently
                        Message 11 of 13 , Jul 9, 2005
                        • 0 Attachment
                          On 7/9/05, Gerald L. Clark <gerald_clark@...> wrote:
                          > I/O errors are usually hardware problems. Your drive may be bad, or your
                          > file system may be pointing to blocks past the end of the drive.

                          The only time I had I/O errors with Unslung was when my 2.5inch USB
                          enclosure was not getting enough power from the slug. Once I powered
                          it independently from the slug, then everything worked perfectly for
                          that drive.

                          -- Rod
                        • driesie2000
                          ... or your ... Mine is a regular 3.5 drive enclosure, with seperate power supply. I don t think there s a hardware issue with the drive as I can read the FAT
                          Message 12 of 13 , Jul 11, 2005
                          • 0 Attachment
                            --- In nslu2-linux@yahoogroups.com, Rod Whitby <list.yahoo@r...> wrote:
                            > On 7/9/05, Gerald L. Clark <gerald_clark@m...> wrote:
                            > > I/O errors are usually hardware problems. Your drive may be bad,
                            or your
                            > > file system may be pointing to blocks past the end of the drive.
                            >
                            > The only time I had I/O errors with Unslung was when my 2.5inch USB
                            > enclosure was not getting enough power from the slug. Once I powered
                            > it independently from the slug, then everything worked perfectly for
                            > that drive.

                            Mine is a regular 3.5" drive enclosure, with seperate power supply. I
                            don't think there's a hardware issue with the drive as I can read the
                            FAT partition fine using a direct USB connection to my PC. I haven't
                            (can't really) tested the linux partitions, so maybe there's an issue
                            there.
                            Thanks for all help though. I think I might try to unling onto a flash
                            memory drive, and just use the FAT part of the USB HD to store files on.

                            Dries.
                          • S├ębastien Bernard
                            I just had the same problem, same message, 2 days ago. On a good hard disk, with an independent alimentation for my usb. My solution, and it worked perfectly:
                            Message 13 of 13 , Sep 2, 2005
                            • 0 Attachment
                              I just had the same problem, same message, 2 days ago. On a good hard
                              disk, with an independent alimentation for my usb.

                              My solution, and it worked perfectly:

                              Stop my nslu2.
                              Plug my HDD direct on my windows machine.
                              Use Paragon Drive Manager to delete the 3 partitions of the disk, just
                              delete them.

                              Start the "Unsling" part again, but reformat the HDD when they say to
                              do it on the installation paper, and IT WORKS direct.

                              Why ? no important.
                            Your message has been successfully submitted and would be delivered to recipients shortly.