<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 15/07/12 15:12, Liviu Andronic
wrote:<br>
</div>
<blockquote
cite="mid:CABxs9VkC98tR920-KsHcjc+BrTSSn18pFXBWKOdepXNe3WnKyA@mail.gmail.com"
type="cite">
<pre wrap="">On Sun, Jul 15, 2012 at 1:59 PM, Joshua O'Leary
<a class="moz-txt-link-rfc2396E" href="mailto:joshua.oleary@btinternet.com"><joshua.oleary@btinternet.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">If you change the hard disk operating mode in the BIOS (e.g. ahci, ide etc.)
does it still have the same errors? Not all hard disks support advanced
features.
</pre>
</blockquote>
<pre wrap="">To my utter surprise, this seems to have done the trick.
I accessed the BIOS and modified the disk operating mode from
'enhanced' to 'compatible', whatever that means. Now Xubuntu boots
quickly, as expected. I checked 'dmesg' and it's clean (there are no
relevant 'error' or 'sector' messages). All in all looks great!
Thanks!
The only issue that I notice is that 'xfce4-notes' refuses to start.
CPU goes to 50% (2 cores). I'm not sure why this happens, especially
since dmesg doesn't complain. But this is part of a bigger worry: As
much as I'm happy that the system boots up gracefully again, I'd like
to perform an audit to see if the disk is damaged and / or needs
changed. Any suggestions on this point?
Regards
Liviu
</pre>
</blockquote>
Giving the output of <b>sudo fdisk -l /dev/sda</b> would be very
helpful, to find out which area of the hard disk is
damaged/faulty/corrupted. That way, we can compare it to the error,
and find out what is actually affected. Running badblocks on the
drive may also see if there are any other problems. When you run
xfce4-notes from terminal, what does it output? You could try
resetting xfce (<b>rm -rf ~/.config/xfce4</b>), which may lose some
settings but remove any problematic config files.<br>
<br>
Joshua<br>
<br>
</body>
</html>