خرید بک لینک

Hi there.

I'm in [LUBUBTU] 14.04 LTS.

I removed my phone's SDcard from my Linux box by mistake when there was an "operation pending". Now it crashes the phone and is not mounted by my linux box.

It has 2 partitions:
(1) An ext3 30gb partition (label "30 GB Volume") for media - Iswear this showed up as EXT3 earlier, but now this shows up as FAT so maybe it's FAT?? - Fdisk -l is telling me so!

Code:

$ sudo file -sL /dev/sdb1
/dev/sdb1: x86 boot sector
(2) An ext3 1GB partition (label "sd-ext") that is an extension of my phone's inteal memory (via the app Link2SD) - all my apps live here so I'd like to avoid reformatting.

fdisk -l tells me the partitions are /dev/sdb1 and /dev/sdb2

I've tried:


(A) Auto-repair 1GB volume with fsuk (unsuccesful):

Code:

$ sudo fsck -v /dev/sdb2
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
sd-ext: recovering joual
Superblock needs_recovery flag is clear, but joual has data.
Run joual anyway<y>? yes
fsck.ext3: unable to set superblock flags on sd-ext


sd-ext: ********** WARNING: Filesystem still has errors **********
And the same on the 30GB volume it doesn't recognise as EXT3 so I tried resetting the "dirty bit" as FAT:

(B) resetting the superblock from backup on the 1GB partition:

Code:

$ sudo mke2fs -n /dev/sdb2
mke2fs 1.42.9 (4-Feb-2014)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
62592 inodes, 250110 blocks
12505 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=260046848
8 block groups
32768 blocks per group, 32768 fragments per group
7824 inodes per group
Superblock backups stored on blocks: 
    32768, 98304, 163840, 229376

$ sudo e2fsck -b 32768 /dev/sdb2
e2fsck 1.42.9 (4-Feb-2014)
e2fsck: Invalid argument while trying to open /dev/sdb2

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try ruing e2fsck with an alteate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

$ sudo e2fsck -b 98304 /dev/sdb2
e2fsck 1.42.9 (4-Feb-2014)
e2fsck: Invalid argument while trying to open /dev/sdb2

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try ruing e2fsck with an alteate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

$ sudo e2fsck -b 163840 /dev/sdb2
e2fsck 1.42.9 (4-Feb-2014)
e2fsck: Invalid argument while trying to open /dev/sdb2

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try ruing e2fsck with an alteate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

$ sudo e2fsck -b 229376 /dev/sdb2
e2fsck 1.42.9 (4-Feb-2014)
e2fsck: Invalid argument while trying to open /dev/sdb2

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try ruing e2fsck with an alteate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

Now:

- The 30GB partition mounts on my Linux box but when I copy files it throws an I/O error.

- The 1GB partition says "an operation is already pending".

If inserted into the phone "media scaing - SDcard" crashes the phone at around 90%.

I've probably not done this methodically enough / missed something? Any ideas?

برچسب: نویسنده: استخدام کار تاريخ: سه شنبه 15 تير 1395 ساعت: 2:31

صفحه بندی