← previous next →
Pages: [1]

Author Topic: Is My Microdrive Dying?  (Read 4334 times)

chyang

  • Sr. Member
  • ****
  • Posts: 270
    • View Profile
    • http://mail.ustc.edu.cn/~chyang/
Is My Microdrive Dying?
« on: April 01, 2006, 08:03:52 am »
I have never heavily used it, but since last hdd1 error problem occurs, I was quite scared at potential problems with it.

I have observed some untable issues with cacko1.23b1 for c3000.This time, I managed to log in via ssh, and observed kernel fault. It seems that it is the probllem with the file system.I rebooted it and found my cookies seem gone. So I dmesged to see what happened:
EXT3-fs error (device ide0(3,2)): ext3_free_blocks: Freeing blocks not in datazone - block = 1946615838, count = 1
EXT3-fs error (device ide0(3,2)): ext3_free_blocks: Freeing blocks not in datazone - block = 2003329893, count = 1
EXT3-fs error (device ide0(3,2)): ext3_free_blocks: Freeing blocks not in datazone - block = 25518693, count = 1
...
XT3-fs error (device ide0(3,2)): ext3_free_blocks: Freeing blocks not in datazone - block = 57700200, count = 1
EXT3-fs error (device ide0(3,2)): ext3_free_blocks: bit already cleared for block 295540
eth0: Undersized frame received (0 bytes)
eth0: Undersized frame received (0 bytes)
EXT3-fs warning (device ide0(3,2)): ext3_unlink: Deleting nonexistent file
(72608), 0
...

Has anyone met similar problems? any comment?
Thanks.
Logged
SL-C3200+Symbol CF WIFI+Corsair 2GB SD
SL-5500+Sharp-3.13 ROM+Viking 512MB CF+Kinston 256MB SD
[img]http://sunsetyang.googlepages.com/c3200.gif\" border=\"0\" class=\"linked-sig-image\" /][img]http://sunsetyang.googlepages.com/5500.gif\" border=\"0\" class=\"linked-sig-image\" /]
Socket CF Bluetooth + EagleTec CF Lan Card + EagleTec CF Modem
Histroy:
[SL-C3000 Cacko 1.23 Beta 1] Sold on 2006/07/27
MA701 CF WIFI + EagleTec CF Bluetooth + D-Link DCF-660W WIFI
[SL5500+Sharp-3.13 ROM+SimpleTech 64MB CF+Hagiwara 128MB SD] Lost on 18,March,04

chyang

  • Sr. Member
  • ****
  • Posts: 270
    • View Profile
    • http://mail.ustc.edu.cn/~chyang/
Is My Microdrive Dying?
« Reply #1 on: April 01, 2006, 08:08:06 am »
Also I have noticed there may be problems with the internal flash file system:
 
Eep. Child "stab" (ino #3051) of dir ino #3050 doesn't exist!
Eep. Child "param" (ino #3068) of dir ino #3050 doesn't exist!
Inode #2893 was a directory with children - removing those too...
Inode #3026 was a directory with children - removing those too...
Inode #3050 was a directory with children - removing those too...
Cannot remove child "stab", ino #3051, because it doesn't exist
Cannot remove child "param", ino #3068, because it doesn't exist

...

How to fix this?
Thanks
Logged
SL-C3200+Symbol CF WIFI+Corsair 2GB SD
SL-5500+Sharp-3.13 ROM+Viking 512MB CF+Kinston 256MB SD
[img]http://sunsetyang.googlepages.com/c3200.gif\" border=\"0\" class=\"linked-sig-image\" /][img]http://sunsetyang.googlepages.com/5500.gif\" border=\"0\" class=\"linked-sig-image\" /]
Socket CF Bluetooth + EagleTec CF Lan Card + EagleTec CF Modem
Histroy:
[SL-C3000 Cacko 1.23 Beta 1] Sold on 2006/07/27
MA701 CF WIFI + EagleTec CF Bluetooth + D-Link DCF-660W WIFI
[SL5500+Sharp-3.13 ROM+SimpleTech 64MB CF+Hagiwara 128MB SD] Lost on 18,March,04

iamasmith

  • Hero Member
  • *****
  • Posts: 1248
    • View Profile
Is My Microdrive Dying?
« Reply #2 on: April 01, 2006, 08:37:23 am »
The ext3 errors on the Microdrive are something to be worried around.. that drive needs an fsck.. boot into the d+b menu and check it.

Ignore the messages from the flash file system.. this is normal behaviour for jffs2 which looks alarming but a little reading about jffs2 will convince you that it is nothing to worry about.

-Andy
Logged
OpenBSD 4.2 -current on full 4Gb of SL-C3000
Microdrive replaced with 4Gb SanDisk Extreme III card

chyang

  • Sr. Member
  • ****
  • Posts: 270
    • View Profile
    • http://mail.ustc.edu.cn/~chyang/
Is My Microdrive Dying?
« Reply #3 on: April 01, 2006, 09:12:30 am »
Andy, thank you very much!
For the first time, I entered the D+B mode, it spent me some time to achive that.
Fixed many problems, hope all the issues will go.

Again, thank you.
Logged
SL-C3200+Symbol CF WIFI+Corsair 2GB SD
SL-5500+Sharp-3.13 ROM+Viking 512MB CF+Kinston 256MB SD
[img]http://sunsetyang.googlepages.com/c3200.gif\" border=\"0\" class=\"linked-sig-image\" /][img]http://sunsetyang.googlepages.com/5500.gif\" border=\"0\" class=\"linked-sig-image\" /]
Socket CF Bluetooth + EagleTec CF Lan Card + EagleTec CF Modem
Histroy:
[SL-C3000 Cacko 1.23 Beta 1] Sold on 2006/07/27
MA701 CF WIFI + EagleTec CF Bluetooth + D-Link DCF-660W WIFI
[SL5500+Sharp-3.13 ROM+SimpleTech 64MB CF+Hagiwara 128MB SD] Lost on 18,March,04

chyang

  • Sr. Member
  • ****
  • Posts: 270
    • View Profile
    • http://mail.ustc.edu.cn/~chyang/
Is My Microdrive Dying?
« Reply #4 on: April 06, 2006, 12:19:04 pm »
After fix, it worked some time,while later, it again showes fs error.So I fixed again.
sharp_sl_nand_resume
pxa_pcmcia_init(0)
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72620, block=294920
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,2)) in ext3_new_inode: IO failure
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72621, block=294920
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,2)) in ext3_new_inode: IO failure
...
sharp_sl_nand_resume
pxa_pcmcia_init(0)
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72611, block=294919
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
Change Core voltage = a.
current voltage 1a
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72609, block=294919
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72609, block=294919
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,2)) in ext3_orphan_add: IO failure
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72609, block=294919
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72609, block=294919
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,2)) in ext3_orphan_add: IO failure
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72609, block=294919
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
pxa_pcmcia_init(1)
...
sharp_sl_nand_resume
pxa_pcmcia_init(0)
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72620, block=294920
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,2)) in ext3_new_inode: IO failure
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72621, block=294920
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,2)) in ext3_new_inode: IO failure
pxa_pcmcia_init(1)

it seems suspend/resume may cause problems.
any help?Thanks a lot!
Logged
SL-C3200+Symbol CF WIFI+Corsair 2GB SD
SL-5500+Sharp-3.13 ROM+Viking 512MB CF+Kinston 256MB SD
[img]http://sunsetyang.googlepages.com/c3200.gif\" border=\"0\" class=\"linked-sig-image\" /][img]http://sunsetyang.googlepages.com/5500.gif\" border=\"0\" class=\"linked-sig-image\" /]
Socket CF Bluetooth + EagleTec CF Lan Card + EagleTec CF Modem
Histroy:
[SL-C3000 Cacko 1.23 Beta 1] Sold on 2006/07/27
MA701 CF WIFI + EagleTec CF Bluetooth + D-Link DCF-660W WIFI
[SL5500+Sharp-3.13 ROM+SimpleTech 64MB CF+Hagiwara 128MB SD] Lost on 18,March,04

Meanie

  • Hero Member
  • *****
  • Posts: 2803
    • View Profile
    • http://www.users.on.net/~hluc/myZaurus/
Is My Microdrive Dying?
« Reply #5 on: April 06, 2006, 09:23:24 pm »
Quote
After fix, it worked some time,while later, it again showes fs error.So I fixed again.
sharp_sl_nand_resume
pxa_pcmcia_init(0)
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72620, block=294920
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,2)) in ext3_new_inode: IO failure
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72621, block=294920
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,2)) in ext3_new_inode: IO failure
...
sharp_sl_nand_resume
pxa_pcmcia_init(0)
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72611, block=294919
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
Change Core voltage = a.
current voltage 1a
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72609, block=294919
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72609, block=294919
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,2)) in ext3_orphan_add: IO failure
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72609, block=294919
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72609, block=294919
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,2)) in ext3_orphan_add: IO failure
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72609, block=294919
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
pxa_pcmcia_init(1)
...
sharp_sl_nand_resume
pxa_pcmcia_init(0)
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72620, block=294920
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,2)) in ext3_new_inode: IO failure
EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=72621, block=294920
EXT3-fs error (device ide0(3,2)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,2)) in ext3_new_inode: IO failure
pxa_pcmcia_init(1)

it seems suspend/resume may cause problems.
any help?Thanks a lot!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=122061\"][{POST_SNAPBACK}][/a][/div]

are you using tetsu's special kernel? i remember that when i used the stock sharp kernel, i had problems after resume with killed processes and also some IO errors due to lost mounts, but after installing the tetsu kernel and modules, the problems went away.
Logged
SL-C3000 - pdaXii13 build5.4.9 (based on pdaXrom beta3) / SL-C3100 - Sharp ROM 1.02 JP (heavily customised)
Netgear MA701 CF, SanDisk ConnectPlus CF, Socket Bluetooth CF, 4GB Kingston CF,  4GB pqi SD, 4GB ChoiceOnly SD, 2GB SanDisk SD USB Plus, 1GB SanDisk USB Plus, 1GB Transcend SD, 2GB SanDisk MicroSD with SD adaptor, Piel Frama Leather Case, GoldX 5-in-1 USB cable, USB hub, USB mouse, USB keyboard, USB ethernet, USB HDD, many other USB accessories...
(Zaurus SL-C3000 owner since March 14. 2005, Zaurus SL-C3100 owner since September 21. 2005)
http://members.iinet.net.au/~wyso/myZaurus - zBook3K

chyang

  • Sr. Member
  • ****
  • Posts: 270
    • View Profile
    • http://mail.ustc.edu.cn/~chyang/
Is My Microdrive Dying?
« Reply #6 on: April 07, 2006, 08:45:13 am »
I may be using the tetsu's kernel, which is carried with Cacko C3kbeta1.
Thanks
Logged
SL-C3200+Symbol CF WIFI+Corsair 2GB SD
SL-5500+Sharp-3.13 ROM+Viking 512MB CF+Kinston 256MB SD
[img]http://sunsetyang.googlepages.com/c3200.gif\" border=\"0\" class=\"linked-sig-image\" /][img]http://sunsetyang.googlepages.com/5500.gif\" border=\"0\" class=\"linked-sig-image\" /]
Socket CF Bluetooth + EagleTec CF Lan Card + EagleTec CF Modem
Histroy:
[SL-C3000 Cacko 1.23 Beta 1] Sold on 2006/07/27
MA701 CF WIFI + EagleTec CF Bluetooth + D-Link DCF-660W WIFI
[SL5500+Sharp-3.13 ROM+SimpleTech 64MB CF+Hagiwara 128MB SD] Lost on 18,March,04

chyang

  • Sr. Member
  • ****
  • Posts: 270
    • View Profile
    • http://mail.ustc.edu.cn/~chyang/
Is My Microdrive Dying?
« Reply #7 on: April 13, 2006, 10:54:17 am »
It seems that I'm wrong, I was using Cacko 1.23 Beta 1 for C3000, which seems to use the Sharp Kernel.

I found this seems to be a known problem for Cacko(?)
http://probbe.nerim.net/zaurus/cacko3k/log3.txt
It also shows the problem.

Well, any one can confirm on C3000?
I often opened Opera 7.55 and then suspend, sometimes, after resume, from the dmesg, I can see the information.
Logged
SL-C3200+Symbol CF WIFI+Corsair 2GB SD
SL-5500+Sharp-3.13 ROM+Viking 512MB CF+Kinston 256MB SD
[img]http://sunsetyang.googlepages.com/c3200.gif\" border=\"0\" class=\"linked-sig-image\" /][img]http://sunsetyang.googlepages.com/5500.gif\" border=\"0\" class=\"linked-sig-image\" /]
Socket CF Bluetooth + EagleTec CF Lan Card + EagleTec CF Modem
Histroy:
[SL-C3000 Cacko 1.23 Beta 1] Sold on 2006/07/27
MA701 CF WIFI + EagleTec CF Bluetooth + D-Link DCF-660W WIFI
[SL5500+Sharp-3.13 ROM+SimpleTech 64MB CF+Hagiwara 128MB SD] Lost on 18,March,04
Pages: [1]
← previous next →