Dear All,
We have a Dell Powervault 745N and want to install FreeBSD 6.1-R.
But the installer complains that it can not find out any hard disk.
Since the dmesg contains ata2~5, I think the controller is recognized
by FreeBSD, but it cannot get the SATA drive.
The dmesg and result of running pciconf -lv is in this PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/103624
Any suggestions?
With Best Regards,
Eric
On Wed, Oct 18, 2006 at 10:46:21PM +0800, Lin Jui-Nan Eric wrote:> We have a Dell Powervault 745N and want to install FreeBSD 6.1-R. > But the installer complains that it can not find out any hard disk. > Since the dmesg contains ata2~5, I think the controller is recognized > by FreeBSD, but it cannot get the SATA drive. > > The dmesg and result of running pciconf -lv is in this PR: > http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/103624The controller (which you label in your PR as "some funny RAID controller") is an Intel 31244: atapci0: <Intel 31244 SATA150 controller> mem 0xfe1ff000-0xfe1fffff irq 25 at device 2.0 on pci2 ata2: <ATA channel 0> on atapci0 ata3: <ATA channel 1> on atapci0 ata4: <ATA channel 2> on atapci0 ata5: <ATA channel 3> on atapci0 Some history: this controller was discussed back in 2005: http://lists.freebsd.org/pipermail/freebsd-current/2005-June/050827.html The appropriate code appears to have been committed to FreeBSD as of June 2005: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/ata-pci.h#rev1.49 There was a DMA-related fix for this controller committed in February 2006: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/ata-pci.h#rev1.49.2.7 Soren, do you have any ideas? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Jeremy Chadwick wrote:> On Wed, Oct 18, 2006 at 10:46:21PM +0800, Lin Jui-Nan Eric wrote: > >> We have a Dell Powervault 745N and want to install FreeBSD 6.1-R. >> But the installer complains that it can not find out any hard disk. >> Since the dmesg contains ata2~5, I think the controller is recognized >> by FreeBSD, but it cannot get the SATA drive. >> >> The dmesg and result of running pciconf -lv is in this PR: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/103624 >> > > The controller (which you label in your PR as "some funny RAID > controller") is an Intel 31244: > > atapci0: <Intel 31244 SATA150 controller> mem 0xfe1ff000-0xfe1fffff irq 25 at device 2.0 on pci2 > ata2: <ATA channel 0> on atapci0 > ata3: <ATA channel 1> on atapci0 > ata4: <ATA channel 2> on atapci0 > ata5: <ATA channel 3> on atapci0 > > Some history: this controller was discussed back in 2005: > > http://lists.freebsd.org/pipermail/freebsd-current/2005-June/050827.html > > The appropriate code appears to have been committed to FreeBSD as > of June 2005: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/ata-pci.h#rev1.49 > > There was a DMA-related fix for this controller committed in February 2006: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/ata-pci.h#rev1.49.2.7 > > Soren, do you have any ideas? >Nothing else that that it should work. I dont own any HW that uses this chip so I cannot test it out. The current support was done for the ARM port IIRC so things might be different on other systems. At any rate you definitly should try out 6.2-beta-something as 6.1 is getting old.... -S?ren
Hi, On 10/19/06, S?ren Schmidt <sos@deepcore.dk> wrote:> Nothing else that that it should work. I dont own any HW that uses this > chip so I cannot test it out. The current support was done for the ARM > port IIRC so things might be different on other systems. > At any rate you definitly should try out 6.2-beta-something as 6.1 is > getting old....I have tried world & kernel built yesterday (10/19), but the OS still can not recognize the hard disk. The dmesg and result of pciconf -lv: http://www.cs.nctu.edu.tw/~jnlin/cc/dmesg.log http://www.cs.nctu.edu.tw/~jnlin/cc/pciconf.log Best Regards, Jui-Nan
Lin Jui-Nan Eric wrote:> Hi, > > On 10/19/06, S?ren Schmidt <sos@deepcore.dk> wrote: >> Nothing else that that it should work. I dont own any HW that uses this >> chip so I cannot test it out. The current support was done for the ARM >> port IIRC so things might be different on other systems. >> At any rate you definitly should try out 6.2-beta-something as 6.1 is >> getting old.... > I have tried world & kernel built yesterday (10/19), but the OS still > can not recognize the hard disk. > > The dmesg and result of pciconf -lv: > > http://www.cs.nctu.edu.tw/~jnlin/cc/dmesg.log > http://www.cs.nctu.edu.tw/~jnlin/cc/pciconf.log >OK, I need the output from a verbose boot. That will tell if the disks are seen at all and just the attach phase is failing. I might have a few ideas depending on the outcome of that... -S?ren
Hi, On 10/20/06, S?ren Schmidt <sos@deepcore.dk> wrote:> OK, I need the output from a verbose boot. That will tell if the disks > are seen at all and just the attach phase is failing. > I might have a few ideas depending on the outcome of that...There is no message about ad0 shown in the boot procedure. Neither there is no message about failed device. How do I get the output from verbose boot? with digital camera? Best Regards, Eric
Dear, On 10/20/06, S?ren Schmidt <sos@deepcore.dk> wrote:> Boot verbose and grap the output like you did earlier in this thread > will do nicely. What I need are the lines from where the channels on the > controller are probed for raw devices, that should reveal if we can se > any HW at all.. >The verbose boot output is in http://www.csie.nctu.edu.tw/~jnlin/dmesg.v.log With Best Regards, Eric