Hi Denis, I hope that I did not miss this obvious suggestion in your past posts. If so, I regret pointing the obvious.
Did you check the file system on the drives? If you did not, here is how to do this safely: 1. check what filesystems you have at what partitions, in case that you you need it later 2. boot into recovery mode or life distribution using CD/DVD/USB, so that you are not using your hard drive(s) or SSD(s) in the machine. 3. run fsck on all partitions excluding swap. Example: fsck /dev/sda1 4. If you encounter errors, follow the instructions on how to fix them. I hope things get better soon ... Tomas On Sun, 2016-11-20 at 09:28 -0800, Denis Heidtmann wrote: > On Sun, Nov 20, 2016 at 9:16 AM, Rich Shepard < > [email protected]> > wrote: > > > On Sun, 20 Nov 2016, Denis Heidtmann wrote: > > > > > Ideas? > > > > If this were my problem the first thing I'd do is separate > > hardware from > > software issues. You wrote that you have a live USB drive with some > > distribution on it. Try booting the problem host with that, or even > > another > > distribution. > > > > If the system boots and works normally you know it's the OS > > software and > > not the hardware. Otherwise, you know it's a hardware issue. > > > > HTH, > > > > Rich > > > Has the hardware messed up the software? Sometimes it boots fine, > esp. > after I run the recovery mode. The "sometimes" nature points to > hardware, > but the repair of dpkg errors points to messed up sw. I will try > your > suggestion after running a memory check for a few hour--maybe > overnight. > > -Denis > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
