My question pertains to a Ubuntu-based fileserver appliance called TurnkeyLinux. I'm posting here because this is a truly bizzare, generic Linux issue and I'm hoping to reach the widest number of eyeballs for a solution.
Server was working fabulously for months (two years in fact), then by accident, I discovered the boot hard drive had completely failed. Took the PC home over the weekend, replaced the boot hard drive, reinstalled the server software, and all should've been well, but wasn't.
To visualize the next part, one must know about the exact hardware config. Primary master is a simple CD-ROM, primary slave is the 15GB boot drive. The secondary master+slave are two (2) 500GB drives. Since these are all IDE drives, I believe
everything is jumpered as cable-select.
After the TKL server appliance was installed, the PC wouldn't reboot into Ubuntu ! I began by retracing my steps till (hours later) I discovered the only
procedure that would
- Startup PC. Only displays a cursor. No disc activity.
- Enter BIOS Setup and switch local IDE config to primary (to disable the Secondary controller.) Reboot.
- PC immediately loads GRUB and loads Ubuntu/TKL fileserver appliance, but somehow this is an unconfigured server. Reboot.
- Re-enter BIOS Setup and change local IDE config back to both controllers. Reboot.
- PC immediately loads GRUB and the Ubuntu/TKL fileserver appliance and customer's fileserver is operational again !
For reasons that I can't explain, the PC will not cold-boot into the TKL anymore. I stumbled on to the BIOS Setup workaround, when I physically disconnected the storage array (ie. the secondary IDE drives) and the PC booted normally. I probably would've solved this on my own, but I ran out of time that weekend and had to return the fileserver for the start of business on Monday. However, I rebooted the server a dozen times in a row, to make sure I had nailed the issue.
To add a new wrinkle, some time later (today, in fact) there was some sort of power failure at the office. I was able to bring up the server per the procedure enumerated above, but after I able to restart the fileserver, my PS/2 keyboard became completely unresponsive !
I can reboot the PC remotely, but my customer is starting to get impatient about this ongoing series of foul ups.
I suspect there's some kind of GRUB error, but GRUB is pretty much opaque to me. Also, I can't explain why the system drive (ie. /
)is designated /dev/hdc1 and not /dev/hda1. There is
when I ls /dev. For every other Linux install I've done, I seem to recall the drives are always designed by primary master+slave, secondary master+slave order.
I just don't understand. Any help is welcome. TIA.....