March 25, 200719 yr I have 2 of my UnRaids running on v4.0beta4, I have a reboot problem on one of them. My Main tower gets an error message in a continuous loop when I reboot using the Web interface. I get:- "atkbd.c: SPURIOUS ACK ON ISA0060/SERIO0. SOME PROGRAM MIGHT BE TRYING TO ACCESS HARDWARE DIRECTLY. I just closed the web interface immediately after clicking reboot then this didn't occur. It doesn't happen at all on the other v4beta4 server. Mark.
March 25, 200719 yr Make sure the only USB Storage device plugged into your server at time of re-boot is the Flash.
March 25, 200719 yr Author Make sure the only USB Storage device plugged into your server at time of re-boot is the Flash. The USB Storage device is the only USB device plugged in at startup (or ever). I have no other devices connected to it, the keyboard is a conventional one. Mark.
March 25, 200719 yr Please double-check the Flash & make sure the volume label is "UNRAID" and the syslinux.cfg file reads: default unRAID label unRAID kernel bzimage append initrd=bzroot rootdelay=10
March 25, 200719 yr Author Please double-check the Flash & make sure the volume label is "UNRAID" and the syslinux.cfg file reads: default unRAID label unRAID kernel bzimage append initrd=bzroot rootdelay=10 syslinux.cfg reads exactly as it should, is there a way to read the volume label of the flash via Telnet? I have a large re-arrange of files going on at the moment between servers & don't want to shut down that machine for a few hours (at least). Mark.
March 25, 200719 yr Author Please double-check the Flash & make sure the volume label is "UNRAID" Flash is labelled "UNRAID", managed to get the same problem again when Windows explorer was still focused to the server whilst I did a re-boot. Mark.
March 26, 200719 yr Author I don't know if it is a coincidence or not but doing a lot of beta testing today, I decided to shut down the other UnRaid on this network to try & work out whether it was contributing to my network performance issue. The "Non" Local Master" UnRaid has been off all afternoon and I've had none of the "Ack" problems when rebooting (and I've done LOTS of that today. I've had to move one of my servers (running 3.1beta2) to my office (that's what I built it for) and another here contains critical data on another network so I'm down to 2 UnRaids to beta test on at the moment, both running v4.0beta4. One running perfectly, one with network issues that I'm sure a driver related. Mark.
March 27, 200719 yr Author Please try 4.0-beta4. The "Spurious ACK" message should disappear. You mean beta5 surely? OK, I will try it once my parity recalc completes today. I didn't like being left with 4 errors listed on some drives after some beta testing yesterday so started a complete parity recalc this morning. Mark.
Archived
This topic is now archived and is closed to further replies.