very odd stability problem
Posted: 2011/06/02 13:22:02
Let me begin by describing our setup. Before I arrived our systems were setup on HP small form factor PCs. The system admin at the time due to the complexity of the install and the custom POS system that was in use, designed copies to be made by mirroring the drive and then breaking the mirror, thus creating 2 drives. The new disk would be used in the new system. There are no records of how the POS system works or is installed or how the server itself is configured making a fresh install not possible. Right before I started here the company started switching from the HP PCs to clearcube blades we previously used the R3150 blades and the copies work on them, however occasionally there seems to be some stability issues and I'm not sure if its due to CentOS not having the proper drivers or more likely the fact that is a broken mirror from another computer. However there are 16 R3150 blades successfully using this method of install. The problem arises when making copies of those blades for use in the new R3080D blades. during the boot process the system always hangs after starting Bluetooth services and before starting netfs. This will also occasionally happen on the R3150 blades as well. I can enter the operating system via single user mode and turn off netfs and the system will finish the boot process but never show the login screen just the blue background( no we dont have any drives that netfs is actualy loading or needed for). My current kernel is 1.6.18-164.el5PAE. When creating the mirrored copy the drive has to be placed into another computer I cant create it from the blade as it only has 1 sata port.
I have tried building a clonezilla box but since the disks have a software raid on them it is not compatable. I cannot remove the raid
I have tried installing a fresh system but due to the complexity of the POS system I cant get that up and running.
I tried upgrading the system first then just the kernel by itself, both times it broke the POS system. This system was written in ruby to use the legacy drivers and software on the servers which even when i reinstall still wont work.
I have tried copies from both working blades and working HP PCs.
I have tried adjusting bios settings, boot options and everything else i can think of.
Does anybody know of a way I can possibly stabilize these install to work on the new hardware, or a way to remove the MD software raid from teh disks without loosing any data. if I could remove the raid I could clone the boxes using clonezilla right onto the blades.
I have tried building a clonezilla box but since the disks have a software raid on them it is not compatable. I cannot remove the raid
I have tried installing a fresh system but due to the complexity of the POS system I cant get that up and running.
I tried upgrading the system first then just the kernel by itself, both times it broke the POS system. This system was written in ruby to use the legacy drivers and software on the servers which even when i reinstall still wont work.
I have tried copies from both working blades and working HP PCs.
I have tried adjusting bios settings, boot options and everything else i can think of.
Does anybody know of a way I can possibly stabilize these install to work on the new hardware, or a way to remove the MD software raid from teh disks without loosing any data. if I could remove the raid I could clone the boxes using clonezilla right onto the blades.