Scritto da
Non Autenticato
il 2010-09-21 10:45:00.0 alle 2010-09-21 10:45:00.0
per wakko e altri nerd
Dal manuale di hdparm:
--make-bad-sector
Deliberately create a bad sector (aka. "media error") on the
disk. EXCEPTIONALLY DANGEROUS. DO NOT USE THIS FLAG!! This
can be useful for testing of device/RAID error recovery mecha‐
nisms. The sector number is given as a (base10) parameter after
the flag. Depending on the device, hdparm will choose one of
two possible ATA commands for corrupting the sector. The
WRITE_LONG works on most drives, but only up to the 28-bit sec‐
tor boundary. Some very recent drives (2008) may support the
new WRITE_UNCORRECTABLE_EXT command, which works for any LBA48
sector. If available, hdparm will use that in preference to
WRITE_LONG. The WRITE_UNCORRECTABLE_EXT command itself presents
a choice of how the new bad sector should behave. By default,
it will look like any other bad sector, and the drive may take
some time to retry and fail on subsequent READs of the sector.
However, if a single letter f is prepended immediately in front
of the first digit of the sector number parameter, then hdparm
will issue a "flagged" WRITE_UNCORRECTABLE_EXT, which causes the
drive to merely flag the sector as bad (rather than genuinely
corrupt it), and subsequent READs of the sector will fail imme‐
diately (rather than after several retries). Note also that the
--repair-sector flag can be used to restore (any) bad sectors
when they are no longer needed, including sectors that were gen‐
uinely bad (the drive will likely remap those to a fresh area on
the media)
Se uso WRITE_UNCORRECTABLE_EXT senza il parametro f, è sgamabile il fatto che il cluster sia stato danneggiato "di proposito" con tale comando?
L'errore è reversibile?
