| View previous topic :: View next topic |
| Author |
Message |
TBerk
Guest
|
 Posted: Fri Oct 10, 2008 8:03 am Post subject: Re: Fried hard disk chip - recovery strategies |
 |
|
Your Hard Drive is suffering (likely) more than a single chip failure.
Just focusing on your one burnt chip may not be enough.
Traditionally the DIY version was to obtain a same model HD and
carefully swap the whole electronics package over to the bad unit, just
long enough to transfer the data off.
If you try that you can do so as your own risk taking behavior dictates.
How to do it? - Google is your friend. Be Careful. (Better yet -->)
Another option is to send it out to a data recovery service; they
usually will charge a two tier schedule: an initial, (usually
non-refundable) minimum to take it on, and another fee to actually get
the data onto another HD or DVD, etc.
Good Luck with that and I'll end off with the following recommendation:
Single Point of Failure can exist in your backup plan as well. CD-Rs and
DVD-Rs are really cheap these days. Your time is your own but back up
your back-up; store a quarterly version offsite somewhere.
TBerk |
|
| |
|
 Back to top |
The Natural Philosopher
Guest
|
| Posted: Fri Oct 10, 2008 1:36 pm Post subject: Re: Fried hard disk chip - recovery strategies |
|
|
Geico Caveman wrote:
| Quote: | Hello,
This is a Maxtor Diamondmax 16, 300GB ATA/133 HDD (3.5"). I bought it 3
years ago in a pre-integrated USB enclosure to serve as my backup disk. I
had an encrypted (luks) filesystem on the disk. A few weeks ago, the disk
stopped working. I tried using a different external HD enclosure. One of
the chips on the disk melted and smoked. I tried it again later with a
different enclosure, same story. Probably the original enclosure had some
kind of a safety interlock that tripped when the power characteristics of
the disk changed.
dmesg indicates :
[ 218.627976] usb 4-6: new high speed USB device using ehci_hcd and
address 6
[ 218.761247] usb 4-6: configuration #1 chosen from 1 choice
[ 218.761657] scsi7 : SCSI emulation for USB Mass Storage devices
[ 218.761973] usb-storage: device found at 6
[ 218.761979] usb-storage: waiting for device to settle before scanning
[ 223.750878] usb-storage: device scan complete
[ 229.352472] usb 4-6: USB disconnect, address 6
[ 229.352904] scsi 7:0:0:0: Device offlined - not ready after error
recovery
[ 269.395761] usb 4-6: new high speed USB device using ehci_hcd and address
7
[ 269.528865] usb 4-6: configuration #1 chosen from 1 choice
[ 269.529257] scsi8 : SCSI emulation for USB Mass Storage devices
[ 269.529666] usb-storage: device found at 7
[ 269.529671] usb-storage: waiting for device to settle before scanning
[ 274.518486] usb-storage: device scan complete
[ 280.120104] usb 4-6: USB disconnect, address 7
[ 280.120292] scsi 8:0:0:0: Device offlined - not ready after error
recovery
Over the years, many different computers have backed up to this disk. Some
of those do not exist anymore (the usual story - old machine, cleaned up,
sold, bought a new machine). There is a lot of data on this disk. The
critical data has secondary backups, so I am not worried about that. But
there are a bunch of photographs from various hiking trips etc. that I
would like to recover from this hard disk if possible.
A colleague told me that if I can get the same chip as I currently have on
this hard disk, I can possibly recover my data. The assumption obviously is
that it is the chip that is dead, and not the actual magnetic disk.
|
Years ago we swapped the whole drive board in a hard disk and it did
subsequently work.
Try and get an identical disk from somewhere and swap..
If the drive motor has siezed up though (had that too) sometimes a drop
of oil on the bearings (not a good normal practice) will allow the thing
to spin up enough to get the data off.
Otherwise you need to invoke the expensive process of sending teh disk
away to somewone who can remount the pllatters and get the data off that
way. Dont expect that to be cheap, but companies do esxist that can.
| Quote: | Is this true, and if it is, how does one even do such a thing ? This
product has been discontinued, so my only hope appears to be to watch for
ebay auctions.
|
Yes, or ask here. Or on more localised groups.
Someone must have a identical working unit.
| Quote: | Is there an alternative way in which I can access this hard disk and mirror
off the data ? FWIW, I bought a new hard disk to replace this which is
ready to go.
|
No. Apatrt from contacting a good professional data recovery company and
paying serious money.
> Thanks. |
|
| |
|
| Back to top |
Rikishi42
Guest
|
| Posted: Sat Oct 11, 2008 4:03 am Post subject: Re: Fried hard disk chip - recovery strategies |
|
|
On 2008-10-10, TBerk <bayareaberk@yahoo.com> wrote:
| Quote: | Traditionally the DIY version was to obtain a same model HD and
carefully swap the whole electronics package over to the bad unit, just
long enough to transfer the data off.
|
Did that, works fine. But you_do_ need an exactly identical drive. Model and
revision.
--
Elevators smell different to midgets |
|
| |
|
| Back to top |
Allodoxaphobia
Guest
|
| Posted: Tue Oct 14, 2008 3:50 am Post subject: Re: mount: can't find /media/cdrom in /etc/fstab or /etc/mta |
|
|
On Mon, 13 Oct 2008 14:54:14 +0200, Frank Steinmetzger wrote:
| Quote: | Brian Fristensky schrob:
What does dmesg show when you insert the disk? Have you tried
different disks?
Nothing new appears in /var/log/dmesg when I insert any of a number of
CDs. In fact, the file was last written yesterday when I rebooted the
system.
AFAIK, dmesg only shows the log of the booting.
|
s/shows/shows some of/
Yesterday I saw a "/tmp too full" (or something to that effect) flash up
the screen on a boot.
Nothing showed via dmesg.
It was in /var/log/messages , tho'.
I've seen other instances like this.
Not everyone sits around and watches the boot messages flash by....
Jonesy
--
Marvin L Jones | jonz | W3DHJ | linux
38.24N 104.55W | @ config.com | Jonesy | OS/2
* Killfiling google & XXXXbanter.com: jonz.net/ng.htm |
|
| |
|
| Back to top |
Jerry Peters
Guest
|
| Posted: Wed Oct 15, 2008 1:38 am Post subject: Re: mount: can't find /media/cdrom in /etc/fstab or /etc/mta |
|
|
Allodoxaphobia <bit-bucket@config.com> wrote:
| Quote: | On Mon, 13 Oct 2008 14:54:14 +0200, Frank Steinmetzger wrote:
Brian Fristensky schrob:
What does dmesg show when you insert the disk? Have you tried
different disks?
Nothing new appears in /var/log/dmesg when I insert any of a number of
CDs. In fact, the file was last written yesterday when I rebooted the
system.
AFAIK, dmesg only shows the log of the booting.
s/shows/shows some of/
Yesterday I saw a "/tmp too full" (or something to that effect) flash up
the screen on a boot.
Nothing showed via dmesg.
It was in /var/log/messages , tho'.
I've seen other instances like this.
Not everyone sits around and watches the boot messages flash by....
Jonesy
|
Because dmesg shows the messages from the _kernel_ printk buffer. /tmp
too full message is not coming from the kernel. Try adding "quiet" as
a parameter on the kernel command line. It shuts up almost all of the
myriads of driver messages during boot. I get just over one screenful
of messages during boot, makes spotting errors/warnings much easier.
Jerry |
|
| |
|
| Back to top |
Theo Markettos
Guest
|
| Posted: Tue Oct 28, 2008 12:21 pm Post subject: Re: Fried hard disk chip - recovery strategies |
|
|
DanS <t.h.i.s.n.t.h.a.t@a.d.e.l.p.h.i.a.n.e.t> wrote:
| Quote: | Some info here. IIRC, the older/smaller the HD, the better chances of a
board swap working.
http://www.deadharddrive.com/
|
Some drives have a kamikaze function. If they detect something wrong (like
me having taken the lid off and poking around the board or head flexi with a
scope probe) they stop working and refuse to spin up the platters ever
again. So there's a chance that fiddling like this will make it worse. The
kamikaze bit is probably stored on the logic board, though, so a board swap
might still work.
(I'm pretty sure I didn't fry the drive, incidentally, as a high impedance
scope probe wouldn't do much more than load a particular signal. I
definitely didn't short anything)
As you say, older drives are more robust. I had an 80MB drive happily
booting Windows 3.1 with the lid off for several weeks.
Theo |
|
| |
|
| Back to top |
Peter Chant
Guest
|
| Posted: Fri Nov 07, 2008 2:21 am Post subject: Re: Fried hard disk chip - recovery strategies |
|
|
Theo Markettos wrote:
| Quote: | Some drives have a kamikaze function. If they detect something wrong
(like me having taken the lid off and poking around the board or head
flexi with a scope probe) they stop working and refuse to spin up the
platters ever
again. So there's a chance that fiddling like this will make it worse.
The kamikaze bit is probably stored on the logic board, though, so a board
swap might still work.
|
Have you got any links referencing that, I tried looking up "hard drive
kamilkaze" and "hard drive anti-tamper" on google and nothing showed up on
the first pages of either. I'm just curious.
I wonder why anyone would build such a feature in, or how? What purpose
would it serve? Only a tiny proportion of people would try this to recover
data. As a security feature I can't see what good it would do. The only
logical idea is that some how the manufacturers are in league with the data
recovery companies to prevent amateur attempts at recovery, I don't think
that is plausible as it would probally cause more trouble than it saved and
is dubious ethically.
Pete
--
http://www.petezilla.co.uk |
|
| |
|
| Back to top |
Charlie+
Guest
|
| Posted: Fri Nov 07, 2008 3:45 pm Post subject: Re: Fried hard disk chip - recovery strategies |
|
|
On Thu, 09 Oct 2008 12:07:42 -0700, Geico Caveman
<spammers-begone@spam.invalid> wrote as underneath my scribble :
| Quote: | Hello,
This is a Maxtor Diamondmax 16, 300GB ATA/133 HDD (3.5"). I bought it 3
years ago in a pre-integrated USB enclosure to serve as my backup disk. I
had an encrypted (luks) filesystem on the disk. A few weeks ago, the disk
stopped working. I tried using a different external HD enclosure. One of
the chips on the disk melted and smoked. I tried it again later with a
different enclosure, same story. Probably the original enclosure had some
kind of a safety interlock that tripped when the power characteristics of
the disk changed.
snip
A colleague told me that if I can get the same chip as I currently have on
this hard disk, I can possibly recover my data. The assumption obviously is
that it is the chip that is dead, and not the actual magnetic disk.
Is this true, and if it is, how does one even do such a thing ? This
product has been discontinued, so my only hope appears to be to watch for
ebay auctions.
Is there an alternative way in which I can access this hard disk and mirror
off the data ? FWIW, I bought a new hard disk to replace this which is
ready to go.
Thanks.
|
Others in the thread have suggested you swap the HD circuit board - this
worked for me perfectly - (Maxtor 80G HDs not identical and produced two
years apart but with same form factor but different revision circuit boards
and IDENTICAL board to hardware connectors! - However you dont seem sure
what is actually broken and there is a probability that there is a platter
drive motor cause, and if this is the case then the second circuit board
may fail too especially if the platter motor is short circuit. I took the
precaution of checking the platter motor drive resistances before trying
the board change and suggest you do the same.
If it is a problem with the platter drive motor itself then you have to use
a recovery service and it would IMHO probably be very expensive indeed
(?prohibitively?) for this type of fault!
Charlie+ |
|
| |
|
| Back to top |
Theo Markettos
Guest
|
| Posted: Sun Nov 09, 2008 5:20 pm Post subject: Re: Fried hard disk chip - recovery strategies |
|
|
Peter Chant <REMpeteOVE@cappetezilla.italsco.uk> wrote:
| Quote: | Some drives have a kamikaze function. If they detect something wrong
(like me having taken the lid off and poking around the board or head
flexi with a scope probe) they stop working and refuse to spin up the
platters ever again.
Have you got any links referencing that, I tried looking up "hard drive
kamilkaze" and "hard drive anti-tamper" on google and nothing showed up on
the first pages of either. I'm just curious.
|
It happened to me - I was poking around a drive head flexi with a scope
probe and all of a sudden the drive shut down. And no matter what I did it
would never spin up again. Up till then it would quite happily spin up with
the lid off. I'm quite sure I didn't short anything. Even if I did short a
signal, the most likely eventuality would be that it'd work again after
powercycling, but it never did. It never even tried to spinup, fail and
give up.
Similar sorts of things happen if I remove a platter... it might spin up
once to spot there's a missing platter, but doesn't a second time.
Even an early 1980s ST506 drive refused to spinup when there was a platter
missing. I can't remember exactly, but I don't /think/ the step servo
responded to ST506 step requests either. Which I was quite disappointed by,
as I'd hoped to use it as a stepper motor controller.
Of all the drives I tried (full height ST506 to modern-ish 4GB) I couldn't
make them spin up once I'd removed platters.
| Quote: | I wonder why anyone would build such a feature in, or how? What purpose
would it serve? Only a tiny proportion of people would try this to recover
data. As a security feature I can't see what good it would do. The only
logical idea is that some how the manufacturers are in league with the data
recovery companies to prevent amateur attempts at recovery, I don't think
that is plausible as it would probally cause more trouble than it saved and
is dubious ethically.
|
I think drives do have some kind of self-preservation mode. Notice how that
they're only accessible from the IDE bus if they spin up. Good drives spin
up, terminally bad drives don't. I've never had a situation where I've
attached a dead drive to an IDE cable and had 100% of sector read errors:
dead drives just don't show up in BIOS. Of course it /could/ be that these
are all logic board faults, but the ones I induced above weren't.
I don't mean drives with some bad sectors, those do show up and give sector
read errors.
I can't see a particular reason other than to emphasise the 'it's dead, buy
a new drive' whereas sector errors might not be spotted. Perhaps there's
some manufacturer-specific command to ignore the errors and try regardless,
but I don't have access to this documentation if it exists.
If there's something mechanically wrong inside there may be a wish to not
cause further damage: for risk of fire or not cause further damage to other
platters. If you're in a datacentre you just want a 'dead' indication
rather than an 'I'm struggling through but please put me out of my misery'.
For some reason retrieving customers' data doesn't seem to be that
important.
Theo
(University of Cambridge Computer Laboratory) |
|
| |
|
| Back to top |
Peter Chant
Guest
|
| Posted: Tue Nov 11, 2008 5:00 am Post subject: Re: Fried hard disk chip - recovery strategies |
|
|
Theo Markettos wrote:
| Quote: | It happened to me - I was poking around a drive head flexi with a scope
probe and all of a sudden the drive shut down. And no matter what I did
it
would never spin up again. Up till then it would quite happily spin up
with
the lid off. I'm quite sure I didn't short anything. Even if I did short
a signal, the most likely eventuality would be that it'd work again after
powercycling, but it never did. It never even tried to spinup, fail and
give up.
|
Static discharge frying something?
| Quote: |
Similar sorts of things happen if I remove a platter... it might spin up
once to spot there's a missing platter, but doesn't a second time.
|
That is strange.
| Quote: | Even an early 1980s ST506 drive refused to spinup when there was a platter
missing. I can't remember exactly, but I don't /think/ the step servo
responded to ST506 step requests either. Which I was quite disappointed
by, as I'd hoped to use it as a stepper motor controller.
Of all the drives I tried (full height ST506 to modern-ish 4GB) I couldn't
make them spin up once I'd removed platters.
|
I wonder, could the platters you removed act as part of the servo loop for
speed control. However, in that case did the drive ought not to run up to
maximum speed?
| Quote: | I wonder why anyone would build such a feature in, or how? What purpose
would it serve? Only a tiny proportion of people would try this to
recover
data. As a security feature I can't see what good it would do. The only
logical idea is that some how the manufacturers are in league with the
data recovery companies to prevent amateur attempts at recovery, I don't
think that is plausible as it would probally cause more trouble than it
saved and is dubious ethically.
I think drives do have some kind of self-preservation mode. Notice how
that
they're only accessible from the IDE bus if they spin up. Good drives
spin
up, terminally bad drives don't. I've never had a situation where I've
attached a dead drive to an IDE cable and had 100% of sector read errors:
dead drives just don't show up in BIOS. Of course it /could/ be that
these are all logic board faults, but the ones I induced above weren't.
|
Hmm, self preservation mode of committing hari kiri? Trouble is, without
disassembling its hard to tell why a drive has died. I've had drives die,
the just started getting errounous quickly then disappeared. I've had
others that just made that dead drive ticking noise, presumably the heads
hitting the end stops.
| Quote: | I don't mean drives with some bad sectors, those do show up and give
sector read errors.
I can't see a particular reason other than to emphasise the 'it's dead,
buy
a new drive' whereas sector errors might not be spotted. Perhaps there's
some manufacturer-specific command to ignore the errors and try
regardless, but I don't have access to this documentation if it exists.
|
I would have thought that that would have become common knowledge by now,
along with last ditch data recovery tools to get the data off a dying
drive.
| Quote: | If there's something mechanically wrong inside there may be a wish to not
cause further damage: for risk of fire or not cause further damage to
other
platters. If you're in a datacentre you just want a 'dead' indication
rather than an 'I'm struggling through but please put me out of my
misery'. For some reason retrieving customers' data doesn't seem to be
that important.
|
Not totally convinced you could put enough power into a stalled disk drive
motor to cause a fire risk. Have heard impressive grinding noises off of a
dying drive - for which a temporary fix (not mine) was to pick up the whole
PC and drop it about 6 inches back onto the desk. It worked, it would
then boot! BTW - no critical data and it would need a new drive anyway
when this failed as a plan.
| Quote: | Theo
(University of Cambridge Computer Laboratory)
|
--
http://www.petezilla.co.uk |
|
| |
|
| Back to top |
Theo Markettos
Guest
|
| Posted: Tue Nov 11, 2008 10:21 am Post subject: Re: Fried hard disk chip - recovery strategies |
|
|
Peter Chant <REMpeteOVE@cappetezilla.italsco.uk> wrote:
| Quote: | Theo Markettos wrote:
It happened to me - I was poking around a drive head flexi with a scope
probe and all of a sudden the drive shut down. And no matter what I did
it would never spin up again. Up till then it would quite happily spin
up with the lid off. I'm quite sure I didn't short anything. Even if I
did short a signal, the most likely eventuality would be that it'd work
again after powercycling, but it never did. It never even tried to
spinup, fail and give up.
Static discharge frying something?
|
It's possible, though I was at an antistatic workstation at the time (might
not have been wearing a wriststrap though).
| Quote: | I wonder, could the platters you removed act as part of the servo loop for
speed control. However, in that case did the drive ought not to run up to
maximum speed?
|
They're not used as servo loop for speed control, but all voice coil (ie not
stepper motor) drives put servo tracks on the platters for head positioning.
Earlier drives devote a platter to it, later drives either put servo tracks
or recover servo information from the data stream. It might be feasible for
the servo data to be read during spinup, but that would require some
variable filtering of the head signal and heads that will float
aerodynamically at low spin speeds.
As you say it would only make sense if the drive tried to spin up the drive
each time before giving up.
| Quote: | Hmm, self preservation mode of committing hari kiri? Trouble is, without
disassembling its hard to tell why a drive has died. I've had drives die,
the just started getting errounous quickly then disappeared. I've had
others that just made that dead drive ticking noise, presumably the heads
hitting the end stops.
|
Can you get SMART data out of these, and does it tell you anything about
what the drive thinks is wrong? I do have something of a problem of
interpreting SMART data as I never know what's normal and what's anomalous.
| Quote: | I would have thought that that would have become common knowledge by now,
along with last ditch data recovery tools to get the data off a dying
drive.
|
Indeed, unless it's under NDA and the tools that do it aren't widely
released (for someone to reverse engineer). I'd be surprised if drives
didn't have some degree of low level control available (ROM space and
preventing users from breaking their drives are the two reasons why not I can
think of).
I agree, this behaviour is odd.
I should add that I wasn't out to measure this effect - I wanted the heads
for something else and was trying to characterise the head preamplifier chip
(which usually have no data available), but in most cases I caused terminal
damage to the drive before I would have expected. So I wasn't keeping notes
of this behaviour but I did observe it and the above is my memory of it.
Theo |
|
| |
|
| Back to top |
Peter Chant
Guest
|
| Posted: Fri Nov 14, 2008 6:20 am Post subject: Re: Fried hard disk chip - recovery strategies |
|
|
Theo Markettos wrote:
| Quote: | Peter Chant <REMpeteOVE@cappetezilla.italsco.uk> wrote:
Theo Markettos wrote:
It happened to me - I was poking around a drive head flexi with a scope
probe and all of a sudden the drive shut down. And no matter what I
did
it would never spin up again. Up till then it would quite happily spin
up with the lid off. I'm quite sure I didn't short anything. Even if
I did short a signal, the most likely eventuality would be that it'd
work
again after powercycling, but it never did. It never even tried to
spinup, fail and give up.
Static discharge frying something?
It's possible, though I was at an antistatic workstation at the time
(might not have been wearing a wriststrap though).
I wonder, could the platters you removed act as part of the servo loop
for
speed control. However, in that case did the drive ought not to run up
to maximum speed?
They're not used as servo loop for speed control, but all voice coil (ie
not stepper motor) drives put servo tracks on the platters for head
positioning. Earlier drives devote a platter to it, later drives either
put servo tracks
or recover servo information from the data stream. It might be feasible
for the servo data to be read during spinup, but that would require some
variable filtering of the head signal and heads that will float
aerodynamically at low spin speeds.
As you say it would only make sense if the drive tried to spin up the
drive each time before giving up.
Hmm, self preservation mode of committing hari kiri? Trouble is, without
disassembling its hard to tell why a drive has died. I've had drives
die,
the just started getting errounous quickly then disappeared. I've had
others that just made that dead drive ticking noise, presumably the heads
hitting the end stops.
Can you get SMART data out of these, and does it tell you anything about
what the drive thinks is wrong? I do have something of a problem of
interpreting SMART data as I never know what's normal and what's
anomalous.
|
Sorry, only got two PC's here, and only the current disks are new enough for
SMART. Well I might have had one disk which gave enough warning to boot
_once_ and once only!
| Quote: | I would have thought that that would have become common knowledge by now,
along with last ditch data recovery tools to get the data off a dying
drive.
Indeed, unless it's under NDA and the tools that do it aren't widely
released (for someone to reverse engineer). I'd be surprised if drives
didn't have some degree of low level control available (ROM space and
preventing users from breaking their drives are the two reasons why not I
can think of).
I agree, this behaviour is odd.
|
What would surprise me is that I've been using PC's since the 8086, there
are a few hard drive manufacturers. That is rather a long time for similar
NDA's from several competing manufacturer's not to get leaked, especially
as a drive "kamikaze" mode would likely be contentious, and thousands of
people by now would be aware.
Also, the board swap scenario you discussed. If the kamikaze mode present
where would it reside? You'd need some way of finger-printing the platters
to the board. Otherwise when a board dies and you do a board swap how does
the old board know there is a problem? The platters will be fine, as far
as it is concerned nothing has changed unless it can remember its previous
state?
| Quote: | I should add that I wasn't out to measure this effect - I wanted the heads
for something else and was trying to characterise the head preamplifier
chip (which usually have no data available), but in most cases I caused
terminal
damage to the drive before I would have expected. So I wasn't keeping
notes of this behaviour but I did observe it and the above is my memory of
it.
|
Sounds odd as you say. If your probes were loading the amp (cable
capacitance?) and confusing the drive why did it not come back to life on
removal of the probes? Was the scope grounded? Earth loop between the
drives power supply and the scope? However, again on removal of probes
things should have been back to normal.
Pete
--
http://www.petezilla.co.uk |
|
| |
|
| Back to top |
Andrew Gideon
Guest
|
| Posted: Wed Dec 03, 2008 9:08 pm Post subject: Re: Upgrading laptop using external drive |
|
|
On Mon, 10 Nov 2008 19:29:16 +0000, Andrew Gideon wrote:
| Quote: | * Install a new distribution on the external drive
* Swap between booting from the internal drive and the
external drive while I'm switching between using my laptop
"normally" and installing the new distribution
* When I'm happy with the new distribution, install
the new drive into the laptop
and have the new distribution work in my laptop? I cannot see any
reason why this process wouldn't work for me, but I could easily be
missing something.
|
Just to complete this: I've finally swapped the external and internal
drives today. The laptop works flawlessly.
During the "install" process, I could easily boot from the internal drive
to restore my "working" environment. Then, hours or days later, I could
boot to the external drive to continue getting the new environment ready
to be productive.
And I suppose I could probably still boot from the previous (and now
external) drive if I needed to run my old environment. But I'm not
expecting that (though I might try it just to be sure I can {8^).
The one important thing to remember is to not use the same volume group
name on the internal and external drives. That would cause a conflict
and I'm not sure how (or even if) it could be resolved so as to have
access to both volume groups at the same time. And having that is very
convenient; it's much easier to copy from the old drive than to restore
from backup over the network.
- Andrew |
|
| |
|
| Back to top |
Kauko Klein
Guest
|
| Posted: Fri Dec 12, 2008 8:26 am Post subject: Ei rauhaa kannata puolustaa asein |
|
|
MTV uutiset 28.04-08. Jopas meinasin tuoliltani tippua, kun MTV kommentoi,
miten maailmaamme nyt raateleva nälänhätäkehitys on saamassa aiemmin täällä
vedätetyn eilisen riisilajipulan sijaan uutta megalomaniaansa. Eli nyt jo
alkaa kummasti irrota vihdoin viimein suorastaan pöyristyttävää faktaa, kun
on PAKKO. Sanottiin SUORAAN syyksi, ettei maailman poliitiset systeemit ole
huomioimneet maaseutua sikamaisesti lainkaan! Tämä on tietysti siltä osin
totta, että maaseudun poliittinen ja rikollinen terrorisointi on tuhonut
paljon. Eli politiikkaa nyt kaupataan selkeänä osasyynä maailmanlaajuiseen
tulevaan ruokakatastrofiin. Kas kun kukaan ei riisirehuja eläimille anna,
eikä myös Suomi ole poltellut ruokiaan bienergiaksi, kuten tähän asti on
aina valehdeltu. Edes etanoliriisejä ei ole tehty!
Mutta raakaan faktaan, maailmalla on jo kuulema 37 maata nälkäkatastrofissa
nyt! Vaikka vasta eilen oli USA:ssa vain "mitätön" väliaikainen säännöstelyn
hupailu. Päivän päästä maailmassa on 37 maata nälkämellakoissa. Lieneekö
siis takana maailman rajuin nälän yö.. ? Vai onko nämä mun esillä pitämät
salatut maailmanlaajuiset nälkäkatastrofit tieten pidetty ydintyyliimme
Suomen tiedotusmonopolien poliittisesta syystä tarkoin piilossa! jottei vaan
maalaisten ahdinkoon tarvitsisi myös TEHDÄ jotain! .. Siis AIVAN VARMASTI!
Mutta yhä mua hämmästyttää miksi edelleen vaietaan siitä miksi meremme
tyhjenee elämästä, mehiläiset katoaa, lentokoneet putoilee kuin viimeistä
päivää oranssiauringonlaskuionisaatiopilviin, ja miksei pelloillemme, edes
janoomme enää riitä edes vettä?! Aivan oikein ydinhallintomme on
jääräpäisesti päättänyt EDELLEEN vaieta synnyttämästään maapallomme
tulevaisuuden jo nyt vaakalaudalle saattaneesta beettasoihtuamisten
ydinaavikoitumistuhosta! Mutta kuten huomaamme PAKON edessä tämä maalaisten
härski ja sikailukulttuurinen kohtelu joudutaan tuomaan julki. Vielä tulee
muuten eteen myös se päivä jolloin näille kaikelle on myös TEHTÄVÄ jotain!
Ja yhtä varmaa on myös se, että ydinalan on myös aika myöntää itsensä
syylliseksi supersalattuun ydinmaavikoitumistuhoaaltoon joka jo lupaavasti
orastaa. Edessä siis jänniä vuosia! |
|
| |
|
| Back to top |
propman
Guest
|
| Posted: Sun Dec 28, 2008 2:41 pm Post subject: Re: My hard drive is clicking |
|
|
annalissa wrote:
| Quote: | Hi all,
I attached a new samsung 250 GB disk, but whenever the computer stops
there is a clicking sound, i googled for this problem and found the
solution here
http://eric.biven.us/2008/10/09/my-hard-drive-is-clicking-again-so-im-stopping-it-cold-when-ubuntu-boots/
I tried what is said in this howto and found that my clicking sound
has
now reduced to a very small noise, now what i want is to eliminate
this sound completely, so how to do it ?
what is the method/means to know if hardware doesn't support 255
option ?
How to find out the optimal apm value for a particular hard disk ?
NB: I use ubuntu 8.04.1
|
Might want to check the following site to see if the information you are
interested in is available:
http://www.samsung.com/global/business/hdd/ |
|
| |
|
| Back to top |
|
