sudo mount /dev/sdc1 /media/k
mount: /dev/sdc1: can't read superblock
-----------------------------------------------------------------------------
sudo mkfs.ext4 -n /dev/sdc
mke2fs 1.42 (29-Nov-2011)
/dev/sdc is entire device, not just one partition!
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
183148544 inodes, 732566646 blocks
36628332 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
22357 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544
"کسی میتونه راهنمایی کنه لطفا."
"Testdisk analyzed GPT and one partition,but after and deep search in analyze ,the disk seems to be dead "read I/O error""
Jul 31 00:19:24 morteza-System-Product-Name kernel: [ 7970.066739] ata3.00: configured
for UDMA/133 (device error ignored)
Jul 31 00:19:24 morteza-System-Product-Name kernel: [ 7970.066770] sd 2:0:0:0: [sdc]
Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 31 00:19:24 morteza-System-Product-Name kernel: [ 7970.066779] sd 2:0:0:0: [sdc]
Sense Key : Aborted Command [current] [descriptor]
Jul 31 00:19:24 morteza-System-Product-Name kernel: [ 7970.066788] Descriptor sense
data with sense descriptors (in hex):
Jul 31 00:19:24 morteza-System-Product-Name kernel: [ 7970.066793] 72 0b 00 00
00 00 00 0c 00 0a 80 00 00 00 00 00
Jul 31 00:19:24 morteza-System-Product-Name kernel: [ 7970.066810] 00 00 00 00
Jul 31 00:19:24 morteza-System-Product-Name kernel: [ 7970.066818] sd 2:0:0:0: [sdc]
Add. Sense: No additional sense information
Jul 31 00:19:24 morteza-System-Product-Name kernel: [ 7970.066827] sd 2:0:0:0: [sdc]
CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Jul 31 00:19:24 morteza-System-Product-Name kernel: [ 7970.066843] end_request: I/O
error, dev sdc, sector 0
Jul 31 00:19:24 morteza-System-Product-Name kernel: [ 7970.066879] ata3: EH complete
TB3 music
-------------------------------------------------
اصلا خیلی عجیب .خاموش کردم روشن کردم دیگه کار نکرد .
فابل سیستم GPT/EXT4 که EXT3 شناخته میشه.فقط Gparted درست میشناخت.یعنی میشناسه
orteza@morteza-System-Product-Name:~$ sudo fsck.ext4 -b 102400000 -B 4096 /dev/sdc1
[sudo] password for morteza:
e2fsck 1.42 (29-Nov-2011)
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdc1
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>
این خروجی mount تو syslog
Jul 31 18:04:29 morteza-System-Product-Name kernel: [ 709.317917] ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Jul 31 18:04:29 morteza-System-Product-Name kernel: [ 709.317926] ata3.00: irq_stat 0x40000008
Jul 31 18:04:29 morteza-System-Product-Name kernel: [ 709.317934] ata3.00: failed command: READ FPDMA QUEUED
Jul 31 18:04:29 morteza-System-Product-Name kernel: [ 709.317949] ata3.00: cmd 60/08:00:c2:02:00/00:00:00:00:00/40 tag 0 ncq 4096 in
Jul 31 18:04:29 morteza-System-Product-Name kernel: [ 709.317952] res 41/40:00:c8:02:00/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Jul 31 18:04:29 morteza-System-Product-Name kernel: [ 709.317959] ata3.00: status: { DRDY ERR }
Jul 31 18:04:29 morteza-System-Product-Name kernel: [ 709.317965] ata3.00: error: { UNC }
Jul 31 18:04:29 morteza-System-Product-Name kernel: [ 709.329953] ata3.00: configured for UDMA/133
Jul 31 18:04:29 morteza-System-Product-Name kernel: [ 709.329974] ata3: EH complete
Jul 31 18:04:30 morteza-System-Product-Name kernel: [ 710.362452] EXT3-fs (sdc1): error: no journal found
اینم خروجی خودِ کامنده.
sudo mount /dev/sdc1 /media/k
mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
اینم امتحان کردن همه ی superblockها به اصطلاح Backup ها......
morteza@morteza-System-Product-Name:~$ sudo fsck.ext4 -b 294912. -B 4096 /dev/sdc1
e2fsck 1.42 (29-Nov-2011)
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdc1
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>
morteza@morteza-System-Product-Name:~$ sudo fsck.ext4 -b 71663616 -B 4096 /dev/sdc1
e2fsck 1.42 (29-Nov-2011)
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdc1
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>
morteza@morteza-System-Product-Name:~$ sudo fsck.ext4 -b 512000000 -B 4096 /dev/sdc1
e2fsck 1.42 (29-Nov-2011)
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdc1
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>یکی کمک!!!!!!
موضوع: can't read superblock (دفعات بازدید: 674 بار)
