[dropping the X bug for this...] On Tue, Aug 24, 2004 at 11:09:50PM +0900, Atsuhito Kohda wrote: > I tested the current 2.4.27 kernel-image and, yes, it worked > much better than older 2.4.x kernels but not yet worked > completely well. > It booted successfully (in a sense) but I needed to press > Control-D at some instance because fsck(?) failed to open > non-root (/home) partition (I defined /dev/sda1 as / and > /dev/sdb1 as /home). > And after boot, I tried to mount /home manually but failed > with the message; > mount: /dev/sdb1 is not a valid block device > I suspected some modules might be missing (or so) but not > sure yet. > lsmod shows; > autofs4 13248 2 (autoclean) > usbcore 87912 1 > tulip 60392 1 > crc32 3488 0 [tulip] > rtc 8288 0 (autoclean) > ext3 108072 0 (autoclean) > jbd 64376 0 (autoclean) [ext3] > sd_mod 17064 4 (autoclean) > sym53c8xx 88336 2 (autoclean) > scsi_mod 119796 2 (autoclean) [sd_mod sym53c8xx] > unix 23224 44 (autoclean) Is /dev/sdb on the same SCSI bus as /dev/sda? If so, you may want to open a bug report against the kernel. What does cat /proc/scsi/scsi show you? Since sarge will not include support for 2.2 kernels when it's released, I think figuring out this problem will be worth your effort. Cheers, -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature