← Back to catalogue
Research draft

bad block

vr.tr.bad-block · thing-bad-block

Let an agent explain bad blocks and how they arise, relay detection, remapping and management from storage references, describe warning signs and data recovery practice in general terms, and distinguish physical bad blocks from logical errors, file corruption and bad clusters at the file system level.

Thing Registry Cross-cutting context XCT.QTY

Research draft, second pass

A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.

Researched by: Claude

Bundle → Layer → Finding → Questions Filled

4 bundles · 8 layers · 8 findings · 16 questions

Understand What a bad block is.

Definition

Definition.

Definition

Definition.

  1. What is a bad block, and how does it differ from logical errors and file corruption? definition
  2. Is the question about the concept, a drive type or a data recovery situation? boundary

Causes

Causes.

Causes

Causes.

  1. What causes bad blocks on hard disks and flash memory? definition
  2. Which entry fits NAND flash memory? action
Manage Detection and management.

Detection

Detection.

Detection

Detection.

  1. How do ECC, SMART and disk checking tools detect bad blocks? provenance
  2. Which references are standard? provenance

Remapping

Remapping.

Remapping

Remapping.

  1. How do drives and file systems remap or mark bad blocks? provenance
  2. Which sources are cited? provenance
Respond Responding to bad blocks.

Warning

Warning signs.

Warning

Warning.

  1. When do bad blocks indicate imminent failure, and what should be done, in general terms? action
  2. Which entry fits backup? action

Recovery

Data recovery.

Recovery

Recovery.

  1. How is data recovered from drives with bad blocks? provenance
  2. Which entry fits data recovery? action
Context Media and history.

Media

Media differences.

Media

Media.

  1. How do HDDs, SSDs and older media differ in bad block behaviour? provenance
  2. Which entry fits solid-state drive? action

History

History.

History

History.

  1. How was bad block handling done on early disks and floppy disks? provenance
  2. Which entry fits the history of data storage? action

Classifiers Filled

Family
Thing Registry
Category
Cross-cutting context
Entry kind
noun.quantity
Plane
XCT
Domain
XCT.QTY
Facets: substance
abstract
Facets: origin
conceptual
Facets: agency
inert
Facets: mobility
not-applicable
Facets: scale
not-applicable
Facets: affordances
observable

What it is Filled

In computer storage, a block, usually one sector, that cannot reliably hold data because of physical damage, wear or manufacturing defects, found on hard disks, solid-state drives and flash memory, detected by error-correcting codes and firmware and remapped to spare areas or marked in a bad block table by the file system; a growing number of bad blocks is a warning sign of drive failure.

Why it exists Filled

Let an agent explain bad blocks and how they arise, relay detection, remapping and management from storage references, describe warning signs and data recovery practice in general terms, and distinguish physical bad blocks from logical errors, file corruption and bad clusters at the file system level.

Distinguishing features Filled

  • Physical defect
  • Remapping
  • Failure predictor
  • Media-specific

What robots and AI may and may not do Filled

Must not

  • Ignore or hide growing bad block counts on drives holding important data.
  • Run destructive surface tests on a drive without a backup and the owner's approval.
  • Present a logical file system error as physical damage or the reverse.
  • Claim deleted or damaged data is unrecoverable without checking.

Only with a human decision

  • Wiping, reformatting or replacing a failing drive.

May

  • Read SMART data and bad block counts from drives the agent is authorized to manage.
  • Warn the owner and recommend a backup when bad blocks increase.

Moral aspects Filled

  • Failing drives can take irreplaceable photos, records and work with them.
  • Drives sold or discarded may still hold readable data in remapped blocks.

Who is affected

  • Data owners
  • Users of shared storage
  • Buyers of used drives

Owners Filled

Steward

The owner of the storage device.

Links to other meta-models Filled

parent

  • oewn-13647935-n - registry parent class

related

  • storage defect - in general terms
  • hard disk drive - and solid-state drives
  • SMART - monitoring
  • file corruption - a logical error

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Vercy registry: vr.tr.bad-block
  • Open English WordNet: oewn-13648260-n
  • WordNet: oewn-13647935-n a block that cannot reliably hold data

Direct properties not applicable Not applicable

  • typical sector size: 512 or 4096 bytes
  • SMART attribute: reallocated sector count note
  • NAND flash: wears with program-erase cycles note

Plane XCT: no invented physical properties.

Recognition optional Filled

  • Sector that cannot reliably hold data
  • Remapped sectors, bad block tables, SMART counts
  • Logical errors are software; file corruption may be unrelated; bad clusters are file system units
  • Not a visible object; a defective storage sector.

Capabilities and actions required Filled

  • explain causes
  • relay detection and remapping
  • describe warning signs
  • distinguish related errors

Hazards and failure modes required Filled

  • Data loss when bad blocks grow
  • Ignoring SMART warnings
  • Confusing physical and logical errors

Standards and interfaces required Filled

  • ATA and NVMe specifications for SMART and remapping
  • JEDEC flash endurance standards

Context of use required Filled

  • Not applicable; a storage defect.
  • factory bad blocks on flash
  • grown bad blocks from wear or damage
  • pending and reallocated sectors on hard disks
  • bad blocks marked by file systems
  • bad blocks in RAID and SSD firmware management

Sources Filled

  1. Open English WordNet 2024, synset oewn-13648260-n - sense and gloss of the concept

Open questions

  • Should SMART and wear levelling be the primary linked entries?
  • How should storage references be linked?
  • How should SSD and HDD handling be distinguished?

Machine files

Provenance

thing registry research (pass 2) · unreviewed

Built from: models/things/publications/thing-bad-block/spec.json