From: ekoshimo <ed....@na...> - 2010-04-20 21:35:01
|
Hello all - I'm trying to create a bootable microSD card per the instructions at the gumstix.net site. The card is a SANS brand 2GB microSD card, which I am using with the SD adaptor and a generic USB card reader. If I follow the posted instructions, then everything appears to go well until I try to mount the ext3 partition. I get an error message saying the partition has an unrecognizable filesystem. At this time trying to use 'fsck' or 'gparted' did not help to recover the ext3 partition. Sometimes I can mount the ext3 partition successfully, but when I try to untar the linux image the process fails partway through and the filesystem becomes inaccessable. Also, at this time trying to use 'fsck' seemed to generate the same error messages, followed by a seemingly successful recovery, which in the end turned out to be not true. I then looked on the forum and found the Blank-2G.img provided. I used 'dd' to write to the microSD card and then I had to fix the filesystems afterwards with 'gparted'. At this time there were still problems with the ext3 partition, If I setup both the smaller 32MB and the larger 1.95GB partitions to a FAT32 filesystem, I don't seem to have any problems with the card. So, the problem appears to be with how I am creating the ext3 partition. Can someone provide any hints or detailed instructions of other things I can try? I would appreciate any help. Thanks, ed -- View this message in context: http://old.nabble.com/overo-fire-summit-board-microSD-issues--tp28287923p28287923.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Frank A. <ft...@ya...> - 2010-04-20 22:25:48
|
On 4/20/2010 5:34 PM, ekoshimo wrote: > > Hello all - > > I'm trying to create a bootable microSD card per the instructions at the > gumstix.net site. The card is a SANS brand 2GB microSD card, which I am > using with the SD adaptor and a generic USB card reader. > > If I follow the posted instructions, then everything appears to go well > until I try to mount the ext3 partition. I get an error message saying the > partition has an unrecognizable filesystem. At this time trying to use > 'fsck' or 'gparted' did not help to recover the ext3 partition. > > Sometimes I can mount the ext3 partition successfully, but when I try to > untar the linux image the process fails partway through and the filesystem > becomes inaccessable. Also, at this time trying to use 'fsck' seemed to > generate the same error messages, followed by a seemingly successful > recovery, which in the end turned out to be not true. > > I then looked on the forum and found the Blank-2G.img provided. I used 'dd' > to write to the microSD card and then I had to fix the filesystems > afterwards with 'gparted'. At this time there were still problems with the > ext3 partition, If I setup both the smaller 32MB and the larger 1.95GB > partitions to a FAT32 filesystem, I don't seem to have any problems with the > card. > > So, the problem appears to be with how I am creating the ext3 p artition. > Can someone provide any hints or detailed instructions of other things I can > try? > I have had issues with some cards if the geometry was not 255 heads, 63 sectors/track. This mostly affected whether the card could boot, but if I were having the issues you're seeing, I'd give it a try. Detailed instructions on configuring card geometry using fdisk are on the beagleboard wiki. The Beagleboard and Overo are close cousins, and I've used the instructions from this page to set up all my Overo microSD cards. Here's the link: http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat > I would appreciate any help. > > Thanks, > ed > |
From: Alex G. <al...@al...> - 2010-04-20 22:47:06
|
On 21/04/2010 7:34 AM, ekoshimo wrote: > Hello all - > > I'm trying to create a bootable microSD card per the instructions at the > gumstix.net site. The card is a SANS brand 2GB microSD card, which I am > using with the SD adaptor and a generic USB card reader. > > If I follow the posted instructions, then everything appears to go well > until I try to mount the ext3 partition. I get an error message saying the > partition has an unrecognizable filesystem. At this time trying to use > 'fsck' or 'gparted' did not help to recover the ext3 partition. > > Sometimes I can mount the ext3 partition successfully, but when I try to > untar the linux image the process fails partway through and the filesystem > becomes inaccessable. Also, at this time trying to use 'fsck' seemed to > generate the same error messages, followed by a seemingly successful > recovery, which in the end turned out to be not true. > > I then looked on the forum and found the Blank-2G.img provided. I used 'dd' > to write to the microSD card and then I had to fix the filesystems > afterwards with 'gparted'. At this time there were still problems with the > ext3 partition, If I setup both the smaller 32MB and the larger 1.95GB > partitions to a FAT32 filesystem, I don't seem to have any problems with the > card. > > So, the problem appears to be with how I am creating the ext3 partition. > Can someone provide any hints or detailed instructions of other things I can > try? > > I would appreciate any help. > > Thanks, > ed > > Make sure to unmount the cards first. Try using the gparted or Palimpsest disk untility (in fedora) to do the formatting if the formatting is giving you problems. Another trick is copy the tarred image file to the card before untarring it (as long as there is enough space) If doing multiple cards , only need to format the first one, then untar to that. Boot it, check that its good instll anything else necessary then dd copy to the others (and make a backup on the pc of the dd file). Alex -- UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views the University of Technology, Sydney. Before opening any attachments, please check them for viruses and defects. |