DevHeads.net

Re: wiped disk - no longer bootable

Zitat von Volker Wysk <post@volker-wysk.de>:

It's crazy. I've done this:

sfdisk -d /dev/sda > /tmp/sda.bak
sfdisk /dev/sda < /tmp/sda.bak

And now the system boots again! (It's a fresh KISS Ubuntu 19.04.)

It's from <a href="https://www.cyberciti.biz/faq/howto-copy-mbr/" title="https://www.cyberciti.biz/faq/howto-copy-mbr/">https://www.cyberciti.biz/faq/howto-copy-mbr/</a> .

The installation of Ubuntu was terribly slow. It hung at the message
"Hole die Datei ... von ..." ("Downloading(?) file ... of ..."). The
counter counted up very slowly. Seems like the Ubuntu servers are
overloaded.

Puzzled,
Volker

Comments

Re: wiped disk - no longer bootable

By Liam Proven at 07/09/2019 - 15:57

For me, more evidence of hardware problems.

If you try again, untick the option to download updates while installing.

Re: wiped disk - no longer bootable

By oxy via ubuntu-users at 07/09/2019 - 14:38

On Tue, 2019-07-09 at 19:52 +0200, Volker Wysk wrote:
Ubuntu GNOME is everything, but KISS ;).

Most likely a broken drive, second likely a broken controller of the
mobo or another part of the mobo is the culprit.

I wouldn't be surprised, if some GNOME shell install or even some other
Ubuntu flavor wouldn't run on old hardware, but if the installation
already is slow, then most likely fishy hardware is the cause, it's even
not much likely that the PEBCAK.

Shouting! Bootcamp mode! Did you replace the fine battery and
restore/upgarde the BIOS? Assuming you are using several RAM bars, did
remove all, excepted of one RAM bar and after that did replace the RAM
bar by one after another RAM bar? That's way more meaningful then
running Memtest.

"Sustainable future" + "budget" vs "the effort of
maintenance/troubleshooting + "human mortality".

Re: wiped disk - no longer bootable

By Volker Wysk at 07/10/2019 - 04:21

Zitat von Ralf Mardorf via ubuntu-users <ubuntu- ... at lists dot ubuntu.com>:

Now it's fast again. %-|

The battery has been replaced. And I have only one RAM bar.

I haven't touched the BIOS. I also couldn't find an option to restore
the BIOS from within the BIOS. How do you restore/upgarde the BIOS?

Bye

Re: wiped disk - no longer bootable

By oxy via ubuntu-users at 07/10/2019 - 05:50

On Wed, 10 Jul 2019 10:21:50 +0200, Volker Wysk wrote:
That depends on the mobo/BIOS. When replacing the battery you usually
should shortcut two pins to clear everything. Then all settings are
lost, but the BIOS is still the old BIOS. To replace the BIOS modern
mobos, even 10 years old mobos, usually provide an option via USB, if
you should have bad luck, then you need a Windows install or at least a
DOS live media. You could download the BIOS (update) and a user manual
from the mobo vendor's homepage.

Filesystem corruption (was: wiped disk - no longer bootable)

By Volker Wysk at 07/10/2019 - 07:54

Am Mittwoch, 10. Juli 2019, 11:50:56 CEST schrieb Ralf Mardorf via ubuntu-
users:
I don't have to skill to do that. The battery has been replaced in the
computer shop, where I brought the machine. I don't know where to look for
the battery, or what pins to shortcut...

What does "option via usb" mean? The mobo downloading the upgrade from an USB
stick? I've looked around in the BIOS, but haven't seen anything like that.

I also don't know the mobo vendor. There is printed "ASUS M5A7BLLE", or
something like this, on it. It's hard to read. Is that the vendor and model
number?

I don't have Windows, never had.

But could it really be the BIOS, being defective?

I have a different (comparatively small) problem with the BIOS: It doesn't
boot from the first HDD/SSD. There only comes an empty screen with a blinking
cursor. Only when you open the mobo's boot menu, you can select the boot
device and then it boots fine.

Bye
Volker

Re: Filesystem corruption

By compdoc at 07/10/2019 - 09:28

Here are the various bios releases for your board and the main reasons
for each release:

Version 2101
2015/04/23
M5A78L LE BIOS 2101
Enhance compatibility with some USB devices.

Version 2001
2014/08/29
M5A78L LE BIOS 2001
Improve system stability.

Version 1802
2013/12/19
M5A78L LE BIOS 1802
Improve system stability.

Version 1601
2013/01/22
M5A78L LE BIOS 1601
Add LAN 8111F support.

Version 1503
2012/12/04
M5A78L LE BIOS 1503
1.Improve system stability.
2.Improve memory compatibility.

Version 1401
2012/09/11
M5A78L LE BIOS 1401
Improve system stability.

Version 1201
2012/08/02
M5A78L LE BIOS 1201
Improve system stability.

Version 1003
2012/04/10
M5A78L LE BIOS 1003
Improve system stability.

Version 0902
2012/02/28
M5A78L LE BIOS 0902
Improve memory compatibility.

Version 0801
2011/12/09
M5A78L-LE BIOS 0801
"1. Improve system stability
2. Support new CPUs. Please refer to our website at:
http://support.asus.com/cpusupport/cpusupport.aspx?SLanguage=en-us"

Version 0604
2011/10/09
M5A78L LE 0604 BIOS
Support new CPUs. Please refer to our website at:
<a href="http://support.asus.com/cpusupport/cpusupport.aspx?SLanguage=en-us" title="http://support.asus.com/cpusupport/cpusupport.aspx?SLanguage=en-us">http://support.asus.com/cpusupport/cpusupport.aspx?SLanguage=en-us</a>

Version 0503
2011/10/06
M5A78L LE 0503 BIOS
Support new CPUs. Please refer to our website at:
<a href="http://support.asus.com/cpusupport/cpusupport.aspx?SLanguage=en-us" title="http://support.asus.com/cpusupport/cpusupport.aspx?SLanguage=en-us">http://support.asus.com/cpusupport/cpusupport.aspx?SLanguage=en-us</a>

Version 0407
2011/05/05
M5A78L LE BIOS 0406
Support new CPUs. Please refer to our website at:
<a href="http://support.asus.com/cpusupport/cpusupport.aspx" title="http://support.asus.com/cpusupport/cpusupport.aspx">http://support.asus.com/cpusupport/cpusupport.aspx</a>

Version 0202
2011/04/07
M5A78L LE BIOS 0202
Initial release

Re: Filesystem corruption

By compdoc at 07/10/2019 - 09:17

If everything worked fine for a long time its doubtful the bios is the
problem, however I always make sure the bios is the latest available.
There can be bugs fixed in the bios versions, and they often make minor
changes to make the system work better with various brands of ram.

In your case, the last bios released was Version 2101 released on
2015/04/23. You would  need to see what version you have, and then read
the instructions on how to flash.

M5A78L LE BIOS 2101

Re: Filesystem corruption

By Volker Wysk at 07/13/2019 - 10:58

Zitat von compdoc < ... at hotrodpc dot com>:

I have done this. The version I had was 1503.

Upgrading really fixed a problem with booting. This was mentioned
elsewhere in this thread.

Cheers
Volker

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By Liam Proven at 07/10/2019 - 08:43

On Wed, 10 Jul 2019 at 13:56, Volker Wysk <post@volker-wysk.de> wrote:
You are being very inconsistent here.

On the one hand you are insisting that you want an exceedingly complex
disk configuration that is scaring me, as a jadad professional of over
30 years' experience.

Then the next minute you can't change a battery?

*Really*?

Yes, exactly that.

But this is one reason I am suggesting dual-booting with Windows.

ASUS is the make.

The rest is the model.

Did you try putting it into Google?

If you did you would have found that it seems to be a typo.

I think you meant

M5A78L LE

It's here:

<a href="https://www.asus.com/us/supportonly/M5A78L%20LE/HelpDesk/" title="https://www.asus.com/us/supportonly/M5A78L%20LE/HelpDesk/">https://www.asus.com/us/supportonly/M5A78L%20LE/HelpDesk/</a>

Check your BIOS version, since you have not told us. See what they
have for download. If it's newer, update it.

May be worth it.

Yes.
BIOSes are software. Software has bugs.

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By Volker Wysk at 07/10/2019 - 09:30

Zitat von Liam Proven < ... at gmail dot com>:

I've found the battery now.

I need some time off... Sorry... :-((

Yes, this can be. Like I've told, it's hard to read.

In the BIOS screen, in "System Information", under "Bios Information",
there is: "Version: 1503" and "Build Date: 11/14/12". At the bottom
there is "v02.61 (C)Copyright 1985-20011, American Megbatrends, Inc."

Let me check the link which you've provided (Asus).

In the BIOS, I have found an "ASUS EZ Flash 2 tool" now. This must be
that "option via usb". It says "Press ENTER to run the utility to
select and update BIOS".

I'll dig into that!

Bye

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By Volker Wysk at 07/10/2019 - 13:47

Hi!

Zitat von Volker Wysk <post@volker-wysk.de>:

I've downloaded the latest BIOS update, along with the mainboard
manual. If formated an USB stick with file system FAT, and placed the
BIOS update Zip on it. When I enter the ASUS EZ Flash 2 tool (in the
BIOS), there comes the message "There are no existing drive!", and the
tool is left immediately (after keypress). It doesn't matter if the
USB stick is in plugged in the monitor or directly in the motherboard,
at the back of the PC. Or if I plug the USB stick at all.

This is strange, since I've already entered that tool before, and
there was no such message.

Looks like I won't be able to update the BIOS, isn't it?

Bye
Volker

Re: Filesystem corruption

By compdoc at 07/10/2019 - 13:55

You have to unzip the files and place them in the root of the usb stick.
you really only need the bios file. syas its about 800k in size

Re: Filesystem corruption

By Volker Wysk at 07/10/2019 - 14:24

Zitat von compdoc < ... at hotrodpc dot com>:

You are right. I've unpacked the ROM and placed it on the USB Stick.
Then I entered the BIOS tool again, and there was no error message any
longer. I was able to make a backup and flash the new ROM. After
rebooting, the first hard disk is found, and booted from. This means,
the other (smaller) problem with the BIOS has gone away.

That BIOS error message "There are no any drives" (or similar), when
entering the flash tool, was very misleading.

Bye!

Re: Filesystem corruption

By compdoc at 07/10/2019 - 18:06

Great to hear. Are you not using the ssd, atm? I thought you said you
were booting from the hdd?

If so, why not power down, disconnect the hdd, place the ssd on the
first sata port in your system. (can be numbered 0 or 1)

Install ubuntu on the ssd using LVD and encryption as you like, or
normally do. I would recommend Ubuntu-Mate 18.04LTS, unless you have a
good reason to use a newer version. Newer versions are not always
stable. I use mate because I like to log in remotely, and I like mate
desktop layout. But any flavor of LTS is fine.

Anyway, allow the ubuntu installer to choose the partitioning because
anything else is too much work. then boot it, and give it a workout.
When you know that its stable, attach the hdd to the second port, and in
the bios make sure it continues to boot from the ssd, and boot and
access your files. On some systems, the first two sata ports are the
fastest.

Newer systems allow you to define the drive as an ssd in the bios, to
have the best compatibility/speed. I doubt yours has that. I used to
build systems with boards just like those. Long ago.

Re: Filesystem corruption

By Volker Wysk at 07/13/2019 - 11:23

Zitat von compdoc < ... at hotrodpc dot com>:

I'm doing this, with the HDD plugged and the SSD unplugged. I'm
"giving it a workout" now. So far, it looks good, no corruption in
sight.

Next, I'll try to set up my SSD-as-a-cache thing again. When
corruption is detected afterwards, it should be the SSD / SSD-Cache.

Cheers
Volker

Re: Filesystem corruption

By Volker Wysk at 07/11/2019 - 12:09

Zitat von compdoc < ... at hotrodpc dot com>:

I mean, the GRUB boot menu starts from the first disk. That's the HDD
right now.

I have installed Ubuntu 19.04 on both the HDD and the SSD. But I am
*not* able to reproduce the corruption problem, on either disk. The
computer appears to run fine.

I want the latest Gnome, therefore I've chosen Ubuntu 19.04. But
that's not relevant for troubleshooting the problem, or is it?

But the first point release, 19.04.1 should be more stable. Or..?

I don't quite get it. Why do you need an LTS version? To rule out
sources of error?

That's the problem, you can't know it's stable. (You only can know
when it's NOT stable.)

The ubuntu 19.04 running here, seems to be stable, but...

Bye

Re: Filesystem corruption

By Liam Proven at 07/11/2019 - 12:56

On Thu, 11 Jul 2019 at 18:11, Volker Wysk <post@volker-wysk.de> wrote:
That's good, right?

But we do not know yet if it's the newer BIOS.

Are you using LVM + encryption + caching?

There won't be a point release of 19.04. Short-term editions don't get
point releases. Only LTS editions get them.

Many of us, me included, for machines which we use for work, only run
LTS releases. I don't run the short-term support editions on any of my
machines at the moment, and when I have had machines with them, they
are for testing and playing around, not for serious use.

Partly because upgrading every 6 months is a pain. Especially because
sometimes things do not work right when you do. For example, I can
only bear to use GNOME 3 if it is fairly heavily customised with
extensions. In my experience, when you update to a new release, about
half your GNOME extensions stop working. This can lead to an unusable
desktop, e.g. can't log in, or can't run programs, or can't log out,
or can't update/remove extensions.

So I only use LTS editions.

Partly because LTS releases get more testing and if there are serious
problems they get fixed. With non-LTS ones, if there is a non-fatal
problem, it might not get fixed until the next release, meaning you
have to just live with it for 6 months.

Then you might get new problems with the new release.

Re: Filesystem corruption

By Volker Wysk at 07/11/2019 - 14:53

Zitat von Liam Proven < ... at gmail dot com>:

It depends...

I'm installing ubuntu 19.04 with lvm+encryption right now. The
slow-installer problem seemed to strike again. The download bandwidth
is fluctuating very much.

That's bad news.

How do you keep Gnome3 up to date? Are there Gnome-PPAs? Kubuntu had 2
PPAs for KDE, but the upgrade to the newest KDE didn't seem to work
well. Actually, there were a lot of problems with KDE.

I guess you do a do-release-upgrade to upgrade to the next LTS
release. Does this cause problems? I had a Kubuntu 16.04 LTS, which I
tried to upgrade to 18.04 LTS with do-release-upgrade. This completely
wrecked my system. I had to set up everything again.

The 16.04 LTS version was quite buggy with respect to KDE, even though
it was an LTS release. I mean it had packaging bugs, amongst others.

Thanks for your explaination. It means that I will probably stick with
LTS versions.

Bye
Volker

Re: Filesystem corruption

By Liam Proven at 07/11/2019 - 16:26

On Thu, 11 Jul 2019 at 20:56, Volker Wysk <post@volker-wysk.de> wrote:
Good luck.

Like I said before: you could just untick "download updates when
installing." You can always just update when you're done, and that
way, you can do other stuff at the same time.

Not really. Maybe it's just because I'm old but 2 years doesn't seem
like such a long time any more.

LTS to LTS updates seem to be slightly more reliable than
standard-to-standard ones. I suppose they get more testing, too.

But upgrading is hazardous, yes. Especially if you customise your
system, and I do.

I don't think I've ever had it totally fail, though. 18.04 was
troublesome; it failed half way through, so I just did the usual:

sudo -s
apt install -f
apt full-upgrade -y

... and it finished normally. Unity had been uninstalled, so I
manually reinstalled that. So had my Synaptics touchpad drivers, so
later, I reinstalled them too.

Now the machine works fine again, but I sort of wish I hadn't upgraded
-- there's no useful improvement over 16.04 for me, and it was faster
before.

I don't. I run Unity on Ubuntu and XKFE on openSUSE.

I've tried GNOME 3 on both, and on Fedora. I don't like it.

I think I answered this before.

I wouldn't. Serious bugs in the LTS version will be fixed, because
it's an LTS. If they can't, they will upgrade GNOME for you. It's
happened before with Firefox and LibreOffice.

This I can believe. I don't like it much either.

I installed LXQt on my KDE laptop and I like it more.

Yes.

It can.

You're welcome. LTS releases do make for a quieter life. :-)

You can always dual-boot the current release as a standby and if you
want to experiment.

Re: Filesystem corruption

By Volker Wysk at 07/16/2019 - 11:21

Zitat von Liam Proven < ... at gmail dot com>:

What exactly does "dual-boot" mean? Having two different systems, with
/home on a separate partition, with it being mounted by either, when
running?

V.

Re: Filesystem corruption

By Liam Proven at 07/16/2019 - 12:21

On Tue, 16 Jul 2019 at 17:23, Volker Wysk <post@volker-wysk.de> wrote:
The shared /home is optional . Just 2 OSes side by side in their own
partitions. That's all it means.

Re: Filesystem corruption

By Oliver Grawert at 07/16/2019 - 11:49

hi,
Am Dienstag, den 16.07.2019, 17:21 +0200 schrieb Volker Wysk:
simply booting two different OSes (or two different versions of the
same OS) while picking between them on boot

*NEVER EVER* !!! share your home between two OSes or different releases
... the way an application stores data, passwords or configs might be
completely different between the two versions on the different
releases/OSes, formats might have changed etc. this will likely cause
corruption and/or application breakage.

ciao
oli

Re: Filesystem corruption

By Liam Proven at 07/16/2019 - 12:23

We've argued over this before.

Your claim is wrong. This is not correct.

[1] If you use a different username it is 100% guaranteed safe. That's
all it takes.

[2] Even if you use the same username, so long as it is the only user
account on both/all the Linuxes, it will usually work fine. I have
done this, repeatedly. It works.

However, yes, option #1 is easier and safer.

You keep saying it *will* fail and *will* break. This is not the case.
There _can_ be problems but it does work. I know because I have done
it, myself, personally.

Re: Filesystem corruption

By Volker Wysk at 07/16/2019 - 12:05

Zitat von Oliver Grawert < ... at ubuntu dot com>:

Okay. Good thing you pointed it out.

V.W.

Re: Filesystem corruption

By =?iso-8859-1?Q?... at 07/16/2019 - 12:02

Deseo salir del grupo como puedo hacerlo?
hi,
Am Dienstag, den 16.07.2019, 17:21 +0200 schrieb Volker Wysk:
simply booting two different OSes (or two different versions of the
same OS) while picking between them on boot

*NEVER EVER* !!! share your home between two OSes or different releases
... the way an application stores data, passwords or configs might be
completely different between the two versions on the different
releases/OSes, formats might have changed etc. this will likely cause
corruption and/or application breakage.

ciao
oli

Re: Filesystem corruption

By Liam Proven at 07/16/2019 - 12:24

On Tue, 16 Jul 2019 at 18:05, eric avendaño cruz < ... at hotmail dot com> wrote:
This is an English language group.

Please bottom quote.

If you want to leave, instructions are in the signature on every
message you get.

Re: Filesystem corruption

By C de-Avillez at 07/16/2019 - 12:18

On Tue, Jul 16, 2019 at 4:03 PM eric avendaño cruz < ... at hotmail dot com> wrote:
Sorry, can read Spanish, pero no hablo. So, there it goes:

At the bottom of *every* email sent thru the mailing list you have:

"ubuntu-users mailing list
<a href="mailto:ubuntu- ... at lists dot ubuntu.com">ubuntu- ... at lists dot ubuntu.com</a>
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-users"
^^^^^^^

Cheers,

..C..

Re: Filesystem corruption

By Liam Proven at 07/11/2019 - 06:12

"LVD"?

LVM?

I'd say, let's start with keeping it simple.

Agreed.

A fair point.

Maté does allow that, but so does XFCE which I happen to prefer,
because I like vertical taskbars. LXDE/LXQt should be fine too.

It's mainly only GNOME and Cinnamon that don't because they can only
work via OpenGL rendering.

In theory KDE can but I have experienced many problems trying to get
KDE 5 to work in VMs (which is in some ways quite similar to using a
remote connection.)

Re: Filesystem corruption

By oxy via ubuntu-users at 07/10/2019 - 14:07

On Wed, 10 Jul 2019 11:55:25 -0600, compdoc wrote:
Correct, the OP needs to unzip first, however, the BIOS should be able
to access a valid fat32 partition, even if there's no usable file on
it. My old (now unused) mobo comes with this "ASUS EZ Flash 2 tool",
too.

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By Volker Wysk at 07/10/2019 - 13:57

Zitat von Liam Proven < ... at gmail dot com>:

vaio /tmp/rp $ ll M5A78L-LE-ASUS-2101.zip
-rw-r--r-- 1 v v 858650 Jul 10 19:55 M5A78L-LE-ASUS-2101.zip
vaio /tmp/rp $ unzip M5A78L-LE-ASUS-2101.zip
Archive: M5A78L-LE-ASUS-2101.zip
inflating: M5A78L-LE-ASUS-2101.ROM
vaio /tmp/rp $ ll M5A78L-LE-ASUS-2101.ROM
-rw-r--r-- 1 v v 2097152 Apr 23 2015 M5A78L-LE-ASUS-2101.ROM
vaio /tmp/rp $ file *ROM
M5A78L-LE-ASUS-2101.ROM: data

Bye

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By oxy via ubuntu-users at 07/10/2019 - 09:48

On Wed, 10 Jul 2019 15:30:31 +0200, Volker Wysk wrote:
:)

For your benefit, always pull the mains plug.
For the benefit of your computer, get rid of static charge.

I didn't read this article, excepted of the quoted part, it's funny:

"Ground Your Body

The fastest way to get rid of static electricity in the body is to let
the electricity do what it wants – discharge from your body into the
ground. To allow this, touch any conductive material not isolated from
the ground such as the screw on a light switch's panel or a metal
streetlight pole. You can also remove your shoes and socks and stand on
the ground if you are outside." -
<a href="https://sciencing.com/rid-static-electricity-body-5862942.html" title="https://sciencing.com/rid-static-electricity-body-5862942.html">https://sciencing.com/rid-static-electricity-body-5862942.html</a>

It is, you don't need to install Windows ;).

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By Volker Wysk at 07/13/2019 - 11:06

Zitat von Ralf Mardorf via ubuntu-users <ubuntu- ... at lists dot ubuntu.com>:

Are they serious with "remove your shoes and socks and stand on the
ground if you are outside"? The rest sound reasonable.

When I want to de-charge, I touch that protection conductor of a power socket.

Bye!

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By Gene Heskett at 07/13/2019 - 12:59

Since your socks are generally slightly damp, thats the best solution.

However, and dependent on the flooring, one could develop a charge
walking back to where you are working, so generally speaking, an
anti-static wrist strap should be worn and clipped to the chassis of
whatever your are working on. Those normally have a relatively large
resistor incorporated in the lead to wrist strap connection that is
large enough to keep you from a dangerous current thru your body should
the other arm accidently come in contact with the high side of the line
power should you be inattentive enough to not have unplugged it from its
power source.

The danger level directly thru the heart muscle is usually considered to
be 20 microamps, a current you will not feel. And it extends upward to
about 20 milliamp's, which you will feel, above that level the heart
will be frozen, and will if the current is removed in a minute or two by
some one noticing your predicament, generally start back up with a
normal beat rhythm.

Its the "window" between 20 microamp's and 20 milliamp's thats dangerous,
causeing fibrillation and it doesn't pump enough blood to keep you
alive. Thats how a defibber kit and its paddles work, by slamming a huge
charge thru the heart to freeze it for a fraction of a second and allow
the heart to resume its normal function.

I would not bet my life on it being grounded. Depending on who wired it,
it could even be hot. 99% of electricians are male AND nominally 30% of
those are color-blind.

Cheers, Gene Heskett

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By Colin Law at 07/13/2019 - 16:59

On Sat, 13 Jul 2019 at 18:01, Gene Heskett < ... at shentel dot net> wrote:
Where did you get that figure from? I thought it was about 10%

Colin

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By Gene Heskett at 07/13/2019 - 23:28

I've seen other figures too Colin, some of which are SWAGs for sure, but
this one came from a test kit our schools use, generally in the first or
2nd year for the student. And after considering that, I did some poking
around at the tv station and I found 8 of our male employees out of a
mixed sex bag of about 55, that had some color problems. So I made sure
those in production or on air switching could read a vectorscope (this
was in never twice same color (NTSC) days for US broadcasting, we've
been digital for 11 years now). This improved our on air color
considerably, and without having to shuffle otherwise talented folks to
someplace where they couldn't hurt us.

And I must say that we had the cream of the talent available in our area
working for us. That was a blessing for me, because I could teach them
the technical details they needed to know so easily.

A little known fact between the usual white person's face or the blackest
person's face, is that while the length of a fuzzy bar on the
vectorscope screen that is the face, may vary some because of the
variable reflection, the color vector that bar points to doesn't vary.
We are all the same color, just different brightnesses.

Your trivia factoid for the day. :)

Cheers, Gene Heskett

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By oxy via ubuntu-users at 07/13/2019 - 15:51

On Sat, 13 Jul 2019 12:59:11 -0400, Gene Heskett wrote:
As long as we don't work for something very expensive high-tech, I'm
completely against it. We could replace a CMOS chip etc., but not a
human live. We do all our work with our hands and between our hands is
the heart. I suspect it's way better, if current has a chance to find
the less resistant way from our right hands to or right feet, than from
or right hand, via the heart, to our left wrist. I'm still in favour of
isolating transformers, especially when using anti static wrist
straps.

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By oxy via ubuntu-users at 07/13/2019 - 13:17

On Sat, 13 Jul 2019 12:59:11 -0400, Gene Heskett wrote:
Gotcha old man! That's what an isolating transformer is good for :p.
Actually there is _no_ f???ing hight side, if you use galvanic
isolation :p.

Here Gene and I are two of a kind again :). I only want to add, that in
old buildings a lot of braindead people most likely did insane things,
that wasn't done by professional electricians in the first place ;).

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By oxy via ubuntu-users at 07/13/2019 - 13:36

On Sat, 13 Jul 2019 19:17:02 +0200, Ralf Mardorf wrote:
Jaded remark: Theoretically RCCBs and correct wiring might replace an
isolating transformer. However, in practise it's impossible to unplug
power sources, if you are troubleshooting hardware and I wish I would
own an isolating transformer at home, since this is the only solution
to rule out fatal accidents.

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By Gene Heskett at 07/13/2019 - 22:06

fleabay has been known to have them occasionally, bigger ones generally
honking big toroids. Very quiet, very efficient. Both heavy and drain
your bank account 'spensive. I bought a 120-240 several years ago,
thinking it would be handy. Cost me about a buck a pound for trucking,
so I've about two bills in it, Was hopeing the 240 winding had a
centertap, but struck out, the 5th, green wire must be a faraday or
possibly an ohmic connection to the toroid core which is likely a long
strip of silicon steel wound to make the core since at 60 HZ, ferrites
would saturate and the curie point temp of most ferrites might make for
some interesting effects at higher loads. So I've only had it hooked up
to test. Weighs right at 70 lbs for a 2kw rating. And while I do have
240 everyplace I have put permanent power here at the coyote.den, I
still haven't found a permanent use for it. Thinking sometimes costs me
money. :(

Cheers, Gene Heskett

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By oxy via ubuntu-users at 07/13/2019 - 14:38

Btw. since Gene and I were video and audio engineers. I added a switch
to one of my 19" audio effects, that allows to cut of ground completely.
This kind of brute force is strictly forbidden in Geramny. Ground lift
needs to be done by a safety capacitor (AC resistance). I know better.
Kids, don't do this at home, to get rid of ground loops.

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By Gene Heskett at 07/13/2019 - 22:10

Even that capacitor can be a dangerous problem child, but you knew that
allready, Ralf.

Cheers, Gene Heskett

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By oxy via ubuntu-users at 07/13/2019 - 12:28

On Sat, 13 Jul 2019 17:06:27 +0200, Volker Wysk wrote:
Unfortunately testing earthing is tricky.

Since you have got a "de" email address, read this
<a href="https://www.elektrikforum.de/threads/erdung-selbst-testen.14733/" title="https://www.elektrikforum.de/threads/erdung-selbst-testen.14733/">https://www.elektrikforum.de/threads/erdung-selbst-testen.14733/</a>. Old
buildings vs new buildings. I never experienced an issue in new
buildings, but in old buildings I experienced more issues, than correct
earthing or neutral conductors.

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By oxy via ubuntu-users at 07/13/2019 - 12:06

On Sat, 13 Jul 2019 17:06:27 +0200, Volker Wysk wrote:
Where in Germany do we find screws on a light switch's panel?
Perhaps a dirty cheap hot sheet hotel has got light switch panels with
screws, but then those screws are not necessarily grounded and they
might be isolated by paint anyway.

Today's ground wire colour in German is yellow+green, but in old
buildings it could be red, while AFAIK red for 3-phase current could be
a phase in old buildings.

Nobody knows what kind of bad wiring somebody has done inside the
joint boxes. For me there doesn't exist a colour for neutral wire, I
always test it.

This article should give an idea how to minimize potential differences,
but it's "funny" and inaccurate. Touching radiators or mixer taps
usually does work.

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By Volker Wysk at 07/13/2019 - 12:51

Zitat von Ralf Mardorf via ubuntu-users <ubuntu- ... at lists dot ubuntu.com>:

I mean that normal, round power socket, with the two holes for the
plug's connectors, and the two contacts at the sides in between. I
think they are called "Schutzleiter" (protective conductor), but I'm
not sure.

Bye
V.W.

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By oxy via ubuntu-users at 07/13/2019 - 16:32

On Sat, 13 Jul 2019 18:51:29 +0200, Volker Wysk wrote:
That's correct, but as a matter of principle your fingers have no place
in the outlet sockets, even not if you just want to touch perfectly
correct wired earth. Hands off!

An interesting question, where do we connect the anti static wrist
straps, if need to fear colour blind electricians?

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By Gene Heskett at 07/13/2019 - 22:45

To the chassis frame of what you are working on. But perhaps I've not
emphasized that the alligator clip and wire leading to the strap has a
very high resistance between it and the strap, something generally in
the 3 to 6 megohm range, and not a bulk carbon but something that can
take the local wall socket voltage virtually forever. Spiral cut in
carbon film generally has a high enough long term voltage withstand that
its chance of failing short are nil. So the chances of receiving a
lethal shock from a wrist strap is so close to impossible that the odds
are very very long and don't enter into most calculations.

If in doubt, and you don't have one of the pocket sniffers handy, stand
on a dry floor, and gently touch the chassis with the back of the hand
in a slow rubbing motion. Thats a very sensitive area, if the rubbing
motion is dead smooth feeling, it should be grounded, but if a vibration
can be felt as the back of the hand is sliding with a feather touch, its
not properly grounded, and its time to get out a meter and see just what
the heck you do have. In the case of an old building you may want to
carry a 50 foot roll of wire and a short metal rod you can step into the
ground a foot, and use that for the meters common. Throw the rod and
wire out the nearest window, step the rod into the grass, and connect
the wire to it. The rod of course should not be alu because the oxide
may take 400 volts to penetrate, copper is best but steel is ok for
this. Pita to setup, but at least you will KNOW what you're dealing
with.

Cheers, Gene Heskett

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By Sarunas Burdulis at 07/10/2019 - 08:31

On 7/10/19 7:54 AM, Volker Wysk wrote:
To get BIOS reset/upgrade info you'll need your motherboard's manual.
You can get it from ASUS (<a href="https://www.asus.com/support" title="https://www.asus.com/support">https://www.asus.com/support</a>), but you'll need
a model number. As you noticed, it's printed on the motherboard, but can
also be found out from a running Linux system, using 'dmidecode' or
'lshw' and possibly some other utilities. For example:

$ sudo dmidecode|less
... ... ...
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: PRIME X370-A
Version: Rev X.0x
... ... ...

Motherboard model is 'PRIME X370-A'.

Regarding your HDD and SSD issues, you probably already did this, but
just in case: try replacing SATA cables.

Good luck.

Re: Filesystem corruption (was: wiped disk - no longer bootable)

By Volker Wysk at 07/10/2019 - 08:02

Zitat von Volker Wysk <post@volker-wysk.de>:
... the first hard disk (where the MBR is placed) being the first one
in the boot menu's list.

Bye

Re: wiped disk - no longer bootable

By Gene Heskett at 07/09/2019 - 19:38

Cheers, Gene Heskett