All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Steffl <steffl@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: udev and /dev/sda1 not found during boot (it's there right after boot)
Date: Sat, 24 Apr 2004 00:37:41 -0700	[thread overview]
Message-ID: <408A1945.1030506@bigfoot.com> (raw)

   just moved to udev and everything seems to be working OK except of 
SATA drive (visible as /dev/sda1) when fsck checks it during boot (it 
works fine right after that).

   all the required modules (as far as I can tell) are in /etc/modules. 
I  see the modules loading and right after the modules are loaded fsck 
starts. It checks /dev/hdb6 (root) and it goes on to check /dev/sda1 and 
complains that there is no such file. At that point I get a choice to 
enter root password for maintenance or ctrl-d to continue booting.

   enter root password: I get command prompt, check the /dev/sda1, it's 
there, I can do fsck or mount it

   ctrl-d: boot continues as usual, /dev/sda1 is mounted

   any ideas how to fix this? is it a timing issue (udev didn't create 
device yet but fsck is already trying to use it)?

   system:

   debian unstable
   kernel 2.6.5
   udev 0.024

/etc/modules:
ip_tables
# -------------- scsi
sd_mod
sr_mod
ide-scsi
sg
scsi_transport_spi
# -------------- cdrom
ide-cd
# -------------- alsa
snd_emu10k1

   TIA

	erik

             reply	other threads:[~2004-04-24  7:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-24  7:37 Erik Steffl [this message]
2004-04-24 15:55 ` udev and /dev/sda1 not found during boot (it's there right after boot) Greg KH
2004-04-24 20:32   ` Marco d'Itri
2004-05-23 15:56   ` Erik Steffl
2004-05-23 16:25     ` Greg KH
2004-05-24  3:29       ` Erik Steffl
2004-05-24  4:58         ` Greg KH

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=408A1945.1030506@bigfoot.com \
    --to=steffl@bigfoot.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.