Results 1 to 3 of 3

Thread: Tv `

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    maniac lao's Avatar
    Join Date
    02 Sep 2009
    Posts
    3,723
    Mentioned
    31 Post(s)
    Rep Power
    107

    Default Tv `

    Am un ssd care a crapat, mai are partitia si datele dar nu pot sa le accesez.
    Am incercat diverse metode, dar n-am reusit.
    Cum pot sa o corectez? Nu vrea sa rescrie superblock.
    [ 4754.216092] ata3: SATA link down (SStatus 0 SControl 300)
    [ 4768.140077] ata3: link is slow to respond, please be patient (ready=0)
    [ 4769.460085] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 4769.472469] ata3.00: ATA-10: ADATA SU750, XA044R07, max UDMA/133
    [ 4769.476947] ata3.00: 2000409264 sectors, multi 1: LBA48 NCQ (depth 32), AA
    [ 4769.499811] ata3.00: Features: Dev-Sleep
    [ 4769.540955] ata3.00: configured for UDMA/133
    [ 4769.541151] scsi 2:0:0:0: Direct-Access ATA ADATA SU750 4R07 PQ: 0 ANSI: 5
    [ 4769.541611] sd 2:0:0:0: Attached scsi generic sg2 type 0
    [ 4769.541691] sd 2:0:0:0: [sdc] 2000409264 512-byte logical blocks: (1.02 TB/954 GiB)
    [ 4769.541730] sd 2:0:0:0: [sdc] Write Protect is off
    [ 4769.541735] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
    [ 4769.541782] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 4769.541848] sd 2:0:0:0: [sdc] Preferred minimum I/O size 512 bytes
    [ 4769.544826] sdc: sdc1
    [ 4769.544987] sd 2:0:0:0: [sdc] Attached SCSI disk
    [ 4887.628085] ata3.00: exception Emask 0x0 SAct 0x80000 SErr 0x0 action 0x6 frozen
    [ 4887.628131] ata3.00: failed command: READ FPDMA QUEUED
    [ 4887.628150] ata3.00: cmd 60/08:98:80:cf:3b/00:00:77:00:00/40 tag 19 ncq dma 4096 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 4887.628199] ata3.00: status: { DRDY }
    [ 4887.628218] ata3: hard resetting link
    [ 4892.980074] ata3: link is slow to respond, please be patient (ready=0)
    [ 4897.660073] ata3: COMRESET failed (errno=-16)
    [ 4897.660107] ata3: hard resetting link
    [ 4903.012073] ata3: link is slow to respond, please be patient (ready=0)
    [ 4907.692073] ata3: COMRESET failed (errno=-16)
    [ 4907.692108] ata3: hard resetting link
    [ 4913.044075] ata3: link is slow to respond, please be patient (ready=0)
    [ 4942.748072] ata3: COMRESET failed (errno=-16)
    [ 4942.748108] ata3: limiting SATA link speed to 1.5 Gbps
    [ 4942.748111] ata3: hard resetting link
    [ 4947.800072] ata3: COMRESET failed (errno=-16)
    [ 4947.800107] ata3: reset failed, giving up
    [ 4947.800123] ata3.00: disable device
    [ 4947.800144] sd 2:0:0:0: [sdc] tag#19 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=91s
    [ 4947.800150] sd 2:0:0:0: [sdc] tag#19 Sense Key : Not Ready [current]
    [ 4947.800153] sd 2:0:0:0: [sdc] tag#19 Add. Sense: Logical unit not ready, hard reset required
    [ 4947.800156] sd 2:0:0:0: [sdc] tag#19 CDB: Read(10) 28 00 77 3b cf 80 00 00 08 00
    [ 4947.800158] I/O error, dev sdc, sector 2000408448 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
    [ 4947.800198] ata3: EH complete
    [ 4947.800294] sd 2:0:0:0: [sdc] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
    [ 4947.800299] sd 2:0:0:0: [sdc] tag#20 CDB: Read(10) 28 00 77 3b cf 80 00 00 08 00
    [ 4947.800301] I/O error, dev sdc, sector 2000408448 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [ 4947.800330] Buffer I/O error on dev sdc1, logical block 250050800, async page read
    [ 4947.800719] sd 2:0:0:0: [sdc] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
    [ 4947.800726] sd 2:0:0:0: [sdc] tag#21 CDB: Read(10) 28 00 00 00 08 02 00 00 02 00
    [ 4947.800728] I/O error, dev sdc, sector 2050 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 2
    [ 4947.800774] EXT4-fs (sdc1): unable to read superblock
    root@debian2:~# lsblk -d -fs /dev/sdc1
    NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
    sdc1 ext4 1.0 c906cd55-242f-44be-a701-26432a46ccfd
    └─sdc
    root@debian2:~# df -H
    Filesystem Size Used Avail Use% Mounted on
    udev 4.1G 0 4.1G 0% /dev
    tmpfs 822M 820k 821M 1% /run
    /dev/sda2 62G 2.0G 57G 4% /
    tmpfs 4.2G 0 4.2G 0% /dev/shm
    tmpfs 5.3M 0 5.3M 0% /run/lock
    /dev/sda1 536M 6.2M 530M 2% /boot/efi
    tmpfs 822M 0 822M 0% /run/user/0
    /dev/sdb1 984G 26G 908G 3% /media/ssd71
    root@debian2:~# mount /dev/sdc1 /media/bad/
    mount: /media/bad: can't read superblock on /dev/sdc1.
    dmesg(1) may have more information after failed mount system call.
    /dev/sdb1 984G 26G 908G 3% /media/ssd71 este alt HDD
    Doi mari vrăjmași are românul: mila pentru străini și ura pentru ai lui - Grigore Vieru

  2. #2
    RSP - TEAM zildan's Avatar
    Join Date
    05 Dec 2007
    Location
    Sudul Romaniei
    Posts
    8,977
    Mentioned
    115 Post(s)
    Rep Power
    100

    Default

    Ia vezi ca povestește acolo ca ai mai multe informații în dmesg.
    Sh40, AML, prime focus 1,5m si altele ...

  3. #3
    maniac lao's Avatar
    Join Date
    02 Sep 2009
    Posts
    3,723
    Mentioned
    31 Post(s)
    Rep Power
    107

    Default

    Pai da, dar...
    root@debian2:~# e2fsck -pcfb 32768 /dev/sdc
    e2fsck: Invalid argument while trying to open /dev/sdc
    /dev/sdc:
    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 running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
    or
    e2fsck -b 32768 <device>
    nu stiu care sunt superblock-urile de backup
    Cele 2 de mai sus nu sunt bune
    root@debian2:~# e2fsck -b 8193 /dev/sdc
    e2fsck 1.47.0 (5-Feb-2023)
    e2fsck: Invalid argument while trying to open /dev/sdc

    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 running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
    or
    e2fsck -b 32768 <device>
    Doi mari vrăjmași are românul: mila pentru străini și ura pentru ai lui - Grigore Vieru

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •