<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
On 15/07/10 22:15, Peter wrote:
<blockquote cite="mid:4C3F17F3.3080301@gswd.com" type="cite">On
15/07/10 21:35, Richard Meyer wrote: <br>
<blockquote type="cite">Advice, I have plenty of, AND AT NO EXTRA
charge... ;-) <br>
<br>
I would check the bios startup messages for any SMART info about the WD
<br>
disk. <br>
<br>
If there were messages about how broken it was, I'd weep. <br>
<br>
What I would then do (regardless of SMART results), is lash out for a <br>
USB disk cage/enclosure for about $20 and put the disk in there. <br>
<br>
I would then boot without it and plug it in, and see whether Linux can <br>
see it .... <br>
<br>
I would also run smartmon against it .. (Hmmm, I don't have smartmon
any <br>
more) I'm sure others will have better ideas for disk diagnostics <br>
anyway ... <br>
<br>
If I could access the disk, I'd back up what I needed and <br>
destroy/reformat the disk as indicated by the SMART status. <br>
<br>
HTH <br>
</blockquote>
</blockquote>
<br>
<br>
<br>
<blockquote cite="mid:4C3F17F3.3080301@gswd.com" type="cite">Following
on from what Richard said, if you can get the machine running either
with the disk in place or in a USB enclosure, you can try some of the
following: <br>
<br>
In a console do "fdisk -l" and/or "cfdisk /dev/???" where ??? is the
drive in question (eg. sdc) to see if Linux can find the disk, even if
it doesn't recognise any partitions. <br>
<br>
If the above works, <br>
<br>
Run 'testdisk' (eg: 'sudo testdisk /dev/sdc' if using a ubuntu live
disk) in a console to see if there are any recoverable partitions. You
may have to install testdisk first as it is not included on a standard
ubuntu installation. If testdisk finds any info on the drive (there
is a "view files" option that sometimes works even if the partitions
are corrupt. You will need another disk (mounted partition) to copy
files to if it finds any. <br>
<br>
I'm three hours out of Perth, so can't offer much in the way of hands
on assistance, but may be able to talk you though some stuff if
required.... <br>
<br>
If none of the above works.... If Linux can not see the drive at
all.... the disk may be dead, however if you can hear it spin up when
powered on and there is no significant noise (ticking?) then you may
have a faulty PCB. The drive may be recoverable but requires
specialist knowledge..... I can put you in touch with someone who may
be able to help, if the above options fail. I recently recovered a
Drive with a fried PCB. It took weeks to recover the data (long story)
but only cost me $50.00 in parts. <br>
<br>
Cheers, <br>
Peter <br>
</blockquote>
<br>
<font color="#000000"><i><br>
Thanks Richard but I can't access the disk.
fdisk and testdisk don't find it either, Peter.<br>
<br>
It proved to be getting power when the other two disks were
disconnected and power switched on - it spun up, but with a slightly
gravelly sound which settled down after a few seconds but the closest
the system has come to recognising it was when I tried to mount it...<br>
<br>
"sudo mount /dev/sdc -t ext3 /mnt" and got the response "no
medium found on /dev/sd3".<br>
<br>
So there it is - a dead duck disk which I bought on 22nd of April 2009!<br>
<br>
Is it worth taking it back to MCG Technology to see if they can do
anything?<br>
What can you at Linux It do Scott?<br>
Do you think your guy might be better able to get access to it, Peter?<br>
<br>
Regards<br>
Dave Dartnall</i></font><br>
<br>
<br>
<blockquote cite="mid:4C3F17F3.3080301@gswd.com" type="cite"><br>
<br>
<blockquote type="cite">On Thu, 2010-07-15 at 21:08 +0800, David
Dartnall wrote: <br>
<blockquote type="cite">Now that the plug server's up again, below
is the third of three emails <br>
which didn't get through. Perhaps someone could advise/help. <br>
<br>
Hi all, <br>
<br>
I need a linux/hardware guru. My system suddenly refused to boot, and I
<br>
took it to the Windows bloke who sold it to me and who has been keeping
<br>
it going over a number of years, and he got Windows running. <br>
<br>
It has XP as well as Lucid on it, and the Windows drive now boots into <br>
Windows, (very slow if the Lucid disk is connected) but Windows systems
<br>
can't see Linux disks, so I tried a Jaunty CD disk that I had but it <br>
would only fully boot into a live session if the drive holding the
Lucid <br>
system is disconnected. <br>
<br>
With it connected, (it's a relatively new WD 500 gig drive), the Jaunty
<br>
live session boot stops after selection of the language 'English' and <br>
drops into a initramfs root prompt. <br>
<br>
Running the live session with WD 500 unplugged, gparted found the <br>
Windows disk and also my third disk which was formatted ext3 but
without <br>
any OS on it. <br>
<br>
I installed Jaunty on this and plugged the 500GB Lucid disk in and <br>
rebooted. After a _very long_ boot time, the Jaunty system comes up but
<br>
all it can see is the Windows disk... Jaunty boots quickly with the <br>
500Gb disk disconnected. <br>
<br>
It's obviously going to cost money but I need to get the Lucid system <br>
going - I'll take the box anywhere Perth Metro area... <br>
<br>
Regards and advice please. <br>
I am unable to access the WD 500GB Lucid disk - can not see it. <br>
No I have not backed up - I'll never learn! I sure will now tho'. <br>
<br>
Regards <br>
Dave Dartnall <br>
</blockquote>
</blockquote>
</blockquote>
<br>
<br>
</body>
</html>