[peterthorn]

They are partitioned as 1 partition each, both HFS + (I have tried both journaled and not). I unmount the drives in disk utility and drag the disks to the raid window (as you normally do), and it starts, but the the error appears. The partition on the first disk on the raid list is also lost, so it has started to do something (and it doesn’t seem to be malfunctioning disks, as it does it with the first disk on the list no matter what order I drag them to the window).

Unfortunately I can’t get the diskutil output right now, as I am away from the office.

Thanks,
Peter

[peterthorn]

The login on the server directly

[peterthorn]

A little late, but…
I had also problems with a procurve, but figured it out – read more here [url]forums1.itrc.hp.com/service/ forums/questionanswer.do?threadId=1059592[/url]

Peter

[peterthorn]

Just to close it – it worked when I connected with my powerbook, and it turned out to be a hanging controller. When the raid was restarted, it worked again.

Peter

[peterthorn]

[QUOTE][u]Quote by: MacTroll[/u]

Connect an ethernet cable directly between a system, like your laptop, and the RAID itself. Bonjour will take care of the rest.

[/QUOTE]

Ahh – why didn’t I think of that my self…
I’ll try it ASAP

Thanks,
Peter

[peterthorn]

Just to follow up with the solution, so others might use it:
– first telnet to the switch
– then enter config mode by writing “config”
– activate lacp on the appropiate ports eg. “int e 33-34 lacp active” (which obviously is activation for port 33 and 34)
– check that it works by writing “show lacp” which should list if the port is active or passive.

That’s it – no need for manual trunking.

Peter

[peterthorn]

I managed to to make lacp active via the telnet command
int e 1-44 lacp active
I figured that I might as well make all the ports active, as no other switches are present, so it shouldn’t be a problem. And when I run the command show lacp, all the ports is registered as active.
But when I look in the status of the network on the server, it still doesn’t work – see the error http://www11.dht.dk/~spildaftid_dk/error.png – it seems that there is a connection, but I don’t get the No Partner part.

Any ideas?
Thanks,
Peter

[peterthorn]

My problem is that I’m not sure if it is possible to enable lacp just like that…
It seems to me that I have to select the ports on the switch, trunk them and then enable them – but if it is possible to just activate lacp without trunking etc. I would prefer that.

Thanks,
Peter

[peterthorn]

I actually believe that this is the solution I am looking for
The controller with the four drives and room for three extra should be sufficient for a long time, and by using the other controller for JBOD seems like the way to do it.
The raid has allready the latest firmware, so that part shouldn’t be a problem either.
I am not by the raid right now, but is configuring the controller to use JBOD just at setting in raid admin?

Thanks!
Peter

[peterthorn]

I have also had a lot of -93 errors within the last couple of months. It topped a few days ago with more than 40 restarts in two days. The users (fortunately only 4) was, of course, on a tight deadline, so I couldn’t take it down for long.
I installed a clean 10.4 on a firewire drive and made the server boot from that (it only runs AFP service) – obviously, only as a temp solution.
It has, however, rebooted once since with the -93 error 🙁

It’s a dual G5 xserve, had a atto scsi card, but it has been removed.
I think the ram swap will be the next move (even though it has reported no errors).

Peter

[peterthorn]

The client has now been updated with the 10.4.1 update, released this morning, and it seems to work now

[peterthorn]

Well not quite the same, but perhaps related. I have set up a Tiger server with AFP sharing. When I try to connect to it with a Tiger client (via the Finder window), it shows the server, but then says that it can’t be found. All the 10.3.x clients can connect to the server, the Tiger client can connect to the 10.3.x clients’ shared folders, and if I try to connect to the server from a 10.3.x client with the 10.4 clients user/pass, it connects without any problems?!?! I haven’t been able to try it with another Tiger client yet.

[Author]

Posts