Re: Problem with Compaq SMART-2SL array controller
I'm trying to install 4.0-RELEASE on a COMPAQ Proliant 1850R with the root disk on a SMART-2SL raid controller. The install works perfectly, but boot/loader fails to load the kernel. Booting "kernel" fails with 'Don't know how to load module "/kernel"', and boot kernel.GENERIC fails for unknown reasons. (It loads partly, but then falls back to the loader). If it "falls back" you should get an error message. Is there an easy way to get this to work, or do I need to start thinking about adding a seperate root disk? Looks like you have data corruption problems here; it's possible that your array wasn't correctly built, or is malfunctioning. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with Compaq SMART-2SL array controller
Jonathan Lemon wrote: For now, you could remove the IDE devices from the config file, until this gets fixed. Ideally, the boot blocks/loader should be taught to boot from something other than wd() or da(). Alas, the loader uses BIOS to read the disk. Anything the BIOS can read, so can the loader. The way it _passes_ the information, though, is limited by the kernel. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "Thus, over the years my wife and I have physically diverged. While I have zoomed toward a crusty middle-age, she has instead clung doggedly to the sweet bloom of youth. Naturally I think this unfair. Yet, if it was the other way around, I confess I wouldn't be happy either." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with Compaq SMART-2SL array controller
After doing a cvsup yesterday evening i can't seem to boot on my raid cotroller using the same kernel config. Is -current probing hardware i a different way now or ?? This is a consequence of a defect in the way that the ida driver works, and new code which resorts the disk drivers (so that the 'wd' driver throws out the 'ida' driver). The correct fix for this is nontrivial and a little while off; you might want to go back to your old kernel for a while if the issue hasn't already been resolved. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with Compaq SMART-2SL array controller
I don't know who is maintaining the id driver, but it looks to me like it isn't able to co-exist with the wd driver (because it "steals" the wd drivers cdevsw entry) Poul-Henning In message [EMAIL PROTECTED], [EMAIL PROTECTED] w rites: After doing a cvsup yesterday evening i can't seem to boot on my raid cotroller using the same kernel config. Is -current probing hardware i a different way now or ?? Is there anyone with an answer to this ?? Kernel Config: #Compaq SMART Array 2-SL Controller controller ida0 device id0 controller wdc0at isa? port IO_WD1 irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1at isa? port IO_WD2 irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 device wcd0#IDE CD-ROM The bootmessage that i got when it was Working : ida0: Compaq SMART-2SL array controller irq 18 at device 0.0 on pci2 ida0: drives=1 firm_rev=3.08 WARNING: "id" is usurping "id"'s cdevsw[] WARNING: "id" is usurping "id"'s bmaj WARNING: "id" is usurping "wd"'s cdevsw[] WARNING: "id" is usurping "id"'s bmaj id0: Compaq Logical Drive on ida0 id0: 17355MB (35544960 sectors), blocksize=512 ~ wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (atapi): CD-ROM 36X/AKW/U22, removable, intr, dma, iordis ~ changing root device to id0s2a The bootmessage that i have now : "Not Working" ida0: Compaq SMART-2SL array controller irq 18 at device 0.0 on pci2 ida0: drives=1 firm_rev=3.08 WARNING: "id" is usurping "id"'s cdevsw[] WARNING: "id" is usurping "id"'s bmaj id0: Compaq Logical Drive on ida0 id0: 17355MB (35544960 sectors), blocksize=512 ~ wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 ~ WARNING: "wd" is usurping "id"'s cdevsw[] WARNING: "wd" is usurping "wd"'s bmaj ~ wdc0: unit 0 (atapi): CD-ROM 36X/AKW/U22, removable, intr, dma, iordis ~ ~ changing root device to wd0s2a changing root device to wd0a rootdev=0xC1499000 error=6 panic cannot mount rootdev To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with Compaq SMART-2SL array controller
In article local.mail.freebsd-current/[EMAIL PROTECTED] you write: After doing a cvsup yesterday evening i can't seem to boot on my raid cotroller using the same kernel config. Is -current probing hardware i a different way now or ?? It appears so. The IDA driver needs to stomp on the WD driver's vectors in order to boot off of the RAID controller. It seems that something changed so that wd is getting probed after the ida driver now, and removing the vectors. For now, you could remove the IDE devices from the config file, until this gets fixed. Ideally, the boot blocks/loader should be taught to boot from something other than wd() or da(). -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with Compaq SMART-2SL array controller
In message [EMAIL PROTECTED] Jonathan Lemon writes: : It appears so. The IDA driver needs to stomp on the WD driver's : vectors in order to boot off of the RAID controller. It seems that : something changed so that wd is getting probed after the ida driver : now, and removing the vectors. Is this so that it could mount root? In 3.x the only way to do this is to have a special disk label type. I've hacked things to get fla bootable on -stable using this method. The sysinstall program hasn't been updated, however. : For now, you could remove the IDE devices from the config file, : until this gets fixed. Ideally, the boot blocks/loader should be : taught to boot from something other than wd() or da(). phk's fla driver mount / correctly when it is the boot device. However, the boot loader does have some interesting limitations in this area last time I checked. Likely it was due to using the -stable version for most of my testing. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with Compaq SMART-2SL array controller
On Sep 09, 1999 at 01:26:35PM -0600, Warner Losh wrote: In message [EMAIL PROTECTED] Jonathan Lemon writes: : It appears so. The IDA driver needs to stomp on the WD driver's : vectors in order to boot off of the RAID controller. It seems that : something changed so that wd is getting probed after the ida driver : now, and removing the vectors. Is this so that it could mount root? In 3.x the only way to do this is to have a special disk label type. I've hacked things to get fla bootable on -stable using this method. The sysinstall program hasn't been updated, however. Yes. The IDA driver will be happy with it's own device nodes (/dev/ida), but last time I checked, the boot/loader would only understand root devices of wd() or da(). I understand that Soren's ad() driver has the same problem. -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with Compaq SMART-2SL array controller
In message [EMAIL PROTECTED] Jonathan Lemon writes: : Yes. The IDA driver will be happy with it's own device nodes : (/dev/ida), but last time I checked, the boot/loader would : only understand root devices of wd() or da(). I understand that : Soren's ad() driver has the same problem. That's not entirely true. I've hacked the 3.x boot loader to grok fla devices on boot. In 4.x I didn't need to hack anything. It just worked, but I might have had to specify the BIOS device number hwen booting... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with Compaq SMART-2SL array controller
In message [EMAIL PROTECTED], Warner Losh writes: phk's fla driver mount / correctly when it is the boot device. However, the boot loader does have some interesting limitations in this area last time I checked. Likely it was due to using the -stable version for most of my testing. I actually have a design and most of an implementation for a better handling of root device/method selection, the boot blocks already pass a environment string in with the name (at least in current). -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
