Making sense of a serial connection to an ss4000 NAS

update: I consider the unit bricked and will donate it to an open source enthusiast.

I'm trying to make sense of this serial connection on my Intel ss4000 nas (a better picture can be seen here).
I found this dl10-db9 connector in an old computer, should be okay right ?
First problem is that this little cable fits in the pin header in two directions, so I have to figure out the correct way to insert it in the pin header.
The pin header has a whole in its casing on one side, and as far as I can tell from pictures on the internet the red line of this little cable should be on the right side, as in this picture:
I then connect this to a brand new serial cable into a real serial port on another Debian computer. All of the following commands give a blank screen when all cables are connected and the NAS is running(*).

cu -l /dev/ttyS0 -s 9600
cu -l /dev/ttyS0 -s 19200
cu -l /dev/ttyS0 -s 115200
cu -o -l /dev/ttyS0 -s 9600
cu -o -l /dev/ttyS0 -s 19200
cu -o -l /dev/ttyS0 -s 115200
screen -l /dev/ttyS0 9600
screen -l /dev/ttyS0 9600 8N1
screen -l /dev/ttyS0 19200
screen -l /dev/ttyS0 38400
screen -l /dev/ttyS0 115200

115200 should be the correct transfer rate.

If I connect the little cable with the red line on the left side (pin 9 of the header according to this blog) like in the below picture, then all of the above commands give me lots of garbage (at different speeds...) on the screen.
How can I get this serial connection to work ? Do I have to reboot the NAS with every attempt ?

(*) The NAS does not respond to ssh or ping since the last 'aptitude update && aptitude upgrade' :(


switching backup devices

The sparc backup server from 2005 was up for a replacement. It was too noisy and too power hungry to keep it running, so it was turned off most of the time anyway. I decided yesterday to replace it with a qnap TS-412, but I wanted to keep the four sata disks, and preferably also the data.

One problem is that there is no way for four RAID5 configured disks to insert them into the qnap without them being "initialized" (as in completely erased losing all data).

First I wanted to be sure all four disks where still operational, which I couldn't do as long as the adaptec controller was in the sparc computer, so I had to move everything to an (already full) x86 machine... or not ?

Being a Linux user, I am generally lazy, so I figured it also had to work if I just moved the controller to the x86, leaving the disks in the sparc... not without risks:

1. the 64-bit pci card had to work in a 32-bit pci slot. Some don't... luckily this one did! The picture below shows the Adaptec controller in the x86 on the right, with the sata cables going through the back of the sparc to the four disks.

2. What to power on first, the x86 or the sparc ? Can something break if only the controller, or if only the disks have power ? I pressed both buttons simultaneously... was I lucky that it worked, or is this normal ?

3. The fricking sparc blade 1000 cover has to be shut tight for the sparc to actually power on. Note also the lack of any cables on the x86 (the left), except for the cat5. This computer has been working without keyboard or display since 2003... why bother when ssh and ssh -X can do everything!

4. Will the x86 (running debian) still come up when I add an extra scsi controller? Note that this x86 was installed with Debian ten years ago, and since then upgraded to $currentDebianToyStoryCharacter. It did make the RAID5 appear as /dev/sda, but thanks the UUID= in /etc/fstab it all worked fine!

root@barry:~# fdisk -l 2>/dev/null | grep Disk
Disk /dev/sda: 960.0 GB, 959994396672 bytes
Disk /dev/sdb: 60.0 GB, 60022480896 bytes
Disk /dev/sdd: 200.0 GB, 200049647616 bytes
Disk /dev/sdc: 82.0 GB, 81964302336 bytes

Everything worked, data was copied, disks inserted in the qnap and reformatted and all is up and running.


Just an hour ago Microsoft Windows had a small problem displaying tram and bus information here in Antwerp ;-)