From: "\"Beerse, Corné\"" <c.beerse@torex-hiscom.nl>
To: "'James Smith'" <james@compusmithllc.com>,
parisc-linux@lists.parisc-linux.org
Subject: RE: [parisc-linux] Disk problems
Date: Mon, 25 Nov 2002 11:24:34 +0100 [thread overview]
Message-ID: <02Nov25.113607cet.119049@ns.hiscom.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1997 bytes --]
> -----Original Message-----
> From: James Smith [mailto:james@compusmithllc.com]
> I just got a pile of 712/60's - $80 for 10 of em :)
I got mine (1 and a half) for free ;-)
> i've set one up & now i'm going through the disks one at a time &
> cloning them as its quicker than going through the install each time
> i've hit one disk that gives me this whenever i try to fdisk it
>
> sixty:~# fdisk /dev/sdb
>
> Unable to read /dev/sdb
>
>
> when i tried to zero the disk, i got this....
>
> sixty:~# dd if=/dev/zero of=/dev/sdb count=1 bs=512
> dd: writing `/dev/sdb': Input/output error
> 1+0 records in
> 0+0 records out
So you cannot read and cannot write to it.
>
> the console sees the disk when i use search
>
> does this indicate a dead disk?
>
> the disk was ok until i put it into a mac......
What where the results on the mac? Can you clone the disks using a mac? If
so, what are the results?
My experience: the 712 I have at home was my workhorse for over 5 years. It
never failed on me. Occasional reboots for obvious reasons never had any
problems. However, after being down for a couple of weeks, the harddisk does
not spin properly. It was reported with several of those older systems. The
ioscan and other tools that only access the firmware of the drive report no
problems. Actual access of the disk is a problem since (in my case) the disk
does not spin at all.
If you can access the data storage using your mac, you might have success
after warming the device. I know the powersupply in the 712 series is
limited and might not provide enough power to start a cold disk. You might
be able to clone disks using your mac.
In an disk array, I have a couple of disks that are all the same specs.
However, due to a hardware defect in one of them, a (HP-UX) `ioscan` reports
0 bytes for that disk where others report their actual value. If you hook
the disk to an HP-UX machine, what does `ioscan` report?
Sorry to say but I think your disk is dead
Success
CBee
[-- Attachment #2: Type: text/html, Size: 3313 bytes --]
next reply other threads:[~2002-11-25 10:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 10:24 "Beerse, Corné" [this message]
2002-11-25 14:47 ` [parisc-linux] Disk problems Derek Engelhaupt
[not found] <3DA3C54C00007733@ocpmta5.be.tiscali.com>
2002-11-27 16:38 ` James Smith
2002-11-27 16:44 ` John David Anglin
2002-11-27 17:06 ` jsoe0708
2002-11-27 22:20 ` James Smith
2002-12-03 5:01 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2002-11-26 17:00 Yves Bodack
2002-11-26 20:31 ` James Smith
2002-11-26 20:42 ` John David Anglin
2002-11-22 21:29 James Smith
2002-11-23 1:52 ` Derek Engelhaupt
2002-11-25 17:13 ` James Smith
2002-11-25 17:46 ` jsoe0708
2002-11-25 18:02 ` Grant Grundler
2002-11-25 17:51 ` John David Anglin
2002-11-25 20:12 ` Derek Engelhaupt
2002-11-25 21:07 ` Grant Grundler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02Nov25.113607cet.119049@ns.hiscom.nl \
--to=c.beerse@torex-hiscom.nl \
--cc=james@compusmithllc.com \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox