• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: another corrupted microSD?  (Read 4739 times)
bad_gui
Jr. Member
**

Karma: 0
Posts: 50


View Profile
« on: January 22, 2013, 06:43:11 PM »

Three months ago I replaced the 4GB microSD that came with my Gurplug Server Plus.  I installed the root fs on it and it
ran over a year until I kept getting I/O errors and it became unbootable.

I bought a Kingston 4GB card three months ago to replace the original and had a hard time recovering many of my files
from the original.  The new one is ext2 and I used instructions on the web to install Squeeze.

Now I can't ssh into the plug and when I use the JTAG I get weird errors about the shell interpreter.  I tried restarting the
ssh service and got a "file not found" error when I can see the file.  I removed the microSD and using a USB adapter I
try to fsck it and get

Code:
# fsck -a /dev/sdc
fsck from util-linux-ng 2.17.2
fsck.ext2: No medium found while trying to open /dev/sdc
/dev/sdc:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

I can see partitions.

Code:
[ 3751.484994] usb-storage: device scan complete
[ 3751.485778] scsi 5:0:0:0: Direct-Access     Generic  STORAGE DEVICE   0272 PQ: 0 ANSI: 0
[ 3751.486402] sd 5:0:0:0: Attached scsi generic sg3 type 0
[ 3751.839501] sd 5:0:0:0: [sdc] 7774208 512-byte logical blocks: (3.98 GB/3.70 GiB)
[ 3751.840624] sd 5:0:0:0: [sdc] Write Protect is off
[ 3751.840633] sd 5:0:0:0: [sdc] Mode Sense: 0b 00 00 08
[ 3751.840638] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[ 3751.843365] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[ 3751.843372]  sdc: sdc1 sdc2 sdc3 < sdc5 >
[ 3751.849510] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[ 3751.849519] sd 5:0:0:0: [sdc] Attached SCSI removable disk

Is this microSD trash or is there hope of repairing it?  Anyone else having problems?

I have an older generation plug and have heavily modified it to deal with heat.
Removed internal power supply and now have external one.  Heatsinks on chips and
external fan that blows air over heatsinks.


Logged

bad_gui
Jr. Member
**

Karma: 0
Posts: 50


View Profile
« Reply #1 on: January 22, 2013, 07:09:03 PM »

It looks like this is a lost cause. 

Here is the partition table

# fdisk -l /dev/sdc

Disk /dev/sdc: 3980 MB, 3980394496 bytes
123 heads, 62 sectors/track, 1019 cylinders
Units = cylinders of 7626 * 512 = 3904512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00087719

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           1          59      220160   83  Linux
Partition 1 has different physical/logical beginnings (non-Linux?):
     phys=(0, 32, 33) logical=(0, 33, 3)
Partition 1 has different physical/logical endings:
     phys=(27, 136, 45) logical=(58, 0, 60)
Partition 1 does not end on cylinder boundary.
/dev/sdc2              59         962     3443712   83  Linux
Partition 2 has different physical/logical beginnings (non-Linux?):
     phys=(27, 136, 46) logical=(58, 0, 61)
Partition 2 has different physical/logical endings:
     phys=(456, 65, 57) logical=(961, 19, 28)
Partition 2 does not end on cylinder boundary.
/dev/sdc3             962        1020      220161    5  Extended
Partition 3 has different physical/logical beginnings (non-Linux?):
     phys=(456, 98, 25) logical=(961, 52, 29)
Partition 3 has different physical/logical endings:
     phys=(483, 202, 39) logical=(1019, 20, 26)
Partition 3 does not end on cylinder boundary.
/dev/sdc5             962        1020      220160   82  Linux swap / Solaris



When I mount the microSD I see

# du -sm  /media/image/
du: cannot access `/media/image/usr/share/man/man2/io_getevents.2.gz': Input/output error
du: cannot access `/media/image/usr/src/linux-headers-2.6.32-5-common/include/rdma': Input/output error
du: cannot access `/media/image/usr/src/linux-headers-2.6.32-5-common/include/linux/patchkey.h': Input/output error
du: cannot access `/media/image/usr/src/linux-headers-2.6.32-5-common/include/net/ipcomp.h': Input/output error
du: cannot access `/media/image/usr/src/linux-headers-2.6.32-5-common/include/asm-generic/mman-common.h': Input/output error
du: cannot access `/media/image/usr/src/linux-headers-2.6.32-5-common/include/video/mbxfb.h': Input/output error
du: cannot access `/media/image/usr/src/linux-headers-2.6.32-5-kirkwood/include/config/smsc': Input/output error
du: cannot access `/media/image/usr/src/linux-headers-2.6.32-5-kirkwood/include/config/snd/mona.h': Input/output error
138759609   /media/image/


Is the Guruplug destroying the MicroSD chips?   Anyone else have this problem?
Logged

ppmt
Full Member
***

Karma: 1
Posts: 129


View Profile
« Reply #2 on: January 24, 2013, 08:46:36 AM »

This is not going to help but I had a similar experienced with MicroSD on my guruplug long time ago.

It was working fine and suddenly it stopped working and I could never recover the card. Since I swtiched to a USB key and it is working happily since
(more than 2 years)

I was going to give it another chance but based on your experience I might reconsider. I thought it was the heat that caused the SD to "burn" but
since you say yours is modified to cope with it....
Logged

bad_gui
Jr. Member
**

Karma: 0
Posts: 50


View Profile
« Reply #3 on: January 25, 2013, 08:25:09 PM »

This is just a guess.

I used a Debian Squeeze installer for the new microSD and it partitioned swap space. My
previous uSD had Lenny without swap- that uSD lasted almost two years.

Perhaps NAND chips shouldn't have a swap partition?  I'm not using the plug for anything
that requires a lot of swap.  I shouldn't have just accepted the defaults.

Another possibility: Some posts I saw on the web claim there are counterfeit low-quality
uSD chips on the market. 

I decided to install Wheezy to an external eSATA drive.  So far it seems much more responsive
than the uSD.  At least it is easier to remember the steps I took to customize the system
after only three months.
Logged

jkwilborn
Newbie
*

Karma: 0
Posts: 4


View Profile
« Reply #4 on: February 05, 2013, 11:01:22 AM »

Only word I've heard is that the ext3 takes a toll on SD chips and that the best way if for an ext2 partition.  Does this jive with what you have found?

Jack
Logged

Pages: [1]
Print
Jump to: