I need to revert to the forum brains trust for advice on how to proceed with a failed server boot.
My spare 1U was occupied with 4x2TB, the last time the server ran everything was fine. I have attempted to start the server and the HDD in slots 1/3/4 all blue LED, slot 2 HDD no LED. The webUI was available and the server was in degraded mode.
I swapped HDD around so a different drive was in slot 2, rebooted the server, and the HDD in slots 1/3/4 all blue LED, slot 2 HDD no LED.
This indicated to me that there was a problem with slot 2.
I opened up the server and found that the serial ATA connector for slot 2 was loose at the motherboard end. I re-seated the connector, buttoned up the server, occupied the HDD in the slots, rebooted, and I had blue LED on 1/2/4, and no LED on the HDD in slot 3.
The server is set to DHCP and it's getting a local IP, but I can't open the webUI at this address.
I've captured a serial log of the boot, and the bit that grabs my attention is the fatal error code 51007.
Kaleidescape VS Starter: version 6.2.1-15092 booting ...
Kaleidescape VS Starter: Checking quarantine state ...
Kaleidescape VS Starter: Waiting for boot file system ...
ad0: 2000GB <WDC WD2002FYPS-02W3B0/04.01G01> (WD-WCAVY7369894) [3876021/16/63/512] at ata0-master UDMA133 in slot 1
Add ad0: scp 1E3FC44, sc 1F290CC, drive 0, slot 1, channel 0, pm-scp 0
ad1: 2000GB <WDC WD2002FYPS-02W3B0/04.01G01> (WD-WCAVY7363489) [3876021/16/63/512] at ata1-master UDMA133 in slot 2
Add ad1: scp 1E40004, sc 1F2C094, drive 1, slot 2, channel 1, pm-scp 0
ad2: 2000GB <WDC WD2002FYPS-02W3B0/04.01G01> (WD-WCAVY7363410) [3876021/16/63/512] at ata4-master UDMA133 in slot 4
Add ad2: scp 1E41654, sc 1F2C274, drive 4, slot 4, channel 2, pm-scp 0
Init_AO_USB_device failed: 0x00e90003
Halting because of fatal error code 510007.
Server can be rebooted by power-cycling it or by inserting a disk.
SkDrvEvent: network connection up using port A
speed: 1000
autonegotiation: yes
duplex mode: full
flowctrl: symmetric
role: slave
irq moderation: disabled
Upload_buffer_to_log_webservice: Await_network_initialization()Upload_buffer_to_log_webservice: URL::Build_log_upload_service_formatUpload_buffer_to_log_webservice: URL:ut_URL_from_bufferUpload_buffer COMPLETE - status=0
Socket output: waiting for connection on port 1497
I'm suspecting the server thinks there are 2 failed HDD, the one that was not detected in slot 2 during the first boot attempt, when it was operating in degraded mode. And in swapping the HDD around for fault finding I've been really unlucky and had a HDD fail, or otherwise tricked the server into thinking 2 HDD have failed.
I put these HDD in my other 1U server in the same order, booted, and again the HDD in slot 3 no LED. So this particular HDD does not appear during the boot when installed in either server.
Any idea what's gone wrong?
My spare 1U was occupied with 4x2TB, the last time the server ran everything was fine. I have attempted to start the server and the HDD in slots 1/3/4 all blue LED, slot 2 HDD no LED. The webUI was available and the server was in degraded mode.
I swapped HDD around so a different drive was in slot 2, rebooted the server, and the HDD in slots 1/3/4 all blue LED, slot 2 HDD no LED.
This indicated to me that there was a problem with slot 2.
I opened up the server and found that the serial ATA connector for slot 2 was loose at the motherboard end. I re-seated the connector, buttoned up the server, occupied the HDD in the slots, rebooted, and I had blue LED on 1/2/4, and no LED on the HDD in slot 3.
The server is set to DHCP and it's getting a local IP, but I can't open the webUI at this address.
I've captured a serial log of the boot, and the bit that grabs my attention is the fatal error code 51007.
Kaleidescape VS Starter: version 6.2.1-15092 booting ...
Kaleidescape VS Starter: Checking quarantine state ...
Kaleidescape VS Starter: Waiting for boot file system ...
ad0: 2000GB <WDC WD2002FYPS-02W3B0/04.01G01> (WD-WCAVY7369894) [3876021/16/63/512] at ata0-master UDMA133 in slot 1
Add ad0: scp 1E3FC44, sc 1F290CC, drive 0, slot 1, channel 0, pm-scp 0
ad1: 2000GB <WDC WD2002FYPS-02W3B0/04.01G01> (WD-WCAVY7363489) [3876021/16/63/512] at ata1-master UDMA133 in slot 2
Add ad1: scp 1E40004, sc 1F2C094, drive 1, slot 2, channel 1, pm-scp 0
ad2: 2000GB <WDC WD2002FYPS-02W3B0/04.01G01> (WD-WCAVY7363410) [3876021/16/63/512] at ata4-master UDMA133 in slot 4
Add ad2: scp 1E41654, sc 1F2C274, drive 4, slot 4, channel 2, pm-scp 0
Init_AO_USB_device failed: 0x00e90003
Halting because of fatal error code 510007.
Server can be rebooted by power-cycling it or by inserting a disk.
SkDrvEvent: network connection up using port A
speed: 1000
autonegotiation: yes
duplex mode: full
flowctrl: symmetric
role: slave
irq moderation: disabled
Upload_buffer_to_log_webservice: Await_network_initialization()Upload_buffer_to_log_webservice: URL::Build_log_upload_service_formatUpload_buffer_to_log_webservice: URL:ut_URL_from_bufferUpload_buffer COMPLETE - status=0
Socket output: waiting for connection on port 1497
I'm suspecting the server thinks there are 2 failed HDD, the one that was not detected in slot 2 during the first boot attempt, when it was operating in degraded mode. And in swapping the HDD around for fault finding I've been really unlucky and had a HDD fail, or otherwise tricked the server into thinking 2 HDD have failed.
I put these HDD in my other 1U server in the same order, booted, and again the HDD in slot 3 no LED. So this particular HDD does not appear during the boot when installed in either server.
Any idea what's gone wrong?
Last edited: