From: Sean S. <sst...@se...> - 2009-11-11 19:44:32
|
I was wondering if I am missing something ... it has been a while since I dove head first into linux, so forgive me :) I recently picked up a 2 gb sandisk card. And then did the following: - Updated the verdex conf file to make sure it would build fat, ext2, and mmcroot - Deleted my gumstix-oe/tmp directory - Rebuilt everything to make sure it was totally clean using gumstix-basic-image (even ran svn update) - used gparted to create the partitions and format them according to the wiki page: - 64 mb fat16 parititon labeled gum-uImage - 1.7 gb ext2 partition labeled gum-rootfs - Copied the uImage file and factory script to the fat partition - extracted the rootfs to the ext2 partition - unmounted the two partitions - plooped the microSD card into my Verdex Pro-XM4 - fired up minicom and booted the gumstix - It seems to read the card fine and it get past where most kernels panic: - Instruction Cache is ON Found gumstix-factory.script on MMC... ## Executing script at a2000000 Booting from mmc/microSD... Detected: 1931264 blocks of 1024 bytes (1886MB) SD card. Vendor: Man 03 OEM SD "SU02G" Date 08/2009 Product: 49424732 Revision: 8.0 reading uimage 902892 bytes read ## Booting image at a2000000 ... Image Name: Angstrom/2.6.21/gumstix- custom-v Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 902828 Bytes = 881.7 kB Load Address: a0008000 Entry Point: a0008000 OK - Then it goes through the boot process but dies with ext2 i/o errors: - Not netCF-vx board: using newer GPIO configuration CPLD responded with: ff Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.8 mmcblk0: error 1 sending stop command end_request: I/O error, dev mmcblk0, sector 3263168 mmcblk0: error 1 sending read/write command end_request: I/O error, dev mmcblk0, sector 3231008 Buffer I/O error on device mmcblk0p2, logical block 393292 lost page write due to I/O error on mmcblk0p2 IO error syncing ext2 inode [mmcblk0p2:000175a9] mmcblk0: error 1 sending read/write command end_request: I/O error, dev mmcblk0, sector 3263168 mmcblk0: error 1 sending read/write command end_request: I/O error, dev mmcblk0, sector 3231008 mmcblk0: error 1 sending read/write command end_request: I/O error, dev mmcblk0, sector 3263168 mmcblk0: error 1 sending read/write command end_request: I/O error, dev mmcblk0, sector 84672 Buffer I/O error on device mmcblk0p2, logical block 0 lost page write due to I/O error on mmcblk0p2 EXT2-fs error (device mmcblk0p2): ext2_get_inode: unable to read inode block - 2 I have tried running 'Check' from gparted and it originally said that the sectors were not what Windows would expect, so I moved the card over to a windows machine and formatted it there and redid the last couple of steps to files on the drive and test. This did not fix anything :( I have noticed that when this occurs, when I try to clear out the gum-rootfs partition, I get stale file handle messages. I have searched through Nabble and Google to no avail. There were some threads about using a ram disk to boot, but I am not sure if the level of effort is appropriate / necessary to get the microSD card going. I have tried the prebuilt images from the Steve's site, but they still have the strange I/O errors ... I am starting to think that I might be suffering from a faulty card, but then again, my host linux box is not complaining about it .. Any thoughts or tips would be greatly appreciated! Respectfully, Sean Stallbaum Serena Software, Inc. | Sr. Technical Consultant E: SSt...@se... | P: 216-374-9195 Sent from Lakewood, Ohio, United States |
From: Dirk B. <dir...@go...> - 2009-11-11 19:58:13
|
Sean Stallbaum wrote: > I was wondering if I am missing something ... it has been a while since I > dove head first into linux, so forgive me :) > > I recently picked up a 2 gb sandisk card. And then did the following: > > - Updated the verdex conf file to make sure it would build fat, ext2, and > mmcroot > - Deleted my gumstix-oe/tmp directory > - Rebuilt everything to make sure it was totally clean using > gumstix-basic-image (even ran svn update) > - used gparted to create the partitions and format them according to the > wiki page: > - 64 mb fat16 parititon labeled gum-uImage > - 1.7 gb ext2 partition labeled gum-rootfs > - Copied the uImage file and factory script to the fat partition > - extracted the rootfs to the ext2 partition > - unmounted the two partitions > - plooped the microSD card into my Verdex Pro-XM4 > - fired up minicom and booted the gumstix > - It seems to read the card fine and it get past where most kernels > panic: > - Instruction Cache is ON > Found gumstix-factory.script on MMC... > ## Executing script at a2000000 > Booting from mmc/microSD... > Detected: 1931264 blocks of 1024 bytes (1886MB) SD card. > Vendor: Man 03 OEM SD "SU02G" Date 08/2009 > Product: 49424732 > Revision: 8.0 > reading uimage > > 902892 bytes read > ## Booting image at a2000000 ... > Image Name: Angstrom/2.6.21/gumstix- > custom-v > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 902828 Bytes = 881.7 kB > Load Address: a0008000 > Entry Point: a0008000 > OK > - Then it goes through the boot process but dies with ext2 i/o errors: > - Not netCF-vx board: using newer GPIO configuration > CPLD responded with: ff > Bluetooth: RFCOMM socket layer initialized > Bluetooth: RFCOMM TTY layer initialized > Bluetooth: RFCOMM ver 1.8 > mmcblk0: error 1 sending stop command > end_request: I/O error, dev mmcblk0, sector 3263168 > mmcblk0: error 1 sending read/write command > end_request: I/O error, dev mmcblk0, sector 3231008 > Buffer I/O error on device mmcblk0p2, logical block 393292 > lost page write due to I/O error on mmcblk0p2 > IO error syncing ext2 inode [mmcblk0p2:000175a9] > mmcblk0: error 1 sending read/write command > end_request: I/O error, dev mmcblk0, sector 3263168 > mmcblk0: error 1 sending read/write command > end_request: I/O error, dev mmcblk0, sector 3231008 > mmcblk0: error 1 sending read/write command > end_request: I/O error, dev mmcblk0, sector 3263168 > mmcblk0: error 1 sending read/write command > end_request: I/O error, dev mmcblk0, sector 84672 > Buffer I/O error on device mmcblk0p2, logical block 0 > lost page write due to I/O error on mmcblk0p2 > EXT2-fs error (device mmcblk0p2): ext2_get_inode: unable to read inode > block - 2 > > I have tried running 'Check' from gparted and it originally said that the > sectors were not what Windows would expect, so I moved the card over to a > windows machine and formatted it there and redid the last couple of steps to > files on the drive and test. This did not fix anything :( I have noticed > that when this occurs, when I try to clear out the gum-rootfs partition, I > get stale file handle messages. > > I have searched through Nabble and Google to no avail. There were some > threads about using a ram disk to boot, but I am not sure if the level of > effort is appropriate / necessary to get the microSD card going. I have > tried the prebuilt images from the Steve's site, but they still have the > strange I/O errors ... I am starting to think that I might be suffering from > a faulty card, I would think so, too. Try an other card. They are so cheap now, I wonder how long 2gb cards will still be available... Best regards Dirk |
From: Søren S. C. <li...@ss...> - 2009-11-11 20:54:30
|
> I wonder how long 2gb cards will still be available... Actually for quite some time I guess. Main reason: That 2GB is the highest capacity in the original SD specification. Next size (4GB) is SDHC and thereby not guaranteed compliant with all old SD (non SDHC compatible) equipment... I would therefore guess, that 2GB will still exist for quite a while, but it might though be that 4GB and 8GB will die on behalf of 16GB and 32GB cards - I totally agree :-)... Best regards Søren --- SSC Solutions ApS - Denmark - www.ssc-solutions.dk |