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

Re: [nslu2-general] Checking if rootfs is on disk after unslinging.

Expand Messages
  • Rod Whitby
    ... Correct. Look at the rootfs and / lines, and ignore the /initrd line. If the size of rootfs and / reflects the size of your disk s data partition, then
    Message 1 of 9 , Aug 1 3:03 PM
    • 0 Attachment
      On 8/2/05, Mattias <mattias@...> wrote:
      > The row containing: /dev/sda1 9656956 45856
      > 9512992 0% /
      > must mean that my rootfs lies on usbdisk1 and partition 1 as it should,
      > or am I wrong?

      Correct. Look at the rootfs and / lines, and ignore the /initrd line.

      If the size of rootfs and / reflects the size of your disk's data
      partition, then you are good.

      Please add this to the FAQ.

      -- Rod
    • mike_pruis
      ... 45856 ... should, ... And what do you do if the rootfs isnt on the new drive? I have upgraded firmware, unslung and all (and had drives not-attached when
      Message 2 of 9 , Aug 8 12:29 PM
      • 0 Attachment
        --- In nslu2-general@yahoogroups.com, Rod Whitby <list.yahoo@r...> wrote:
        > On 8/2/05, Mattias <mattias@i...> wrote:
        > > The row containing: /dev/sda1 9656956
        45856
        > > 9512992 0% /
        > > must mean that my rootfs lies on usbdisk1 and partition 1 as it
        should,
        > > or am I wrong?
        >
        > Correct. Look at the rootfs and / lines, and ignore the /initrd line.
        >
        > If the size of rootfs and / reflects the size of your disk's data
        > partition, then you are good.
        >
        > Please add this to the FAQ.
        >
        > -- Rod

        And what do you do if the rootfs isnt on the new drive?
        I have upgraded firmware, unslung and all (and had drives not-attached
        when told) but the unsling script (probably) didn't work correctly?

        this is the result of the df command:
        # df
        Filesystem 1k-blocks Used Available Use% Mounted on
        rootfs 6528 5324 1204 82% /
        /dev/mtdblock4 6528 5324 1204 82% /
        /dev/sda1 299681 18359 278228 6% /share/hdd/data
        /dev/sda2 123923 4142 118502 3% /share/hdd/conf

        I want to unsling my 512MB memstick, which is on port 1 and formatted
        using the slug... copying of all files seemed to go okay and the
        script didn't show any error (as far as my newbie unix skilz would
        allow me to understand)...

        please help?

        greetz,

        Mike
      • Rod Whitby
        Did you reboot the slug (with the same disk attached to the same port) after running the unsling command? If so, and it still doesn t load the rootfs from the
        Message 3 of 9 , Aug 8 8:47 PM
        • 0 Attachment
          Did you reboot the slug (with the same disk attached to the same port)
          after running the unsling command?

          If so, and it still doesn't load the rootfs from the external disk,
          please post the result of "ls -la /" and "ls -la /initrd".

          -- Rod

          On 8/9/05, mike_pruis <mike_pruis@...> wrote:
          > And what do you do if the rootfs isnt on the new drive?
          > I have upgraded firmware, unslung and all (and had drives not-attached
          > when told) but the unsling script (probably) didn't work correctly?
          >
          > this is the result of the df command:
          > # df
          > Filesystem 1k-blocks Used Available Use% Mounted on
          > rootfs 6528 5324 1204 82% /
          > /dev/mtdblock4 6528 5324 1204 82% /
          > /dev/sda1 299681 18359 278228 6% /share/hdd/data
          > /dev/sda2 123923 4142 118502 3% /share/hdd/conf
          >
          > I want to unsling my 512MB memstick, which is on port 1 and formatted
          > using the slug... copying of all files seemed to go okay and the
          > script didn't show any error (as far as my newbie unix skilz would
          > allow me to understand)...
        • mike_pruis
          Yep I did a reboot... in the mean time I have done the whole proces again (reflash/reformatted/re...): same problem... here my latest output - from before and
          Message 4 of 9 , Aug 9 2:51 AM
          • 0 Attachment
            Yep I did a reboot...
            in the mean time I have done the whole proces again
            (reflash/reformatted/re...): same problem...
            here my latest output - from before and after the reboot...

            anyone have any ideas?

            >>>

            Rivendel login: root
            Password:
            No directory, logging in with HOME=/


            BusyBox v0.60.4 (2004.07.01-03:05+0000) Built-in shell (ash)
            Enter 'help' for a list of built-in commands.

            # /sbin/unsling disk1
            Target disk is /share/hdd/data
            Copying the complete rootfs from / to /share/hdd/data.
            19123 blocks
            Linking /usr/bin/ipkg executable on target disk.
            Creating /.sda1root to direct switchbox to boot from /share/hdd/data.
            # cp /etc/passwd /share/hdd/conf/passwd
            # df
            Filesystem 1k-blocks Used Available Use% Mounted on
            rootfs 6528 5324 1204 82% /
            /dev/mtdblock4 6528 5324 1204 82% /
            /dev/sda2 123923 4142 118502
            3% /share/hdd/conf
            /dev/sda1 299681 18239 278348
            6% /share/hdd/data
            #

            AFTER REBOOT >>>

            # df
            Filesystem 1k-blocks Used Available Use% Mounted on
            rootfs 6528 5324 1204 82% /
            /dev/mtdblock4 6528 5324 1204 82% /
            /dev/sda1 299681 18256 278331
            6% /share/hdd/data
            /dev/sda2 123923 4142 118502
            3% /share/hdd/conf
            # ls -la /
            drwxr-xr-x 1 root root 0 Aug 9 11:47 .
            drwxr-xr-x 1 root root 0 Aug 9 11:47 ..
            -rw-r--r-- 1 root root 1 Aug 9 11:47 .sda1root
            -rw-rw-r-- 1 root root 25 Jan 1 1970 .unslung
            drwxrwxr-x 1 root root 0 Jan 1 1970 bin
            drwxrwxr-x 1 root root 0 Jan 1 1970 dev
            drwxr-xr-x 1 root root 0 Jan 1 1970 dev.state
            drwxr-xr-x 1 root root 0 Aug 9 11:53 etc
            drwxrwxr-x 1 root root 0 Jan 1 1970 home
            drwxr-xr-x 1 root root 0 Jan 1 1970 initrd
            drwxrwxr-x 1 root root 0 Jan 1 1970 lib
            -rwxr-xr-x 1 root root 3685 Jan 1 1970 linuxrc
            drwxr-xr-x 1 root root 0 Jan 1 1970 lost+found
            drwxrwxr-x 1 root root 0 Jan 1 1970 mnt
            drwxrwxr-x 1 root root 0 Jan 1 1970 opt
            dr-xr-xr-x 52 root root 0 Jan 1 1970 proc
            drwxrwxr-x 1 root root 0 Jan 1 1970 sbin
            drwxrwxr-x 1 admin everyone 0 Aug 9 01:15 share
            drwxrwxrwt 1 root root 0 Aug 9 11:53 tmp
            drwxr-xr-x 1 root root 0 Jan 1 1970 unslung
            drwxr-xr-x 1 root root 0 Jan 1 1970 upload
            drwxrwxr-x 1 root root 0 Jan 1 1970 usr
            drwxrwxr-x 1 root root 0 Jan 1 1970 var
            drwxr-xr-x 1 root root 0 Jan 1 1970 var.state
            # ls -la /initrd
            drwxr-xr-x 1 root root 0 Jan 1 1970 .
            drwxr-xr-x 1 root root 0 Aug 9 11:47 ..




            --- In nslu2-general@yahoogroups.com, Rod Whitby <list.yahoo@r...>
            wrote:
            > Did you reboot the slug (with the same disk attached to the same
            port)
            > after running the unsling command?
            >
            > If so, and it still doesn't load the rootfs from the external disk,
            > please post the result of "ls -la /" and "ls -la /initrd".
            >
            > -- Rod
            >
            > On 8/9/05, mike_pruis <mike_pruis@h...> wrote:
            > > And what do you do if the rootfs isnt on the new drive?
            > > I have upgraded firmware, unslung and all (and had drives not-
            attached
            > > when told) but the unsling script (probably) didn't work
            correctly?
            > >
            > > this is the result of the df command:
            > > # df
            > > Filesystem 1k-blocks Used Available Use% Mounted on
            > > rootfs 6528 5324 1204 82% /
            > > /dev/mtdblock4 6528 5324 1204 82% /
            > > /dev/sda1 299681 18359 278228
            6% /share/hdd/data
            > > /dev/sda2 123923 4142 118502
            3% /share/hdd/conf
            > >
            > > I want to unsling my 512MB memstick, which is on port 1 and
            formatted
            > > using the slug... copying of all files seemed to go okay and the
            > > script didn't show any error (as far as my newbie unix skilz would
            > > allow me to understand)...
          • Inge B. Arnesen
            ... Yeah - probably a long shot, but it could be that the disk is not ready within the boot delay period, so the flash is started as rootfs instead as no disk
            Message 5 of 9 , Aug 9 4:56 AM
            • 0 Attachment
              > Yep I did a reboot...
              > in the mean time I have done the whole proces again
              > (reflash/reformatted/re...): same problem...
              > here my latest output - from before and after the reboot...
              >
              > anyone have any ideas?

              Yeah - probably a long shot, but it could be that the disk is not ready
              within the boot delay period, so the flash is started as rootfs instead as
              no disk is detected. Then, when the disk becomes ready it generates the
              hd_conn pseudofile and is detected by the Linksys automount SW which then
              mounts it as usual (under /share/hdd).

              The reason I don't quite believe this is that the delay is already quite
              large. If you had a serial connnection (you don't, do you?) you could see
              the boot statements, but I don't think the echo-statements from /linuxrc
              is stored anywhere (help me out here guys)?

              best,

              -- Inge
            • Rod Whitby
              ... Reboot again, and as soon as you get in, grab the output from dmesg and post that here. That will identify whether it s a slow disk or not. BTW, we ll
              Message 6 of 9 , Aug 9 6:22 AM
              • 0 Attachment
                On 8/9/05, mike_pruis <mike_pruis@...> wrote:
                > Yep I did a reboot...
                > in the mean time I have done the whole proces again
                > (reflash/reformatted/re...): same problem...
                > here my latest output - from before and after the reboot...

                Reboot again, and as soon as you get in, grab the output from "dmesg"
                and post that here. That will identify whether it's a slow disk or
                not.

                BTW, we'll be asking you to write up these troubleshooting steps on the wiki ...

                -- Rod
              • mike_pruis
                ok guys/girls, thnx for the help.. I d be happy to update the wiki... as soon as I know how :-) I will at minimum present it in a readable form and hope
                Message 7 of 9 , Aug 9 10:20 AM
                • 0 Attachment
                  ok guys/girls, thnx for the help.. I'd be happy to update the wiki...
                  as soon as I know how :-) I will at minimum present it in a readable
                  form and hope someone will help me wiki it...

                  Ok.. rebooted the slug, enabled telnet, logged in as root and did a
                  dmesg... and here's gibberish it returned (at least for me it is :-):


                  # dmesg
                  Linux version 2.4.22-xfs (unslung@...) (gcc version 3.4.4) #1
                  Sun Jun 12
                  21:17:17 PDT 2005
                  CPU: XScale-IXP425/IXC1100 revision 1
                  Machine: Intel IXDP425 Development Platform
                  Warning: bad configuration page, trying to continue
                  Security risk: creating user accessible mapping for 0x60000000 at
                  0xff00f000
                  Security risk: creating user accessible mapping for 0x51000000 at
                  0xf1000000
                  On node 0 totalpages: 8192
                  zone(0): 8192 pages.
                  zone(1): 0 pages.
                  zone(2): 0 pages.
                  Kernel command line: console=ttyS0,115200n8 root=/dev/mtdblock4
                  rootfstype=jffs2
                  rw init=/linuxrc mem=32M@0x00000000
                  Relocating machine vectors to 0xffff0000
                  Calibrating delay loop... 131.48 BogoMIPS
                  Memory: 32MB = 32MB total
                  Memory: 30276KB available (1582K code, 274K data, 244K init)
                  Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
                  Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
                  Mount cache hash table entries: 512 (order: 0, 4096 bytes)
                  Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
                  Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
                  POSIX conformance testing by UNIFIX
                  PCI Autoconfig: Found Bus 0, Device 1, Function 0
                  PCI Autoconfig: BAR 0, Mem, size=0x1000, address=0x4bfff000
                  PCI Autoconfig: Found Bus 0, Device 1, Function 1
                  PCI Autoconfig: BAR 0, Mem, size=0x1000, address=0x4bffe000
                  PCI Autoconfig: Found Bus 0, Device 1, Function 2
                  PCI Autoconfig: BAR 0, Mem, size=0x100, address=0x4bffdf00
                  PCI: bus0: Fast back to back transfers disabled
                  Linux NET4.0 for Linux 2.4
                  Based upon Swansea University Computer Society NET3.039
                  Initializing RT netlink socket
                  Starting kswapd
                  VFS: Disk quotas vdquot_6.5.1
                  Journalled Block Device driver loaded
                  devfs: v1.12c (20020818) Richard Gooch (rgooch@...)
                  devfs: boot_options: 0x0
                  Installing knfsd (copyright (C) 1996 okir@...).
                  JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis
                  Communications AB.
                  i2c-core.o: i2c core module
                  i2c-dev.o: i2c /dev entries driver module
                  i2c-core.o: driver i2c-dev dummy driver registered.
                  i2c-algo-bit.o: i2c bit algorithm module version 2.6.1 (20010830)
                  pty: 256 Unix98 ptys configured
                  Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ
                  SERIAL_PCI en
                  abled
                  ttyS00 at 0xff000003 (irq = 15) is a XScale UART
                  ttyS01 at 0xff001003 (irq = 13) is a XScale UART
                  RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
                  loop: loaded (max 8 devices)
                  SCSI subsystem driver Revision: 1.00
                  * host:<NULL>
                  IXP425 Flash: Found an alias at 0x800000 for the chip at 0x0
                  cfi_cmdset_0001: Erase suspend on write enabled
                  0: offset=0x0,size=0x20000,blocks=64
                  Using buffer write method
                  Creating 6 MTD partitions on "IXP425 Flash":
                  0x00000000-0x00040000 : "RedBoot"
                  0x00040000-0x00060000 : "SysConf"
                  0x00060000-0x00160000 : "Kernel"
                  0x00160000-0x00180000 : "Ramdisk"
                  0x00180000-0x007e0000 : "Flashdisk"
                  0x007e0000-0x00800000 : "FIS directory"
                  usb.c: registered new driver usbdevfs
                  usb.c: registered new driver hub
                  pci probe begin
                  ehci_hcd 00:01.2: NEC Corporation USB 2.0
                  ehci_hcd 00:01.2: irq 26, pci mem c3872f00
                  usb.c: new USB bus registered, assigned bus number 1
                  PCI: 00:01.2 PCI cache line size set incorrectly (0 bytes) by BIOS/FW.
                  PCI: 00:01.2 PCI cache line size corrected to 32.
                  ehci_hcd 00:01.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-19/2.4
                  hub.c: USB hub found
                  hub.c: 5 ports detected
                  pci probe ok
                  host/usb-uhci.c: $Revision: 1.1 $ time 21:18:46 Jun 12 2005
                  host/usb-uhci.c: High bandwidth mode enabled
                  host/usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
                  host/usb-ohci.c: USB OHCI at membase 0xc387a000, IRQ 28
                  host/usb-ohci.c: usb-00:01.0, NEC Corporation USB
                  usb.c: new USB bus registered, assigned bus number 2
                  hub.c: USB hub found
                  hub.c: 3 ports detected
                  host/usb-ohci.c: USB OHCI at membase 0xc3880000, IRQ 27
                  host/usb-ohci.c: usb-00:01.1, NEC Corporation USB (#2)
                  usb.c: new USB bus registered, assigned bus number 3
                  hub.c: USB hub found
                  hub.c: 2 ports detected
                  Initializing USB Mass Storage driver...
                  usb.c: registered new driver usb-storage
                  USB Mass Storage support registered.
                  i2c-dev.o: Registered 'IXP425 I2C Adapter' as minor 0
                  i2c-core.o: adapter IXP425 I2C Adapter registered as adapter 0.
                  NET4: Linux TCP/IP 1.0 for NET4.0
                  IP Protocols: ICMP, UDP, TCP, IGMP
                  IP: routing cache hash table of 512 buckets, 4Kbytes
                  TCP: Hash tables configured (established 2048 bind 4096)
                  IP-Config: No network devices available.
                  NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
                  NetWinder Floating Point Emulator V0.97 (double precision)
                  VFS: Mounted root (jffs2 filesystem).
                  Freeing init memory: 244K
                  hub.c: new USB device 00:01.2-1, assigned address 2
                  Protocol: Transparent SCSI
                  before kernel thread
                  *** detect:usb-storage
                  * scsi_register: usb-storage-1,
                  * scsi_reg, hostno:1 prot is 49
                  * scsi_reg, retval->host_no:1
                  scsi1 : SCSI emulation for USB Mass Storage devices
                  ! scan_scsis
                  *** 49
                  31 port connect!!!!!
                  Vendor: Kingston Model: DataTraveler 2.0 Rev: 1.04
                  Type: Direct-Access ANSI SCSI revision: 02
                  the host no is 1
                  * sd_attach:0
                  Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
                  SCSI device sda: 1003520 512-byte hdwr sectors (514 MB)
                  sda: Write Protect is off
                  Partition check:
                  /dev/scsi/host1/bus0/target0/lun0: p1 p2 p3
                  WARNING: USB Mass Storage data integrity not assured
                  USB Mass Storage device found at 2
                  Module init.
                  ixp425_eth:
                  Initializing IXP425 NPE Ethernet driver software v. 1.1
                  ixp425_eth: CPU clock speed (approx) = 0 MHz
                  [error] ixEthMiiPhyScan : unexpected Mii PHY ID 00008201
                  ixp425_eth: ixp0 is using the PHY at address 1
                  ixp425_eth: ixp1 is using the PHY at address 0
                  ixp425_eth: ixEthMiiLinkStatus failed on PHY0.
                  Can't determine
                  the auto negotiated parameters. Using default values.
                  enable_irq(22) unbalanced from c39451bc
                  X1226: I2C based RTC driver.
                  i2c-core.o: driver X1226 registered.
                  X1226: found X1226 on IXP425 I2C Adapter
                  i2c-core.o: client [X1226] registered to adapter [IXP425 I2C
                  Adapter](pos. 0).
                  atr is 20
                  kjournald starting. Commit interval 5 seconds
                  EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
                  EXT3-fs: recovery complete.
                  EXT3-fs: mounted filesystem with ordered data mode.
                  kjournald starting. Commit interval 5 seconds
                  EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,2), internal journal
                  EXT3-fs: mounted filesystem with ordered data mode.
                  kjournald starting. Commit interval 5 seconds
                  EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,2), internal journal
                  EXT3-fs: mounted filesystem with ordered data mode.
                  Adding Swap: 63980k swap-space (priority -1)
                  EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal




                  --- In nslu2-general@yahoogroups.com, Rod Whitby <list.yahoo@r...> wrote:
                  > On 8/9/05, mike_pruis <mike_pruis@h...> wrote:
                  > > Yep I did a reboot...
                  > > in the mean time I have done the whole proces again
                  > > (reflash/reformatted/re...): same problem...
                  > > here my latest output - from before and after the reboot...
                  >
                  > Reboot again, and as soon as you get in, grab the output from "dmesg"
                  > and post that here. That will identify whether it's a slow disk or
                  > not.
                  >
                  > BTW, we'll be asking you to write up these troubleshooting steps on
                  the wiki ...
                  >
                  > -- Rod
                • Petr Jakes
                  Hi all, I just want to know how the story from this posting ended up. I have got the same problem. I did follow up the Unslung-5.x Family Release README
                  Message 8 of 9 , Sep 7, 2005
                  • 0 Attachment
                    Hi all, I just want to know how the story from this posting ended up.
                    I have got the same problem. I did follow up the "Unslung-5.x Family
                    Release README INSTALLATION" precisely and carefully many times and
                    after reboot the rootfs is starting from the slug, not from the memory
                    stick.
                    Petr


                    --- In nslu2-general@yahoogroups.com, "mike_pruis" <mike_pruis@h...>
                    wrote:
                    > ok guys/girls, thnx for the help.. I'd be happy to update the wiki...
                    > as soon as I know how :-) I will at minimum present it in a readable
                    > form and hope someone will help me wiki it...
                    >
                    > Ok.. rebooted the slug, enabled telnet, logged in as root and did a
                    > dmesg... and here's gibberish it returned (at least for me it is :-):
                    >
                    >
                    > # dmesg
                    > Linux version 2.4.22-xfs (unslung@u...) (gcc version 3.4.4) #1
                    > Sun Jun 12
                    > 21:17:17 PDT 2005
                    > CPU: XScale-IXP425/IXC1100 revision 1
                    > Machine: Intel IXDP425 Development Platform
                    > Warning: bad configuration page, trying to continue
                    > Security risk: creating user accessible mapping for 0x60000000 at
                    > 0xff00f000
                    > Security risk: creating user accessible mapping for 0x51000000 at
                    > 0xf1000000
                    > On node 0 totalpages: 8192
                    > zone(0): 8192 pages.
                    > zone(1): 0 pages.
                    > zone(2): 0 pages.
                    > Kernel command line: console=ttyS0,115200n8 root=/dev/mtdblock4
                    > rootfstype=jffs2
                    > rw init=/linuxrc mem=32M@0x00000000
                    > Relocating machine vectors to 0xffff0000
                    > Calibrating delay loop... 131.48 BogoMIPS
                    > Memory: 32MB = 32MB total
                    > Memory: 30276KB available (1582K code, 274K data, 244K init)
                    > Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
                    > Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
                    > Mount cache hash table entries: 512 (order: 0, 4096 bytes)
                    > Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
                    > Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
                    > POSIX conformance testing by UNIFIX
                    > PCI Autoconfig: Found Bus 0, Device 1, Function 0
                    > PCI Autoconfig: BAR 0, Mem, size=0x1000, address=0x4bfff000
                    > PCI Autoconfig: Found Bus 0, Device 1, Function 1
                    > PCI Autoconfig: BAR 0, Mem, size=0x1000, address=0x4bffe000
                    > PCI Autoconfig: Found Bus 0, Device 1, Function 2
                    > PCI Autoconfig: BAR 0, Mem, size=0x100, address=0x4bffdf00
                    > PCI: bus0: Fast back to back transfers disabled
                    > Linux NET4.0 for Linux 2.4
                    > Based upon Swansea University Computer Society NET3.039
                    > Initializing RT netlink socket
                    > Starting kswapd
                    > VFS: Disk quotas vdquot_6.5.1
                    > Journalled Block Device driver loaded
                    > devfs: v1.12c (20020818) Richard Gooch (rgooch@a...)
                    > devfs: boot_options: 0x0
                    > Installing knfsd (copyright (C) 1996 okir@m...).
                    > JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis
                    > Communications AB.
                    > i2c-core.o: i2c core module
                    > i2c-dev.o: i2c /dev entries driver module
                    > i2c-core.o: driver i2c-dev dummy driver registered.
                    > i2c-algo-bit.o: i2c bit algorithm module version 2.6.1 (20010830)
                    > pty: 256 Unix98 ptys configured
                    > Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ
                    > SERIAL_PCI en
                    > abled
                    > ttyS00 at 0xff000003 (irq = 15) is a XScale UART
                    > ttyS01 at 0xff001003 (irq = 13) is a XScale UART
                    > RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
                    > loop: loaded (max 8 devices)
                    > SCSI subsystem driver Revision: 1.00
                    > * host:<NULL>
                    > IXP425 Flash: Found an alias at 0x800000 for the chip at 0x0
                    > cfi_cmdset_0001: Erase suspend on write enabled
                    > 0: offset=0x0,size=0x20000,blocks=64
                    > Using buffer write method
                    > Creating 6 MTD partitions on "IXP425 Flash":
                    > 0x00000000-0x00040000 : "RedBoot"
                    > 0x00040000-0x00060000 : "SysConf"
                    > 0x00060000-0x00160000 : "Kernel"
                    > 0x00160000-0x00180000 : "Ramdisk"
                    > 0x00180000-0x007e0000 : "Flashdisk"
                    > 0x007e0000-0x00800000 : "FIS directory"
                    > usb.c: registered new driver usbdevfs
                    > usb.c: registered new driver hub
                    > pci probe begin
                    > ehci_hcd 00:01.2: NEC Corporation USB 2.0
                    > ehci_hcd 00:01.2: irq 26, pci mem c3872f00
                    > usb.c: new USB bus registered, assigned bus number 1
                    > PCI: 00:01.2 PCI cache line size set incorrectly (0 bytes) by BIOS/FW.
                    > PCI: 00:01.2 PCI cache line size corrected to 32.
                    > ehci_hcd 00:01.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-19/2.4
                    > hub.c: USB hub found
                    > hub.c: 5 ports detected
                    > pci probe ok
                    > host/usb-uhci.c: $Revision: 1.1 $ time 21:18:46 Jun 12 2005
                    > host/usb-uhci.c: High bandwidth mode enabled
                    > host/usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
                    > host/usb-ohci.c: USB OHCI at membase 0xc387a000, IRQ 28
                    > host/usb-ohci.c: usb-00:01.0, NEC Corporation USB
                    > usb.c: new USB bus registered, assigned bus number 2
                    > hub.c: USB hub found
                    > hub.c: 3 ports detected
                    > host/usb-ohci.c: USB OHCI at membase 0xc3880000, IRQ 27
                    > host/usb-ohci.c: usb-00:01.1, NEC Corporation USB (#2)
                    > usb.c: new USB bus registered, assigned bus number 3
                    > hub.c: USB hub found
                    > hub.c: 2 ports detected
                    > Initializing USB Mass Storage driver...
                    > usb.c: registered new driver usb-storage
                    > USB Mass Storage support registered.
                    > i2c-dev.o: Registered 'IXP425 I2C Adapter' as minor 0
                    > i2c-core.o: adapter IXP425 I2C Adapter registered as adapter 0.
                    > NET4: Linux TCP/IP 1.0 for NET4.0
                    > IP Protocols: ICMP, UDP, TCP, IGMP
                    > IP: routing cache hash table of 512 buckets, 4Kbytes
                    > TCP: Hash tables configured (established 2048 bind 4096)
                    > IP-Config: No network devices available.
                    > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
                    > NetWinder Floating Point Emulator V0.97 (double precision)
                    > VFS: Mounted root (jffs2 filesystem).
                    > Freeing init memory: 244K
                    > hub.c: new USB device 00:01.2-1, assigned address 2
                    > Protocol: Transparent SCSI
                    > before kernel thread
                    > *** detect:usb-storage
                    > * scsi_register: usb-storage-1,
                    > * scsi_reg, hostno:1 prot is 49
                    > * scsi_reg, retval->host_no:1
                    > scsi1 : SCSI emulation for USB Mass Storage devices
                    > ! scan_scsis
                    > *** 49
                    > 31 port connect!!!!!
                    > Vendor: Kingston Model: DataTraveler 2.0 Rev: 1.04
                    > Type: Direct-Access ANSI SCSI revision: 02
                    > the host no is 1
                    > * sd_attach:0
                    > Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
                    > SCSI device sda: 1003520 512-byte hdwr sectors (514 MB)
                    > sda: Write Protect is off
                    > Partition check:
                    > /dev/scsi/host1/bus0/target0/lun0: p1 p2 p3
                    > WARNING: USB Mass Storage data integrity not assured
                    > USB Mass Storage device found at 2
                    > Module init.
                    > ixp425_eth:
                    > Initializing IXP425 NPE Ethernet driver software v. 1.1
                    > ixp425_eth: CPU clock speed (approx) = 0 MHz
                    > [error] ixEthMiiPhyScan : unexpected Mii PHY ID 00008201
                    > ixp425_eth: ixp0 is using the PHY at address 1
                    > ixp425_eth: ixp1 is using the PHY at address 0
                    > ixp425_eth: ixEthMiiLinkStatus failed on PHY0.
                    > Can't determine
                    > the auto negotiated parameters. Using default values.
                    > enable_irq(22) unbalanced from c39451bc
                    > X1226: I2C based RTC driver.
                    > i2c-core.o: driver X1226 registered.
                    > X1226: found X1226 on IXP425 I2C Adapter
                    > i2c-core.o: client [X1226] registered to adapter [IXP425 I2C
                    > Adapter](pos. 0).
                    > atr is 20
                    > kjournald starting. Commit interval 5 seconds
                    > EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
                    > EXT3-fs: recovery complete.
                    > EXT3-fs: mounted filesystem with ordered data mode.
                    > kjournald starting. Commit interval 5 seconds
                    > EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,2), internal journal
                    > EXT3-fs: mounted filesystem with ordered data mode.
                    > kjournald starting. Commit interval 5 seconds
                    > EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,2), internal journal
                    > EXT3-fs: mounted filesystem with ordered data mode.
                    > Adding Swap: 63980k swap-space (priority -1)
                    > EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
                    >
                    >
                    >
                    >
                    > --- In nslu2-general@yahoogroups.com, Rod Whitby <list.yahoo@r...>
                    wrote:
                    > > On 8/9/05, mike_pruis <mike_pruis@h...> wrote:
                    > > > Yep I did a reboot...
                    > > > in the mean time I have done the whole proces again
                    > > > (reflash/reformatted/re...): same problem...
                    > > > here my latest output - from before and after the reboot...
                    > >
                    > > Reboot again, and as soon as you get in, grab the output from "dmesg"
                    > > and post that here. That will identify whether it's a slow disk or
                    > > not.
                    > >
                    > > BTW, we'll be asking you to write up these troubleshooting steps on
                    > the wiki ...
                    > >
                    > > -- Rod
                  Your message has been successfully submitted and would be delivered to recipients shortly.