You are here: Home » Reply » Reply To: NSLU2 setup problem

Reply To: NSLU2 setup problem

#14487
BrianOSullivan
Participant

Thanks for the reply sonichouse, I took your advise, and got this:

# dmesg
/bus0/target0/lun0: p1 p2 p3
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
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 detrmine
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
ufsd: driver loaded
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
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 warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,17), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,18), internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Adding Swap: 120480k swap-space (priority -1)
Adding Swap: 127964k swap-space (priority -2)
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,17), internal journal
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
TCP: drop open request from 88.229.159.38/3525
TCP: drop open request from 88.229.159.38/3528
TCP: drop open request from 88.229.159.38/3525
TCP: drop open request from 88.229.159.38/3528
TCP: drop open request from 88.229.159.38/3538
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
attempt to access beyond end of device
08:01: rw=0, want=0, limit=247473
#

Which seems to agree with what your saying about disk corruption… I ran e2fsck also and…

#e2fsck
Segmentation fault

Do I need to get a new flash drive and unsling from start???