Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #174876
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Distinguishing between hardware, software, and operator induced symptoms |
| Date | 2016-11-19 12:10 +0100 |
| Message-ID | <sFbGV-4bf-11@gated-at.bofh.it> (permalink) |
| References | <sESkW-8jW-35@gated-at.bofh.it> <sEXuh-32H-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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?
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Distinguishing between hardware, software, and operator induced symptoms Richard Owlett <rowlett@cloud85.net> - 2016-11-18 15:30 +0100
Re: Distinguishing between hardware, software, and operator induced symptoms Richard Owlett <rowlett@cloud85.net> - 2016-11-18 15:50 +0100
Re: Distinguishing between hardware, software, and operator induced symptoms Cindy-Sue Causey <butterflybytes@gmail.com> - 2016-11-18 16:10 +0100
Re: Distinguishing between hardware, software, and operator induced symptoms Richard Owlett <rowlett@cloud85.net> - 2016-11-18 17:30 +0100
Re: Distinguishing between hardware, software, and operator induced symptoms "Thomas Schmitt" <scdbackup@gmx.net> - 2016-11-18 16:30 +0100
Re: Distinguishing between hardware, software, and operator induced symptoms Richard Owlett <rowlett@cloud85.net> - 2016-11-18 17:20 +0100
Re: Distinguishing between hardware, software, and operator induced symptoms Bob Weber <bobrweber@gmail.com> - 2016-11-18 16:30 +0100
Re: Distinguishing between hardware, software, and operator induced symptoms Richard Owlett <rowlett@cloud85.net> - 2016-11-18 17:10 +0100
Re: Distinguishing between hardware, software, and operator induced symptoms Pascal Hambourg <pascal@plouf.fr.eu.org> - 2016-11-18 21:00 +0100
Re: Distinguishing between hardware, software, and operator induced symptoms Richard Owlett <rowlett@cloud85.net> - 2016-11-19 12:10 +0100
Re: Distinguishing between hardware, software, and operator induced symptoms Pascal Hambourg <pascal@plouf.fr.eu.org> - 2016-11-19 13:30 +0100
Re: Distinguishing between hardware, software, and operator induced symptoms David Christensen <dpchrist@holgerdanske.com> - 2016-11-19 04:30 +0100
Re: Distinguishing between hardware, software, and operator induced symptoms Richard Owlett <rowlett@cloud85.net> - 2016-11-19 12:10 +0100
csiph-web