From: Grant Grundler <grundler@puffin.external.hp.com>
To: "Pedot, Wolfgang" <wpedot@harris.com>
Cc: "'Parisc Linux Mailinglist'" <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] HD not bootable after installation....
Date: Fri, 13 Jul 2001 22:48:28 -0600 [thread overview]
Message-ID: <200107140448.WAA28246@puffin.external.hp.com> (raw)
In-Reply-To: Message from "Pedot, Wolfgang" <wpedot@harris.com> of "Fri, 13 Jul 2001 06:14:02 EDT." <8D4C69676E66D511A1CB00508BBBB19216268C@ranmx1.ran.harris.com>
"Pedot, Wolfgang" wrote:
...
> After installing an other Harddisk the installation
> went fine but for some reason this new Harddisk is not bootable
> (Palo was executed successfully), its not in the list of bootable
> devices at startup and if i select it manualy it fails to boot.
> But after booting from network the disk is detected. Since this harddisk
> was in a PC before I wonder if theres anything
> I may have forgotten...
Perhaps. To add/remove jumpers on the HD to enable "Auto-Spinup"?
You need a spec sheet for the HD to figure out which jumpers those are.
If you only have 1 or 2 HDs, it's better to disable "Spinup Delay".
PC BIOS (or scsi controller Expansion ROM) and Linux SCSI drivers
are smart enough to send a "Start Unit" cmd to spin up the disk.
PDC on most (all?) parisc workstations is not. I don't think the
servers are any smarter but don't know for sure.
grant
Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253
next prev parent reply other threads:[~2001-07-14 4:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 10:14 [parisc-linux] HD not bootable after installation Pedot, Wolfgang
2001-07-14 4:48 ` Grant Grundler [this message]
[not found] <8D4C69676E66D511A1CB00508BBBB192162690@ranmx1.ran.harris.com>
2001-07-16 13:49 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2001-07-16 15:11 Pedot, Wolfgang
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=200107140448.WAA28246@puffin.external.hp.com \
--to=grundler@puffin.external.hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=wpedot@harris.com \
/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