Greetings all;
As those of you the the USA know, Southern WV took a beating from the weather last night and today. Heavy rains, high winds combined to kill the power for about 25% of the states population, and threaten to drown quite a few. My own automatic 20 kw nat gas standby ran from about 3:20 Thursday morning until a final restart shortly after 18:00 local. So I am busy catching up on my email, when apparently my ups did not properly restart after one of the inevitable short term power up's when the line crews are closing circuits to see if they fault again because there yet another down tree laying on the lines a half mile around the corner.
So I'm typing away on a message reply when the screen goes black, the ups has a low battery and kills the load. Restarting the ups was a matter of holding down the power button for 3 or 4 seconds, followed by a trip to the tower to tap its power switch. Everything solved as soon as its booted, right?
Wrong... No /usr/bin/X to be found. I had to totally apt-get install --re-install all of the Xorg-server stuff, 35 or 40 packages, to get the missing /usr/bin/X. That may not have been the only package that was nuked by the untimely powerdown but I've no way to verify that.
But why should a powerdown as unceremonious as pulling the plug, have deleted /usr/bin/X? It doesn't grok at this site.
Clues?
Thanks.
Cheers, Gene Heskett
On Fri, Jun 24, 2016 at 12:22:18AM -0400, Gene Heskett wrote:
But why should a powerdown as unceremonious as pulling the plug, have deleted /usr/bin/X? It doesn't grok at this site.
File system corruption?
What file system do you have? If it is something with a journal (ext4, for example) I would be surprised. If it is something experimental or less reliable (btfs, reiserfs?) then I wouldn't be surprised.
All file systems can lose data if you interrupt them while updating the file system, but some are more resiliant than others. I tend to prefer the good old ext3 or ext4 standby over flashier, faster but less resiliant newer file systems, and older, unjournaled file systems like ext2.
Have a look inside /lost+found (assuming /usr/bin is in the / partition) and see if there's anything there. You may find all your X files, and more, given generic names. Or you may find nothing at all.
Steven D'Aprano wrote:
On Fri, Jun 24, 2016 at 12:22:18AM -0400, Gene Heskett wrote:
But why should a powerdown as unceremonious as pulling the plug, have deleted /usr/bin/X? It doesn't grok at this site.
File system corruption?
What file system do you have? If it is something with a journal (ext4, for example) I would be surprised. If it is something experimental or less reliable (btfs, reiserfs?) then I wouldn't be surprised.
All file systems can lose data if you interrupt them while updating the file system, but some are more resiliant than others. I tend to prefer the good old ext3 or ext4 standby over flashier, faster but less resiliant newer file systems, and older, unjournaled file systems like ext2.
Have a look inside /lost+found (assuming /usr/bin is in the / partition) and see if there's anything there. You may find all your X files, and more, given generic names. Or you may find nothing at all.
Or unsynced RAID cache - I had it once.
On Friday 24 June 2016 02:11:31 deloptes wrote:
Steven D'Aprano wrote:
On Fri, Jun 24, 2016 at 12:22:18AM -0400, Gene Heskett wrote:
But why should a powerdown as unceremonious as pulling the plug, have deleted /usr/bin/X? It doesn't grok at this site.
File system corruption?
What file system do you have? If it is something with a journal (ext4, for example) I would be surprised. If it is something experimental or less reliable (btfs, reiserfs?) then I wouldn't be surprised.
All file systems can lose data if you interrupt them while updating the file system, but some are more resiliant than others. I tend to prefer the good old ext3 or ext4 standby over flashier, faster but less resiliant newer file systems, and older, unjournaled file systems like ext2.
Have a look inside /lost+found (assuming /usr/bin is in the / partition) and see if there's anything there. You may find all your X files, and more, given generic names. Or you may find nothing at all.
Or unsynced RAID cache - I had it once.
No raids on the property, Steven.
Thanks.
Cheers, Gene Heskett
On Friday 24 June 2016 00:51:53 Steven D'Aprano wrote:
On Fri, Jun 24, 2016 at 12:22:18AM -0400, Gene Heskett wrote:
But why should a powerdown as unceremonious as pulling the plug, have deleted /usr/bin/X? It doesn't grok at this site.
File system corruption?
Doubtfull. Two drives currently mounted, / is ext4, and /amandatapes is ext3.
What file system do you have? If it is something with a journal (ext4, for example) I would be surprised. If it is something experimental or less reliable (btfs, reiserfs?) then I wouldn't be surprised.
I have 3 sshfs mounts of other computers, but given the power outages, they could not have been mounted as thats in my /etc/rc.local and only mounted when this machine is rebooted. I may have had up to 3 ssh -Y sessions that wasn't in active use at the time of the ups shutdown.
All file systems can lose data if you interrupt them while updating the file system, but some are more resiliant than others. I tend to prefer the good old ext3 or ext4 standby over flashier, faster but less resiliant newer file systems, and older, unjournaled file systems like ext2.
So do I, after a 2 install foray into reiserfs long before it was ready for everyday use. At least a decade back. And I need to see what it takes to convert the ext3 amanda uses to ext4. That just shows how long I have been using amanda. It was ext2 only back in the late 90's. :)
Have a look inside /lost+found (assuming /usr/bin is in the / partition) and see if there's anything there. You may find all your X files, and more, given generic names. Or you may find nothing at all.
Its empty on both drives. So I am scratching my head yet.
Thanks.
Cheers, Gene Heskett
On Friday 24 June 2016 05:22:18 Gene Heskett wrote:
But why should a powerdown as unceremonious as pulling the plug, have deleted /usr/bin/X? It doesn't grok at this site.
The first time my husband accidentally switched off the power switch while his computer was running, I had to reinstall. (Meaning that I could see no other way out of the mess the file system was in!!)
It happens. Rarely, but it happens. :-(
Bad luck. :-(
Lisi
On Friday 24 June 2016 04:05:25 Lisi Reisz wrote:
On Friday 24 June 2016 05:22:18 Gene Heskett wrote:
But why should a powerdown as unceremonious as pulling the plug, have deleted /usr/bin/X? It doesn't grok at this site.
The first time my husband accidentally switched off the power switch while his computer was running, I had to reinstall. (Meaning that I could see no other way out of the mess the file system was in!!)
It happens. Rarely, but it happens. :-(
Bad luck. :-(
I guess. Anyway, the system is back amoung the living, which is what counts.
After that blast of weather, we are promised good dry weather the rest of the weekend, and that will be a great help as my pickup and a 6x12 u-haul cargo van are trapped in the yard until such time as the yellow clay under what little grass there is has dried enough.
I'm not trying to move 9500 lbs with greasy clay under the tires on the side of a hill. It has to dry and harden up enough I can leave it pulling all 4 corners and move it all w/o spinning. And I am supposed to have it unloaded and back to the drop off point 25 miles up the superpothole (I-79) by 5pm today. But thats not going to happen until I can back out into the street, and back it up into the driveway far enough an engine hoist crane can stay on the concrete slab I poured in front of the garage 8 years ago. Its long enough my pickup will be blocking the street. But there are 3 streets in this little cul-de-sac, so thats not a huge issue.
Lisi
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
Lisi Reisz lisi.reisz@gmail.com napisał(a):
The first time my husband accidentally switched off the power switch while his computer was running, I had to reinstall. (Meaning that I could see no other way out of the mess the file system was in!!)
It happens. Rarely, but it happens. :-(
At work, I had Debian 6 with /home configured as LUKS/dm-crypt volume. Most cases when power went off without shutting the system down, some files were missing at this home partition. In Debian 8 it looks like the problem is solved... or I just have too much files. MCbx