wolfram vorher waren es 4 Partitionen

Bevor du was gemacht hast?

wolfram fdisk, parted et.c. probiert, selbst dd oder shred funktioniert nicht.

"Funktioniert nicht" als Fehlermeldung ist wenig hilfreich

    Josephus Miller
    ich kann es dir ehrlich gesagt nicht mehr sicher sagen, habe wie in einem Wahn alles mögliche versucht...
    zuletzt: mit der Windows CD in diskpart; ansonsten fdisk, parted, sfdisk, mkfs.btrfs, cfdisk, gparted, gdisk,

    gerade eben noch einmal versucht:
    ```/dev/sda:

    ATA device, with non-removable media
    Model Number: Intenso SSD Sata III
    Serial Number: AA000000000000004069
    Firmware Revision: O1225L
    Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
    Standards:
    Supported: 9 8 7 6 5
    Likely used: 9
    Configuration:
    Logical max current
    cylinders 16383 16383
    heads 16 16
    sectors/track 63 63
    --
    CHS current addressable sectors: 16514064
    LBA user addressable sectors: 268435455
    LBA48 user addressable sectors: 494925759
    Logical Sector size: 512 bytes
    Physical Sector size: 512 bytes
    Logical Sector-0 offset: 0 bytes
    device size with M = 1024*1024: 241662 MBytes
    device size with M = 1000*1000: 253401 MBytes (253 GB)
    cache/buffer size = unknown
    Nominal Media Rotation Rate: Solid State Device
    Capabilities:
    LBA, IORDY(can be disabled)
    Queue depth: 32
    Standby timer values: spec'd by Standard, no device specific minimum
    R/W multiple sector transfer: Max = 2 Current = 1
    DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
    Cycle time: min=120ns recommended=120ns
    PIO: pio0 pio1 pio2 pio3 pio4
    Cycle time: no flow control=120ns IORDY flow control=120ns
    Commands/features:
    Enabled Supported:
    * SMART feature set
    Security Mode feature set
    * Power Management feature set
    * Write cache
    * Look-ahead
    * Host Protected Area feature set
    * WRITE_BUFFER command
    * READ_BUFFER command
    * NOP cmd
    * DOWNLOAD_MICROCODE
    SET_MAX security extension
    Automatic Acoustic Management feature set
    * 48-bit Address feature set
    * Device Configuration Overlay feature set
    * Mandatory FLUSH_CACHE
    * FLUSH_CACHE_EXT
    * SMART error logging
    * SMART self-test
    * General Purpose Logging feature set
    * WRITE_{DMA|MULTIPLE}_FUA_EXT
    * 64-bit World wide name
    * {READ,WRITE}_DMA_EXT_GPL commands
    * Segmented DOWNLOAD_MICROCODE
    * Gen1 signaling speed (1.5Gb/s)
    * Gen2 signaling speed (3.0Gb/s)
    * Gen3 signaling speed (6.0Gb/s)
    * Native Command Queueing (NCQ)
    * Host-initiated interface power management
    * Phy event counters
    * READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
    * DMA Setup Auto-Activate optimization
    Device-initiated interface power management
    * Software settings preservation
    Device Sleep (DEVSLP)
    * SMART Command Transport (SCT) feature set
    * SCT Write Same (AC2)
    * SCT Error Recovery Control (AC3)
    * SCT Features Control (AC4)
    * SCT Data Tables (AC5)
    * SANITIZE feature set
    * CRYPTO_SCRAMBLE_EXT command
    * BLOCK_ERASE_EXT command
    * DOWNLOAD MICROCODE DMA command
    * WRITE BUFFER DMA command
    * READ BUFFER DMA command
    * Data Set Management TRIM supported (limit 8 blocks)
    * Deterministic read ZEROs after TRIM
    Security:
    Master password revision code = 65534
    supported
    not enabled
    not locked
    not frozen
    not expired: security count
    supported: enhanced erase
    4min for SECURITY ERASE UNIT. 4min for ENHANCED SECURITY ERASE UNIT.
    Logical Unit WWN Device Identifier: 5000000000000000
    NAA : 5
    IEEE OUI : 000000
    Unique ID : 000000000
    Device Sleep:
    DEVSLP Exit Timeout (DETO): 40 ms (drive)
    Minimum DEVSLP Assertion Time (MDAT): 31 ms (drive)
    Checksum: correct```

    fdisk /dev/sda
    Gerät enthält keine erkennbare Partitionstabelle.
    Eine neue DOS-(MBR-)Festplattenbezeichnung 0xe1843ed5 wurde erstellt.

    w
    Die Partitionstabelle wurde verändert.
    ioctl() wird aufgerufen, um die Partitionstabelle neu einzulesen.
    /dev/sda: fsync auf dem Gerät ist fehlgeschlagen: Eingabe-/Ausgabefehler

    Steht dann noch was im dmesg zu dem I/O Fehler?

    • wolfram hat auf diesen Beitrag geantwortet.

      frostschutz
      Danke für den Hinweis "dmesg", war mir vorher nicht bekannt 🙂
      Da steht ne Menge !
      [ 383.764082] scsi 1:0:0:0: Direct-Access ATA Intenso SSD Sat 5L PQ: 0 ANSI: 5
      [ 383.764901] sd 1:0:0:0: [sda] 494925759 512-byte logical blocks: (253 GB/236 GiB)
      [ 383.764995] sd 1:0:0:0: [sda] Write Protect is off
      [ 383.765007] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
      [ 383.765163] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
      [ 383.765458] sd 1:0:0:0: [sda] Preferred minimum I/O size 512 bytes
      [ 383.767101] sd 1:0:0:0: [sda] Attached SCSI disk
      [ 539.646164] ata2.00: Read log 0x10 page 0x00 failed, Emask 0x1
      [ 539.646176] ata2: failed to read log page 10h (errno=-5)
      [ 539.646184] ata2.00: exception Emask 0x1 SAct 0x4000 SErr 0x0 action 0x0
      [ 539.646192] ata2.00: irq_stat 0x40000001
      [ 539.646198] ata2.00: failed command: WRITE FPDMA QUEUED
      [ 539.646202] ata2.00: cmd 61/01:70:00:00:00/00:00:00:00:00/40 tag 14 ncq dma 512 out
      res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x1 (device error)
      [ 539.646223] ata2.00: status: { DRDY }
      [ 539.646449] ata2.00: revalidation failed (errno=-2)
      [ 539.646462] ata2: hard resetting link
      [ 539.959791] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
      [ 539.960756] ata2.00: revalidation failed (errno=-2)
      [ 544.979508] ata2: hard resetting link
      [ 545.293643] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
      [ 545.294610] ata2.00: revalidation failed (errno=-2)
      [ 545.294621] ata2.00: disable device
      [ 545.294657] ata2: EH complete
      [ 545.294705] sd 1:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=5s
      [ 545.294715] sd 1:0:0:0: [sda] tag#21 CDB: Write(10) 2a 00 00 00 00 00 00 00 01 00
      [ 545.294720] I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
      [ 545.294730] Buffer I/O error on dev sda, logical block 0, lost async page write

      Wird noch erkannt, aber dann Schreibfehler und Bus Resets.

      Wenn du noch Daten brauchst, kannst du es mit ddrescue versuchen. Ansonsten mal neu verkabeln, und schauen ob sie sich nach einem Secure Erase wieder einrenkt.

      Aber wahrscheinlich ist die einfach hinüber.

      • wolfram hat auf diesen Beitrag geantwortet.

        frostschutz

        Also die Daten hab ich am Anfang schon retten können, Gott sei Dank 🙂
        Neu verkabeln ist schwierig, alle anderen SATA Anschlüsse sind schon belegt, mit ROM und HDD oder ist es für Linux kein Problem die Anschlüsse zu vertauschen?

        Dann mal Anschlüsse tauschen und ein anderes SATA-Kabel verwenden.

          schard
          also, ein frisches Kabel angeschlossen und die Reihenfolge von sda, sdb, sdc geändert.
          Siehe da, im dmesg gibt es keinen Fehler mehr ! 🙂

          [ 0.691078] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
          [ 0.692124] ata4.00: HPA detected: current 494925759, native 494927872
          [ 0.692138] ata4.00: ATA-9: Intenso SSD Sata III, O1225L, max UDMA/133
          [ 0.692246] ata4.00: 494925759 sectors, multi 2: LBA48 NCQ (depth 32), AA
          [ 0.692886] ata4.00: Features: Dev-Sleep
          [ 0.693890] ata4.00: configured for UDMA/133
          [ 0.759978] scsi 3:0:0:0: Direct-Access ATA Intenso SSD Sat 5L PQ: 0 ANSI: 5
          [ 0.760909] sd 3:0:0:0: [sdc] 494925759 512-byte logical blocks: (253 GB/236 GiB)
          [ 0.760995] sd 3:0:0:0: [sdc] Write Protect is off
          [ 0.761005] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
          [ 0.761076] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
          [ 0.761156] sd 3:0:0:0: [sdc] Preferred minimum I/O size 512 bytes
          [ 0.762415] sd 3:0:0:0: [sdc] Attached SCSI disk

          jetzt werde ich noch einmal mit dem hotreplugin not frozen erzwingen,
          und sollte dann noch etwas beachten?

          13 Tage später

          Also lag es am Kabel? Ein Update wäre ..öhm.. hübsch.

          4 Monate später

          Guten Tag zusammen,
          es ist jetzt etwas Zeit vergangen ich weiß aber als das Problem aktuell war, hatte ich mir einfach eine neue HDD gekauft und die alte SSD erstmal beiseite gelassen. Jetzt will ich aber trotzdem sie wieder aktivieren. Für geduldige Hilfe bin ich sehr dankbar 🙂

          Stand der Dinge

          Konnte not frozen erzwingen aber eine Partition lässt sich nicht erstellen.

          dmesg gibt folgendes raus:
          viel Fehlermeldungen die vorher nicht waren und ich leider nicht verstehe...

          [ 7512.554277] ata4: SATA link down (SStatus 0 SControl 300)
          [ 7517.994634] ata4: SATA link down (SStatus 0 SControl 300)
          [ 7517.994652] ata4: limiting SATA link speed to <unknown>
          [ 7521.564647] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 3F0)
          [ 7521.567138] ata4.00: configured for UDMA/133
          [ 7761.495888] ata4: SATA link down (SStatus 0 SControl 3F0)
          [ 7766.956289] ata4: SATA link down (SStatus 0 SControl 3F0)
          [ 7766.956297] ata4: limiting SATA link speed to <unknown>
          [ 7771.322876] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 3E0)
          [ 7771.351347] ata4.00: configured for UDMA/133
          [ 7771.351369] ata4: limiting SATA link speed to 1.5 Gbps
          [ 7772.059284] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
          [ 7772.061762] ata4.00: configured for UDMA/133
          [ 8798.898981] ata4.00: Read log 0x10 page 0x00 failed, Emask 0x1
          [ 8798.898993] ata4: failed to read log page 10h (errno=-5)
          [ 8798.899000] ata4.00: exception Emask 0x1 SAct 0x80000000 SErr 0x0 action 0x0
          [ 8798.899008] ata4.00: irq_stat 0x40000001
          [ 8798.899015] ata4.00: failed command: WRITE FPDMA QUEUED
          [ 8798.899019] ata4.00: cmd 61/b8:f8:00:f7:7f/00:00:1d:00:00/40 tag 31 ncq dma 94208 out
                                  res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x1 (device error)
          [ 8798.899039] ata4.00: status: { DRDY }
          [ 8798.899146] ata4.00: revalidation failed (errno=-2)
          [ 8798.899154] ata4: hard resetting link
          [ 8799.212557] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
          [ 8799.213547] ata4.00: revalidation failed (errno=-2)
          [ 8804.305582] ata4: hard resetting link
          [ 8804.619151] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
          [ 8804.620048] ata4.00: revalidation failed (errno=-2)
          [ 8804.620057] ata4.00: disable device
          [ 8804.620088] ata4: EH complete
          [ 8804.620146] sd 3:0:0:0: [sdc] tag#5 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
          [ 8804.620157] sd 3:0:0:0: [sdc] tag#5 CDB: Write(10) 2a 00 00 00 00 00 00 00 08 00
          [ 8804.620162] I/O error, dev sdc, sector 0 op 0x1:(WRITE) flags 0x100000 phys_seg 8 prio class 2
          [ 8804.620173] Buffer I/O error on dev sdc, logical block 0, lost async page write
          [ 8804.620181] Buffer I/O error on dev sdc, logical block 1, lost async page write
          [ 8804.620185] Buffer I/O error on dev sdc, logical block 2, lost async page write
          [ 8804.620189] Buffer I/O error on dev sdc, logical block 3, lost async page write
          [ 8804.620193] Buffer I/O error on dev sdc, logical block 4, lost async page write
          [ 8804.620197] Buffer I/O error on dev sdc, logical block 5, lost async page write
          [ 8804.620201] Buffer I/O error on dev sdc, logical block 6, lost async page write
          [ 8804.620205] Buffer I/O error on dev sdc, logical block 7, lost async page write
          [ 8804.620228] sd 3:0:0:0: [sdc] tag#6 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=5s
          [ 8804.620235] sd 3:0:0:0: [sdc] tag#6 CDB: Write(10) 2a 00 1d 7f f7 00 00 00 b8 00
          [ 8804.620239] I/O error, dev sdc, sector 494925568 op 0x1:(WRITE) flags 0x800 phys_seg 23 prio class 2
          [ 8804.620835] sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
          [ 8804.620849] sd 3:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 00 00 21 f8 00 00 08 00
          [ 8804.620854] I/O error, dev sdc, sector 8696 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2
          [ 8804.621506] sd 3:0:0:0: [sdc] tag#15 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
          [ 8804.621518] sd 3:0:0:0: [sdc] tag#15 CDB: Write(10) 2a 00 00 01 22 20 00 00 08 00
          [ 8804.621524] I/O error, dev sdc, sector 74272 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2
          [ 8804.638009] sd 3:0:0:0: [sdc] tag#1 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
          [ 8804.638023] sd 3:0:0:0: [sdc] tag#1 CDB: Write(10) 2a 00 0e 84 00 00 00 05 40 00
          [ 8804.638028] I/O error, dev sdc, sector 243531776 op 0x1:(WRITE) flags 0x4000 phys_seg 168 prio class 2
          [ 8804.638056] sd 3:0:0:0: [sdc] tag#2 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
          [ 8804.638063] sd 3:0:0:0: [sdc] tag#2 CDB: Write(10) 2a 00 0e 84 05 40 00 02 c0 00
          [ 8804.638066] I/O error, dev sdc, sector 243533120 op 0x1:(WRITE) flags 0x0 phys_seg 88 prio class 2
          [ 8804.638088] sd 3:0:0:0: [sdc] tag#3 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
          [ 8804.638093] sd 3:0:0:0: [sdc] tag#3 CDB: Write(10) 2a 00 0e 84 08 00 00 05 40 00
          [ 8804.638097] I/O error, dev sdc, sector 243533824 op 0x1:(WRITE) flags 0x4000 phys_seg 168 prio class 2
          [ 8804.638113] sd 3:0:0:0: [sdc] tag#4 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
          [ 8804.638118] sd 3:0:0:0: [sdc] tag#4 CDB: Write(10) 2a 00 0e 84 0d 40 00 02 c0 00
          [ 8804.638121] I/O error, dev sdc, sector 243535168 op 0x1:(WRITE) flags 0x0 phys_seg 88 prio class 2
          [ 8804.638141] sd 3:0:0:0: [sdc] tag#5 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
          [ 8804.638146] sd 3:0:0:0: [sdc] tag#5 CDB: Write(10) 2a 00 0e 84 10 00 00 05 40 00
          [ 8804.638150] I/O error, dev sdc, sector 243535872 op 0x1:(WRITE) flags 0x4000 phys_seg 168 prio class 2
          [ 8804.638165] sd 3:0:0:0: [sdc] tag#6 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
          [ 8804.638170] sd 3:0:0:0: [sdc] tag#6 CDB: Write(10) 2a 00 0e 84 15 40 00 02 c0 00
          [ 8804.638173] I/O error, dev sdc, sector 243537216 op 0x1:(WRITE) flags 0x0 phys_seg 88 prio class 2
          [ 8805.335998] Buffer I/O error on dev sdc, logical block 8, lost async page write
          [ 8805.336002] Buffer I/O error on dev sdc, logical block 9, lost async page write
          [ 8806.791762] sd 3:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
          [ 8806.791767] sd 3:0:0:0: [sdc] Sense not available.
          [ 8806.791780] sd 3:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
          [ 8806.791781] sd 3:0:0:0: [sdc] Sense not available.
          [ 8806.791785] sd 3:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)
          [ 8806.791804] sdc: detected capacity change from 494925759 to 0
          [ 9014.180480] sd 3:0:0:0: [sdc] tag#17 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
          [ 9014.180485] sd 3:0:0:0: [sdc] tag#17 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
          [ 9134.703494] sd 3:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
          [ 9134.703507] sd 3:0:0:0: [sdc] Sense not available.
          [ 9134.703797] sd 3:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
          [ 9134.703807] sd 3:0:0:0: [sdc] Sense not available.

          Ganz ehrlich, mit den ganzen IO-Fehlern würde ich die SSD nicht mehr verwenden wollen, sie ist vermutlich hinüber.

          • wolfram hat auf diesen Beitrag geantwortet.
            8 Tage später

            Dirk Hallo Dirk,

            vielen Dank für deine ehrliche Einschätzung.
            Ich spare mir die Zeit und werde mir eine neue zulegen 🙂
            Gruß