IBM

Nabbed an RS/6000 7043/43p, figuring out what to do with it

pentium wrote:
Is this REALLY only compatible with OS/400 and Z? Nothing from AIX? Not even from Linux?


I'd be very surprised if it works with Z. I've never seen any twinax or RS-232 stuff hooked up to any mainframe.

Usually when you say OS/400 and Z in the same sentence there is a problem :oops:

_________________
Paint It Blue
Hi again! I have one Hitachi Ultrastar ( model: IC35L036UCDY10-0, p/n: 08K0294, 35Gb size), my SGI Octane show as :
octane4 5# fx -x
fx version 6.5, Jan 7, 2004
fx: "device-name" = (dksc)
fx: ctlr# = (0)
fx: drive# = (1) 2
fx: lun# = (0)
...opening dksc(0,2,0)
...drive selftest...OK
Scsi drive type == IBMAS400DDYS36M S27E


But, cannot label :
label info has changed for disk dksc(0,2,0). write out changes? (yes) yes
fx/exit: Error: Invalid argument: on write at block 2 for 1 block
retry #2
fx/exit: Error: Invalid argument: on write at block 2 for 1 block
retry #3
fx/exit: Error: Invalid argument: on write at block 2 for 1 block
retry #4
fx/exit: Error: Invalid argument: on write at block 2 for 1 block
fx/exit: Warning: can't write sgilabel


Cannot mkfs, fsck :
octane4 14# mkfs /dev/rdsk/dks0d2s0
bdstrat: writeb failed: I/O error
meta-data=/dev/rdsk/dks0d2s0 isize=256 agcount=33, agsize=262144 blks
data = bsize=4096 blocks=8554112, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096 mixed-case=Y
log =internal log bsize=4096 blocks=1200
realtime =none extsz=65536 blocks=0, rtextents=0
bdstrat: readb failed: I/O error
filesystem failed to initialize
octane4 15# fsck -y /dev/rdsk/dks0d2s0
fsck: I/O error

CANNOT BLOCK READ: BLK 1
CONTINUE? yes

Primary superblock inaccessible or invalid. Trying secondary.
fsck: I/O error

CANNOT BLOCK READ: BLK 68432895
CONTINUE? yes

No filesystem on /dev/rdsk/dks0d2s0


Is possible convert/format for efs filesystem ?
Any idea which utilites or progamm there are be on IRIX ( like i scsitool, or some low-level format )?
SunForSun wrote: ... or some low-level format ?

That subject used to cause endless debates in the sgi newsgroups. If you want to cut to the chase just grab any old adaptec card (back to a 2940), stick it in a peecee, and do a low-level from the BIOS. That's the quickest, cheapest, simplest, most foolproof way to accomplish this task.
he said a girl named Patches was found ...
fx> label/set/g
change data bytes/sec to 512, let other parameters default
fx> d/format
fx/debug/format: Drive parameters to use in formatting = (current)
exit and re-enter fx, and do label/create as normal, label/sync
:PI: :O2: :Indigo2IMP: :Indigo2IMP:
robespierre thanks!

octane4 1# prtvtoc /dev/rdsk/dks0d2s0
* /dev/rdsk/dks0d2s0 (bootfile "/unix")
* 512 bytes/sector
Partition Type Fs Start: sec Size: sec Mount Directory
0 xfs 266240 68427776
1 raw 4096 262144
8 volhdr 0 4096
10 volume 0 68694016
octane4 2# mkfs /dev/rdsk/dks0d2s0
meta-data=/dev/rdsk/dks0d2s0 isize=256 agcount=33, agsize=262144 blks
data = bsize=4096 blocks=8553472, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096 mixed-case=Y
log =internal log bsize=4096 blocks=1200
realtime =none extsz=65536 blocks=0, rtextents=0
AS/400's enjoy 520byte sectors. If I understand it correctly, you've got 512bytes for data, and 8 bytes for virtual memory extension tagging. They don't have "swap" per-say, merely things may exist and run from Primary Storage or Secondary storage.

520 byte sectors ought make most systems barf. :) Low leveling it as was suggested ought slip it the bullet.
Al Boyanich
adb -w -P "world> " -k /dev/meta/galaxy/ksyms /dev/god/brain