Skip to main content
Super User

Return to Question

edited tags
Link
ilmiont
ilmiont
  • 111
  • 3
Various recent edits to properly phrase as a question, remove superfluous comments, add important details
Source Link
ilmiont
ilmiont
  • 111
  • 3

Both drives are running the latest Samsung firmware and report no SMART errors. The filesystem is — ext4.

smartctl output from Desktop this morning:

An extended SMART test and Full LBA Scan in Samsung Magician with the drive installed in a Windows system reported no errors.

Afterwards, I rebooted back into the system and it functioned normally; however, 10 minutes later after returning to the machine having stepped away, it had diedfailed again (the shortest uptime yet endured). The console was filled with these errors:

  1. I first thought there might be a physical hardware issue. However, subsequent tests indicate the drives are consistently reported as healthy, and it's now feeling more like a filesystem issue.
  2. It is notable, I think, that everything about these two systems is different, except they are using the same model drives, and have been through the same drive migration process.
  3. I wonder if the dd has caused corruption, although no errors were reported at the time. I'm not (yet) sure how to investigate or resolve this.

Both drives are running the latest Samsung firmware and report no SMART errors. The filesystem is ext4.

smartctl output from Desktop this morning:

Afterwards, I rebooted back into the system and it functioned normally; however, 10 minutes later after returning to the machine having stepped away, it had died again (the shortest uptime yet endured). The console was filled with these errors:

  1. I first thought there might be a physical hardware issue. However, the drives are consistently reported as healthy, and it's now feeling more like a filesystem issue.
  2. It is notable, I think, that everything about these two systems is different, except they are using the same model drives, and have been through the same drive migration process.
  3. I wonder if the dd has caused corruption, although no errors were reported at the time. I'm not (yet) sure how to investigate or resolve this.

Both drives are running the latest Samsung firmware and report no SMART errors — smartctl output from Desktop this morning:

An extended SMART test and Full LBA Scan in Samsung Magician with the drive installed in a Windows system reported no errors.

Afterwards, I rebooted back into the system and it functioned normally; however, 10 minutes later after returning to the machine having stepped away, it had failed again (the shortest uptime yet endured). The console was filled with these errors:

  1. I first thought there might be a physical hardware issue. However, subsequent tests indicate the drives are consistently reported as healthy, and it's now feeling more like a filesystem issue.
  2. It is notable, I think, that everything about these two systems is different, except they are using the same model drives, and have been through the same drive migration process.
  3. I wonder if the dd has caused corruption, although no errors were reported at the time. I'm not (yet) sure how to investigate or resolve this.
Various recent edits to properly phrase as a question, remove superfluous comments, add important details
Source Link
ilmiont
ilmiont
  • 111
  • 3

dd-cloned How to investigate ext4 filesystem going read-only; fsck only sometimes reports errors; no SMART issuesonly (no hardware errors reported)?

I'm not sure how to proceed at this point. Please can I ask for suggestions on where to take this investigation process next.

Thoughts + speculations:

dd-cloned ext4 filesystem going read-only; fsck only sometimes reports errors; no SMART issues

I'm not sure how to proceed at this point. Please can I ask for suggestions on where to take this investigation process next.

Thoughts + speculations

How to investigate ext4 filesystem going read-only (no hardware errors reported)?

I'm not sure how to proceed at this point. Please can I ask for suggestions on where to take this investigation process next:

added 69 characters in body
Source Link
ilmiont
ilmiont
  • 111
  • 3
added 69 characters in body
Source Link
ilmiont
ilmiont
  • 111
  • 3
Source Link
ilmiont
ilmiont
  • 111
  • 3