public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Beolach <beolach@comcast.net>
To: jtwilliams@vt.edu
Cc: linux-newbie@vger.kernel.org
Subject: Re: Damn unmouted root
Date: Fri, 25 Jun 2004 06:43:10 -0600	[thread overview]
Message-ID: <40DC1DDE.6000607@comcast.net> (raw)
In-Reply-To: <1088132157.21223.11.camel@localhost>

I've never myself done anything w/ SCSI drives (other than ide-scsi
emulation for CD-Writing pre kernel 2.6), but I thought SCSI harddrives
were usually /dev/sd?, while IDE drives were /dev/hd?.

From /usr/src/linux-2.6.7/Documentation/devices.txt:

  8 block       SCSI disk devices (0-15)
                  0 = /dev/sda          First SCSI disk whole disk
                 16 = /dev/sdb          Second SCSI disk whole disk
                 32 = /dev/sdc          Third SCSI disk whole disk
                    ...
                240 = /dev/sdp          Sixteenth SCSI disk whole disk

                Partitions are handled in the same way as for IDE
                disks (see major number 3) except that the limit on
                partitions is 15.

Good luck,
Conway S. Smith


John T. Williams wrote:
> I've been having the hardest time getting a kernel I've compiled to
> work.  I've compiled kernels at least a dozen times and this is the
> first one that has given me any real trouble.  I think the issue might
> be the scsi hard-drive.  
> 
> I've compiled in scsi support ( actually in, not as module ), but every
> time I try to boot the kernel, i get the error 
> 
> VFS unable to mount root fs on /dev/hdf1
> 
> and a kernel panic.  
> 
> the kernel uses devfs and I'm passing the kernel 
> 
> root=/dev/hdf1 devfs=mount 
> 
> as I said, I'm pretty sure its the scsi harddrive that is giving me
> problems as its the only thing in this situation that I've never had to
> deal with before, but even with that insight I haven't been able to
> figure out how to get the kernel.
> 
> Thanks,
> John 
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  parent reply	other threads:[~2004-06-25 12:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-25  2:55 Damn unmouted root John T. Williams
2004-06-25  3:32 ` Ken
2004-06-25 12:43 ` Beolach [this message]
2004-06-25 14:09 ` Ray Olszewski

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=40DC1DDE.6000607@comcast.net \
    --to=beolach@comcast.net \
    --cc=jtwilliams@vt.edu \
    --cc=linux-newbie@vger.kernel.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