partitioning program does not see scsi disk

Anton Shterenlikht <[email protected]>
Newsgroups gmane.os.freebsd.devel.alpha
Message-ID <[email protected]>
HI

I'm trying to install
FreeBSD 6.2-RELEASE #0: Sat Jan 13 02:32:39 UTC 2007
on
AlphaServer DS10L 466 MHz Console V7.3-1, Feb 27 2007 13:17:58

I cannot see the SCSI disk in the partitioning program.

The disk worked fine under VMS 8.3.

I can see the disk in SRM:

>>>show dev
dka0.0.0.17.0              DKA0       QUANTUM ATLAS10K3_18_WLS  020K
dqb0.0.1.13.0              DQB0                        CD-224E  9.5B    
dva0.0.0.0.0               DVA0                               
ewa0.0.0.9.0               EWA0              08-00-2B-87-42-31
ewb0.0.0.11.0              EWB0              08-00-2B-87-42-4E
pka0.7.0.17.0              PKA0                  SCSI Bus ID 7
>>>


and the SCSI controller is the standard NCR 53C895:


>>>init
Initializing...
*** keyboard not plugged in...
1024 Meg of system memory
probing hose 0, PCI
probing PCI-to-ISA bridge, bus 1
bus 0, slot 9 -- ewa -- DE500-BA Network Controller
bus 0, slot 11 -- ewb -- DE500-BA Network Controller
bus 0, slot 13 -- dqa -- Acer Labs M1543C IDE
bus 0, slot 13 -- dqb -- Acer Labs M1543C IDE
bus 0, slot 17 -- pka -- NCR 53C895
initializing GCT/FRU at 3ff40000
Testing the System
Testing the Disks (read only)
Testing ew* devices.
System Temperature is 43 degrees C

AlphaServer DS10L 466 MHz Console V7.3-1, Feb 27 2007 13:17:58
>>>


so it should be supported by the ncr(4) driver. I could not see this
driver in modules or in kernel (why? should it appear somewhere?)
so I further loaded sym(4) module before booting:


Loading /boot/defaults/loader.conf 
/boot/kernel/kernel data=0x6fed50+0x39a70 syms=[0x8+0x76578+0x8+0x61c05]
-
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel] in 9 seconds... 

Type '?' for a list of commands, 'help' for more detailed help.
OK load sym
/boot/kernel/sym.ko text=0x10048 data=0x32ae+0xa syms=[0x8+0x12f0+0x8+0xb40]
OK lsmod
 0xfffffc0000300000: /boot/kernel/kernel (elf kernel, 0x810950)
  modules: splash.1 ufs.1 nfsserver.1 nfslock.1 nfs.1 nfs4.1 wlan.1 wlan_wep.1 wlan_tkip.1 wlan_ccmp.1 if_gif.1 if_faith.1 ether.1 sysvshm.1 sysvsem.1 sysvmsg.1 cd9660.1 isa.1 pseudofs.1 procfs.1 msdosfs.1 usb.1 cdce.0 random.1 ppbus.1 pci.1 null.1 mpt_raid.1 mpt.1 mpt_cam.1 mpt_core.1 miibus.1 mem.1 ispfw.0 isp.1 sbp.1 fwe.1 firewire.1 if_ath.1 ath_rate.1 ath_hal.1 ast.1 afd.1 acd.1 atapci.1 ad.1 ata.1 ahc.1 ahc_pci.1 ahc_isa.1 ahc_eisa.1 cam.1 
 0xfffffc0000b10950: /boot/mfsroot (mfs_root, 0x438000)
 0xfffffc0000f4a000: /boot/kernel/sym.ko (elf module, 0x25140)
  modules: sym.1 
OK 


and I can see the disk detected correctly by sym during boot:

[...]
da0 at sym0 bus 0 target 0 lun 0
da0: <QUANTUM ATLAS10K3_18_WLS 020K> Fixed Direct Access SCSI-3 device 
da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled
da0: 17537MB (35916548 512 byte sectors: 255H 63S/T 2235C)
[...]


but after that I cannot see the disk (this is a screen copy):

                         FreeBSD Disklabel Editor


Part      Mount          Size Newfs   Part      Mount          Size Newfs
----      -----          ---- -----   ----      -----          ---- -----








                                                                           



The following commands are valid here (upper or lower case):
C = Create        D = Delete   M = Mount pt.
N = Newfs Opts    Q = Finish   S = Toggle SoftUpdates   Z = Custom Newfs
T = Toggle Newfs  U = Undo     A = Auto Defaults        R = Delete+Merge

Use F1 or ? to get more help, arrow keys to select.


furthermore if I press some keys, like Z, or R, I get signal 11:

 
	+--------------------------- Message ---------------------------+
	|A signal 11 was caught - I'm saving what I can and shutting    |  
	|down.  If you can reproduce the problem, please turn Debug on  |  
	|in the Options menu for the extra information it provides      |  
	|in debugging problems like this.                               |  
	+-------------------------------------------------------(100%)--+  
	|                         [  OK  ]                              |  
	+-------------------[ Press enter or space ]--------------------


I've only found one related thread on the net:
http://lists.freebsd.org/pipermail/freebsd-alpha/2003-April/000162.html

in which the author had what seems like a similar problem and he
resolved it by:

	Fixed my own problem really.  Turns out that neither disk had an 
	acceptable first block for FreeBSD.  Running a "dd if=/dev/null 
	of=/dev/da1 bk=0 s=1" (or whatever the correct syntax is, I forget) to 
	zero out the first block made the disk appear in the 5.0 disklabel 
	program.

Now, how do I do that? Do I actually need to remove the disk from alpha
and put in some other unix box?

I tried to write NIL to the first block using SRM exer as follows:

>>>init
>>>chmod +w dka*
>>>exer -d1 0 -sb 0 -eb 1 -a 'w-Rc' dka0

but nothing changed.

There is nothing on this problem in the release notes:
http://www.freebsd.org/releases/6.2R/hardware-alpha.html

except:

	The kernel config file must contain:

	options    DEC_ST6600    
	cpu EV5

I'm not sure how to do this before boot.

Any ideas?

thanks a lot
anton


-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 928 8233 
Fax: +44 (0)117 929 4423
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-alpha
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.