openbsd, fsck at boot, repair files without disk

[hd77]

Hi,

I have here an old laptop running well obsd with dwm.
unfortunately, hdd seems to be a bit tired, when fw_udpdate cant install the wifi driver because of an i/o error.
problem the hdd is a unique connector and seems to be out of availability. No other choice to use that one.
so I was wondering to do something, as for the first one I was doing with linux previously : run a fsck at each startup to fix iflesystem errors.

how to do that? mean, fsck_ffs sd0a but just at openbsd boot, to ensure everything is correct?


then, how to fix files errors/unavailability/missing without booting on the openbsd disc? is it possible from web to repair some files damaged by repair them one by one (md5 comparison from web?)

thank you vm

[jggimi]

Originally Posted by harrollld

...fw_udpdate cant install the wifi driver because of an i/o error.

Please post this system's dmesg(8) and a copy of the error message from fw_update(8). The I/O error may also be logged in the dmesg(8), and/or in the file /var/log/messages, and the level of detail in the messages may differ.

...run a fsck at each startup to fix iflesystem errors....how to do that? mean, fsck_ffs sd0a but just at openbsd boot, to ensure everything is correct? .... then, how to fix files errors/unavailability/missing without booting on the openbsd disc? is it possible from web to repair some files damaged by repair them one by one (md5 comparison from web?)

fsck(8) / fsck_ffs(8) will automatically be run in preen mode at boot time if a filesystem was not previously unmounted cleanly. Preen mode will provide simple, minor fixes of metadata without data loss. If any filesystem fails to be recovered in preen mode, booting will halt. The system will be left in single-user mode so that the admin can decide what to do next. Repairing filesystem inconsistencies at this point will cause data loss. Recovery from backup may be necessary.

• If the inconsistency was due to an unplanned reboot, such as after a power failure, files opened for write at the time of the failure will be impacted.
• If the cause was due to I/O errors, data loss may be catastrophic.