[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Distinguishing between hardware, software, and operator induced symptoms



On 11/18/2016 1:58 PM, Pascal Hambourg wrote:
Le 18/11/2016 à 15:25, Richard Owlett a écrit :
As noted in the "Invoking ddrescue" thread
[https://lists.debian.org/debian-user/2016/11/msg00641.html],
my laptop
[dedicated to educational/experimental projects which could fail
spectacularly] used to apparently successfully run ddrescue,
malfunctioned.

The most important tool is a brain with knowledge of the history.
Exemple :

Q. Did the operator change anything to the system before it failed ?

A. Yes. He created a permanent automatic mount entry in fstab for
a removable device which is not always present. BIG mistake. At
least when you do that, add the "nofail" option and use an
identifier which is less volatile than the device file.

Solution : revert the change. No need to reinstall.

If could've, would've <smile>
When I noticed that systemd was having problems with the destination disk I discovered the wall wart was unplugged.
If my _only_ problem was the fstab entry, shouldn't my sequence of:
  1. power down laptop
  2. plug in wall wart
  3. power up laptop to reboot
have worked?





Reply to: