Date: Tue, 9 Sep 2003 16:04:21 +0100 From: Nick Jones <nick@freebsd.cx> To: freebsd-sparc64@freebsd.org Subject: Dedicated disks from a sparc64/-CURRENT system into an Alpha Message-ID: <20030909150421.GC7145@freebsd.cx>
next in thread | raw e-mail | index | archive | help
Sorry to cross post this, but a suggestion mailed to me off-list regarding the problem below suggested that maybe it's endian related. As I need to get these disks working in either an Alpha box or an x86 box and sparc64 being the 'odd-one-out' (big endian), maybe someone on this list can shed some light. > To: freebsd-alpha@freebsd.org > > I'm trying to install two IDE disks that were created in dedicated mode on a > Sun Ultra5 running -CURRENT (from about a month ago) into a Compaq > Professional Workstation XPS1000 running 5.1-RELEASE. The disks are attached > to a Promise ATA100 PCI IDE Controller, and both devices are detected on boot > as follows: > > ad0: 58644MB <IC35L060AVER07-0> [119150/16/63] at ata2-master UDMA100 > ad1: 114473MB <WDC WD1200JB-00DUA0> [232581/16/63] at ata2-slave UDMA100 > > The corresponding entries in fstab taken from the sparc64 installation are: > > /dev/ad1f /data1 ufs rw 2 2 > /dev/ad0d /data2 ufs rw 2 2 > > However, neither 'ad0d' or 'ad1f' exist on the Alpha, and bsdlabel simply > returns: > > willow# bsdlabel /dev/ad0 > bsdlabel: /dev/ad0: no valid label found > > If I put the drives back into the sparc64 box all is well, so it's not > something that's happened physically to the drives during removal and > reinstallation. > > Any ideas? This is actually the first time I've really messed with 5.x and > devfs in particular so it might be something obvious I'm neglecting to do, but > I can't see it. > > TIA. -- /Nick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030909150421.GC7145>