trixbox 2.6.2.2 ISO installation problem
Submitted by Peter847 on Wed, 03/04/2009 - 9:28pm.
I am currently running version 2.6.1.11 and decided to do a clean install of 2.6.2.2 but it freezes after I select my keyboard type in the GUI screen. Here are more details that might help:
The only issue I saw on the original 2.6.1.11 install was an error message saying it was removing an inconsistent RAID set but I have the raid controller disabled in the BIOS. I ignored it and the installation went through OK.
To get to the GUI screens on 2.6.2.2 I have to use the "skipddc" option otherwise it freezes before it gets to the GUI screen. I've tried the "noprobe" & "resolution= . . ." options but they do not help. I've also tried turning on & off various peripherals in the BIOS but nothing seems to work. The motherboard is based on the SiS 761GX/965L chipset.
Is there any way to bypass the GUI & do a CLI install or does anyone know how to get the GUI working?
 
What GUI screen???? trixbox
Wed, 03/04/2009 - 10:18pm
What GUI screen???? trixbox does not have a GUI. It as a web interface.
Are you trying to install the x server?
--
Scott
aka "Skyking"
 
Sorry maybe my terminology
Thu, 03/05/2009 - 6:25am
Sorry maybe my terminology is wrong. All the previous versions of trixbox I have installed use a command line inteface, character based screens, no mouse and they have always installed no matter what hardware I used. With 2.6.2.2 the installation starts with the familar character based screens but then I see a CLI output saying it is loading the x server - can't be sure about this because it goes away quickly. Then I get a full graphics based screen with a mouse & fancy buttons that says it is installing Centos 5 - sorry if I've got it wrong but I thought the former were probably CLI generated screens and the latter a GUI from an x server.
However just to clear this is nothing to do with the web interface, my issue is trying to install trixbox onto a clean machine from the ISO. I suspect it is a hardware/driver problem, probably because the SiS chipset is a little different from the norm.
Anyone got any ideas?
 
The ISO does not install X -
Thu, 03/05/2009 - 11:10am
The ISO does not install X - Something is wrong with your burn.
--
Scott
aka "Skyking"
 
Ok I'll download & burn
Thu, 03/05/2009 - 12:09pm
Ok I'll download & burn again . . . but it passed the verify after the burn & the verify check at the begining of the ISO installation.
 
gui / x server
Thu, 03/05/2009 - 1:51pm
Um Scott, TB does load X server at the install point
it loads it so you can set time zone / password and so on.
To the OP are you using a USB keyboard?? if so do not
 
If there is an error
Thu, 03/05/2009 - 2:12pm
If there is an error sometimes the iso defaults to a base install of CentOS. I have never seen it go to graphical mode.
 
When you install tbCE there
Thu, 03/05/2009 - 2:45pm
When you install tbCE there should be no X screen to setup date/time/etc...
However, the tbPRO installation does use X.
 
Thanks for the help can I
Thu, 03/05/2009 - 2:49pm
Thanks for the help can I clarify what is happening before I take my system down again.
The x server may be a false lead - I saw a message briefly appear & I think it said something about "loading x . .". However what is certain is that after the usual trixbox blue screen & "loading anaconda" message, I go into a very different screen than all previous trixbox installations. It has a white background, an animated mouse, scroll bars etc and starts with a CentOS 5 logo, it then proceeds to a select language screen & a select keyboard screen before freezing. So it looks like my problem is not that one of these screens freezes but that I should not even be there in the first place - correct?
Finally to answer the USB keyboard question, yes with a USB CD drive as well but I went back to a PS2 keyboard & an IDE CD drive & disabled the USB ports in the BIOS just to be safe.
 
x server
Thu, 03/05/2009 - 5:03pm
My bad, I do remember X server loading , but I have not install a TB distro in a good long time
maybe it was Pro I loaded last.
anyway the issue is the hardware, TB does not like some USB drives / KB's the Kick start script gets lost.
 
Download a fresh copy of the
Thu, 03/05/2009 - 5:59pm
Download a fresh copy of the ISO, burned CD on a different machine and . . . exactly the same as before. There is a couple of messages that appear straight after the "Probing for Video Card" message that definitely say something about "Waiting for X server to start . . ." but it runs to quickly to read. I then go to a full graphics screen with a large CentOS logo and a couple of screens later it freezes.
I tried a 2.6.1.13 CD, reset the PC & it loads fine, so what has changed in the linux loader between 2.6.1.13 & 2.6.2.2
 
Yes, trixbox-2.6.2.1.iso ISSUE as well
Thu, 03/05/2009 - 11:50pm
First, let me say that I'm not an expert, but not quite a noob. Been using since AAH/A@H.
Anyway, I wanted to do an install with 2.6.2.1 as posted on the trixbox.org/downloads link, http://master.dl.sourceforge.net/sourceforge/asteriskathome/trixb...
I downloaded... twice... from two separate networks... on two different computers... but both with Firefox... at two different times... both failed the media check and the hash/md5 value.
In the meantime, the end user (now a new customer because of the issues that they/"son/IT staff" had with their TB) was down. So instead of using 2.6.2.1, I downloaded the trixbox-2.6.1-i386.iso (with Firefox) from Sourceforge. And guess what no problems on hash/md5 match, install, and operation. Weird that 2.6.2.1 gave me issues.
On a side note, the end user actually started a paid support incident with Fonality yesterday. Per their words... on hold for 40 minutes after paying. No callback as of today at 7pm. At least to my knowledge.
I also called today to follow up and mention the hash/md5 issue that I experienced. I also stated that we had not received a call back from the previous day's paid support incident. Sales (of course, the only way to get a live person) transferred me to Grant's voicemail. I left the details and received no callback.
The good news is that the end user is up and running with 2.6.1.
This is just my story... I'm known to make mistakes so who knows about the 2.6.2.1 iso... Maybe it was my error.
John
duckdive@yahoo.com
 
Need some help here
Fri, 03/06/2009 - 4:59pm
Need some help here please!
I think my issue is something to do with the SiS on-board graphics . If I put in an old PCI video card I stay in the CLI mode but still fail later in the process because it "Cannot open display: 1". Interestingly if I add the "noprobe" option it still probes & finds the SiS video controller even if the output is coming from the PCI board. As this system works fine on 2.6.1.11 there must have been a change in the kernel drivers?
 
Yes, we update the kernel
Fri, 03/06/2009 - 7:36pm
Yes, we update the kernel and driver all the time to stay current and have driver available for new hardware. trixbox will NOT work on every PC out there. We recommend users stick to very standard hardware to avoid problems. Seems like in this case you should try a different system. Anything from the Dell optiplex line or a trixbox appliance will work very well.
 
No good on OptiPlex 755
Wed, 03/25/2009 - 12:48pm
I'm trying to install 2.6.2.2 on an optiplex 755 and am having the problem experienced.. After selecting the keyboard, anaconda starts using a full CPU core and the system essentially hangs.. no error messages in any of the consoles (alt+f1,f2, etc). I am using a USB keyboard as I have no option for a PS2.
 
CentOS 5.1
Wed, 03/25/2009 - 2:04pm
I should also note that CentOS 5.1 installed just fine on this system.
 
PIAF & AsteriskNow
Wed, 03/25/2009 - 3:16pm
I have tried both PBX in a flash and AsteriskNOW, both seem to load OK so I'm not convinced this is a hardware issue. I do not have the time or knowledge to work through the install scripts to find out why it is stalling so it seems the only answer is to either buy Dell hardware . . . or move to one of these distributions.
 
Hardware RAID
Thu, 03/26/2009 - 9:19am
Let it be known this was a hardware RAID problem.. RTFM for me. on-board SATA RAID-1 was somehow causing anaconda to go to max CPU. Interesting that 1) CentOS 5.1 installed on this system fine, 2) according to console the disk was successfully detected by trixbox. Oh well...
 
Hardware Raid
Thu, 03/26/2009 - 10:04am
Interesting, on earlier trixbox installations I have got an error message saying "Incorrect RAID set . . . . something, something" even though I have the SATA RAID disabled in the BIOS. I have always ignored the message and the installation has proceeded OK, maybe this is not the same with the latest trixbox version.
 
A quick note about RAID
Thu, 03/26/2009 - 10:16am
A quick note about RAID issues, since I've noticed that so many people are having them. Hardware RAID cards are the best sort of RAID to have when using trixbox because when trixbox is being installed, the hardware RAID shows only 1 drive. EX: if you are using a hardware RAID 1 on two 500GB drives, (RAID 1 is mirroring), when you install trixbox it will detect only 1 drive, and install just fine WITHOUT any drivers.
If you buy a RAID hardware card, make sure it is *actually* a hardware RAID card. Adaptec sells a ton of RAID cards with something called 'hostRAID'. The basically sell the card saying that it is hardware RAID card, but in actuality, it is software RAID. I've recently dealt with someone who had this issue, and the workaround is not pretty.
If you have a software raid card, then when you boot up trixbox, look at the kernel boot options and set them appropriately (sataraid, etc.) and you will be prompted to point the install to your driver location (USB stick or something).
In my personal opinion, the best thing to do is use a real hardware RAID card. If you can't do that, then just have multiple SATA/IDE drives internally, and install on one of the drives (this applies only for RAID 1 users), then once trixbox is installed, install the tbm-raid package and then setup software RAID with that.
Cheers!
 
RAID vs No RAID
Thu, 03/26/2009 - 1:34pm
Thanks for the tip. I believe my motherboard isn't true hardware RAID otherwise it would not require special drivers, which is why I disable it in the BIOS and do not use the SATA ports at all. But I still seem to get problems. Maybe my problem is due to Linux finding the RAID chip on the motherboard but it is disabled in the BIOS?
 
Same Issue
Thu, 03/26/2009 - 6:53pm
I am having the exact same issue. Chipset on mine is a Via Uncrome Pro IGP.
 
Got it!
Thu, 03/26/2009 - 7:46pm
I only found this thread because my machine kept on freezing after I selected U.S. Keyboard but anyways I finally got past this issue by swapping the hard drive. I was using a old 300GB Maxtor SATA hard drive and since I kept having issues with the powerspec I originally wanted to use, I swapped out the drive and installed it in an Optiplex GX580 and I got the same problem. I figured it was either the CD or the hard drive. I swapped the drive with a Seagate 160GB SATA HDD and it got past that step. The very next screen that comes up after you select U.S. keyboard is the disc partioning options. Anyways my install is going now and it looks good so far. I'll keep you guys updated once it's all installed.
***Side Note*** I had the same issue where it would not go past blue screen after checking the CD media. The only way I could get the Cent OS part of the install was if I did "linux skipddc" or "linux resolution 800x600".
 
Yes, I could get past the
Thu, 03/26/2009 - 8:09pm
Yes, I could get past the blue screen too by using the linux skipddc option but I then go into the CentOS X server installation mode (impossible according to others!) and lock up. Please post if you find the underlying cause.
 
OK, I am totally bapheled
Fri, 03/27/2009 - 4:51pm
OK, I am totally bapheled now. After writing my post last night I went back to my install to realize it was frozen so I called it a night and went home. I spoke with one of the technicians here this AM and we redownloaded the 2.6.2.2 ISO just in case and tried re-installing on the Optiplex GX580 with the same 160GB HDD that the install froze on last night. To my surprise the whole install is completly different. There is no more Cent OS GUI and now my install is complete. I think that the reason we keep getting the GUI is because we used the "linux resolution=800x600" or "skipddc" command. Anyways, I wiped the same 160GB drive and put it in my powerspec with the CD that worked minutes ago on the Optiplex. I did get further then I did get before and I didn't have to use the "linux resolution=800x600" command but it crashed again during the install at the point where it was formatting the drive. I am just going to say that there has to be some kind of hardware compatiblity issue with that machine. I will also recommend redownloading the ISO. The new image for some reason got me much further in the install (even though I still had other issues).
 
Snap
Fri, 03/27/2009 - 5:48pm
Yep - I have the same problem. Using the skipddc option takes you into the CentOS GUI, which then freezes but without it the install halts with a blue screen after it detects the video card. Interestingly if press Ctrl/Alt/Del at the blue screen Linux closes down gracefully but in the CentOS GUI it locks up & needs a hardware reset. I'm staying on my old version of trixbox until I have the time to "burn in" a Pbx In A Flash system.
 
I've tried to clean install
Mon, 03/30/2009 - 9:58am
I've tried to clean install 2.6.2.2 on 3 separate system configurations and the all hang after anaconda starts(after you select your keyboard layout).
 
What kind of machine are you
Wed, 04/01/2009 - 6:59am
What kind of machines are you running it on? I am wondering if this issue has to do with the raid controllers.
 
I got it to install by
Wed, 04/01/2009 - 4:46am
I got it to install by disabling 1394 in the BIOS and install went fine
System Build:
MB: GA-MA790GP-DS4H
CPU: Phenom 9950 BE
RAM: 2GB OCZ Platinum
HDD: 2x VelociRaptors
NIC: Intel Pro/100 Server Adapter
 
Nice! I am going to try
Wed, 04/01/2009 - 7:00am
Nice! I am going to try that on my PowerSpec Machine.
 
Many of the Same problems
Tue, 04/14/2009 - 10:16am
I'm having many of the same problems listed in this thread. I've been a TB user since 1.1 and have loved it. I've purchased support plans every year since. My company is now out of business and I simply wanted to use TB for my home and 2 VOIP lines. Piece of cake; right? Not so. I'm a serious Windows guy with plenty of experience with old school SCO/Unix as well. I've got to say that this has been the worst TB CE experience to date. I know things are shaking up with personnel and the economy but to release a build that doesn't install for SEVERAL reasons is a little surprising. Ok, enough ranting; now I will help the group the best I can.
I fresh installed 2.6.2.2 on a Dell Dimension 8400. I know it has worked for up to 2.4 on this machine before. I planned on using the built-in HARDWARE RAID 1 but it would hang on the blue screen (and I thought that BSOD was only for Windows...?) Read a thread to disable RAID so I did. I had to disable RAID, disconnect the extra HD and hurray, it installed. I then proceeded to secure my machine, change passwords, etc... Several files were missing, in the wrong place, and started over. I reinstalled clean again, this time proceeding straight to config/status; screen won't come up. Package manager gets 500. Several screens don't look like a tutorial I found on SureTeq site even though they're tagged the same version. I changed the timeout as mentioned in this thread and that works for PMgr, but not for the Status/Config.
Now, this is a simple system and I'm wanting to get on the TBox banner waiving platform again and I'm trying real hard to waive it, but DAMN, it's hard to get motivated. So it appears that one shoudl install an older version, yum it, upgrade it, and it will have better luck? What should I do?
I'm in no time crunch like a lot of you so I'm simply going to install 2.4.2.0 and see how that treats me.
Any feedback would be greatly appreciated and I hope the group has learned from my post. Peace
 
Work around
Sun, 05/24/2009 - 12:56am
I just installed 2.6.2.2 on a Dell T100 server and ran into the exact same problem. The CD boots up fine but as soon as you select your keyboard type and hit enter, the system just freezes at a blue color screen just right after "loading trixbox installer". Installed it with 2.6.1 CD and it works fine. The first thing I throght about was the crapy Adaptec "RAID" controller. I removed it and put the HD back on the onboard SATA controller but it resulted the same thing. I tried again by remove all the HD from the system and booted the CD without any HD into. I was able to pass the frozen blue screen but it complain immidiately with the error " no hard disk found". So I know that frozen issue is not caused by anything in the server but the hard disk. I tried different brand and different size HD but no luck. I than tried attach an external USB drive and installed it again. The CD boots up fine and was able to install the TB in an USB drive. I pull the drive from inside the server and put it in the USB enclosure and tried install it again. It froze exactly like it was in internal. The final conclusion is the TB 2.6.2.2 installer has something different with the eariler version and caused incompartible issue with some HD. Here is my work around to get the 2.6.2.2 on this Dell T100 server with incompartible drives.
1. keep my RAID controller in the server but disconnect all cables to the HDs.
2. Attach an external USB drive to the server.
3. Install the TB 2.6.2.2 into the USB drive. If you don't have a compartible HD in the USB enclosure, you can use 4GB USB memory stick.
4. Reconnect all internal HDs to the RAID controller and build the array.
5. Use disk cloning boot CD to boot the system.
6. Clone all partition in the USB drive into the internal drive array.
7. Disconnect the USB drive and reboot the system from the array
8. Seat back and Smile...
A little bit complicate but works. Hope this help anyone else who has this same issue.
 
That is a crazy solution.
Sun, 05/24/2009 - 1:23am
That is a crazy solution. Where there any partitions on the HD that would not work?
You are closer to anyone to actually finding what is tripping folks up with the new version. When I test (and I know most developers do the same thing) I am always installed to a clean VM.
It would be useful to get to the root cause of the issue. I am sure that Randall would slipstream in any changes that would make the install smoother.
By any chance did you try the 2.8 beta?
--
Scott
aka "Skyking"
 
It's the only way
Sun, 05/24/2009 - 2:19am
It's the only way I can figure out to force this impossible to be possible. I did try every options that the TB loader offer like "noprobe", "resolution=", "linux dd" ..... None of them work. All i knew about is when the server froze, the DELL server made a beep sound and told me the CPU hung. I'm not an expert in Linux to diagnose why the CPU hung at that moment but I do know as long as the Linux installed with the RAID controller driver alone with the kernel, the HD will boot up just fine even you clone it to a different HD. The issue I was facing just incompartible HD. All I have to do is install it into a compartible HD and clone it back to the HD that I want. The DELL T100 server was the one I used the first time. I didn't have any issue with the 2.6.2.2 install in ther other model nor in the VM. I purchased this new server for the customer and had no enough time to exchange it for a different model. I had to make it work no matter what. TB 2.8 is still in beta and I don't want to put it in production yet.
The other possible solution is install the TB in VM and install the RAID controller driver or compile the driver into kernel and use virtual to physical tool to convert the VM image back to the server.
 
You never answered by
Sun, 05/24/2009 - 10:02am
You never answered by question, was there any type of partition on the HD prior to installation?
There may have been a OEM test or driver partition, often these have a small Linux Kernel to execute the diags.
--
Scott
aka "Skyking"
 
No existing partition
Sun, 05/24/2009 - 10:48am
The server was purchased without OS. It should be blank. I throught about that issues as well. I ran fdisk and made sure both drives are blank.
 
I have the same issue with hardware RAIDS
Sun, 05/24/2009 - 6:47pm
I use Elastix distro without issues try that it uses Freepbx plus has a Hardware and phone detection tool.
 
Too little, too late
Mon, 05/25/2009 - 10:27am
Apologies in advance for the "party pooper" post but I need to add my two cents here.
I started this thread nearly 3 months ago & was roundly blasted for my lack of knowledge on linux/trixbox ("What GUI screen????") and ISO burning ("ISO does not install X - Something is wrong with your burn"). The official trixbox answer was to go and buy different hardware ("Seems like in this case you should try a different system"), even though all previous versions of trixbox worked fine.
My cure for this issue was simple: install pbxinaflash, it works out of the box.
 
I love these
Mon, 05/25/2009 - 12:54pm
I love these posts:
Quote:
My cure for this issue was simple: install pbxinaflash, it works out of the box.
Every distro has it's strengths and weakneses, however in this case I question your motives for posting this as trix and PBXiaf are on the same CentOS kernels.
--
Scott
aka "Skyking"
 
Facts speak for themselves
Mon, 05/25/2009 - 2:49pm
All I can say is that trixbox did not install whereas pbxinaflash did, simple as that. As for my motive for posting here, it is to encourage you not to shoot people down quite so quickly.
 
Blast you? My original
Mon, 05/25/2009 - 2:56pm
Blast you? My original comment was that x was not installed by default, something is wrong.
As I said in my later post to you I would love to define what is going on with the "corner cases" of folks who simply have a disaster of a time installing.
For 99.999% (unscientific of course) of the install it's perfect the first time.
If PBXiaf works for you that's great. They have a good community of folks.
--
Scott
aka "Skyking"
 
I've worked with tons of
Tue, 05/26/2009 - 12:05pm
I've worked with tons of systems 2.6.2.2 that are in production, and never once experienced issues where I could not get trixbox to install. I'm really curious to see what the -root- cause is for these machines? If there is anyone else out there experiencing these issues and reading this thread, please post all of your machine hardware details, as well as everything you have tried to resolve the issue, as I would love to hear it and get working on some sort of fix.
I would also urge anyone who gets the graphical installer to download the ISO again from another OUTSIDE nework (eg: at a friend's home, or something), and also burn the image to a different brand of CD. (Will help eliminate image issues). If both of those fail, then please let us know!
 
Is the issue with the hard disk
Tue, 05/26/2009 - 11:34pm
After many time of retry the installation of 2.6.2.2, I have the following conclusion.
A. The anaconda installer in 2.6.2.2 does not like some model/brand of hard disks
B. Some of the hard disks don't like the installer in 2.6.2.2
Here is what I tested with in last week.
System A -
Dell PowerEdge T100 server
1 224-1524 Dual Core Pentium E2220, 2.4 GHz, 1MB Cache, 800MHz Front Side Bus for PowerEdge T100
1 311-9356 2GB, DDR2, 800MHz, 1x2GB Dual Ranked DIMMs
1 341-5815 160GB 7.2K RPM SATA 3Gbps 3.5-in Cabled Hard Drive
1 341-5437 No Floppy Drive
1 420-6320 No Operating System
1 430-0488 On board Network Adapter
1 313-6943 16x DVD Drive, Internal
2 341-5824 160GB 7.2K RPM SATA 3Gbps 3.5-in Cabled Hard Drive
1 341-7772 Onboard SATA, 1-2 Drives connected to onboard SATA controller - No RAID
System B -
Trixbox Appliance - 512MB DDR RAM, 2x 80 GB SATA hard Disk
I added an adaptec 1220SA RAID controller in the DELL server before I started the installation. When I installed the TB 2.6.2.2 on the DELL server, I ran into the system frozen issue just right after I selected KB type and the system is loading the anoconda Trixbox installer. It's right before I can select the time zone screen.
My first thought was crappy RAID controller is not compartible. I removed it and put all the hard disks on the onboard SATA contoller and retried the installation. It ran into the same issue.
My second thought was the hard disks ship from DELL may have utility partition that may be causing issue. I made a DOS disk and ran fdisk to check the disk and saw no partitions. To be sure the disk has nothing in it that may cause interference, I ran low format untilty on the disks to zero out everything in it. Ran the installation again but still the same issue.
My third thought was may the installer has issue creating software RAID on the disks and hung. I removed one of the disks and install it again without "sataraid" option. It's still the same problem. I than tried all other option like the people mentioned above but no luck.
My fourth thought was the bad CD or bad downloaded ISO image. I downloaded the ISO again and burn it to three different brand of CDs (HP, Sony, TDK). Tried the different CD but still the same issue. I tried the installation with the 2.6.2.1 CD but the same issue. I than tried the 2.6.1 CD and it installed successfully. Since I was able to install 2.6.1, I knew the server is good. There is nothing wrong with it.
My fifth thought was the incompartible hard disk. I took both DELL disks (WD 160GB) out of the server and put in a Seage 500GB disk and ran the installer again. It ran into the same hang up issue.
My Sixth thought was the disk size too big. I took the Seagate disk out again and put in a Hitachi 150GB but still the same issue.
I was pretty much stuck there and almost ran out of idea. I stopped what I was doing and took a lunch break. When I came back from lunch, I started my seventh thought.
My seventh thought was the 2.6.2.2 does not like any of my hard disk, I removed all the disks and installed it again. It was able to past the freezing screen and got the "no disk found error".
The conclusion at this point was the system froze right at the moment it's trying to detect the disk size/partition. For whatever reason, it caused the system to hang.
To confirm my conclusion is true, I put a 4GB USB memory stick on the back of the DELL server and started the installation again without any hard disks. The installation ran successfully and put the TB 2.6.2.2 into the memory stick. So the problem is the hard disk.
My eighth thought was still on the hard disk because I had installed this 2.6.2.2 on four other different systems just a month before. I knew It worked. I started look for the systems that I had installed before and I found one Trixbox appliance that I installed with 2.6.2.2 couple weeks ago. It was still in my customer site as demo unit. I ran hurry back to the customer site and pulled the TB appliance back to my office. I ran the installation on the TB appliance to make sure the ISO image I downloaded has nothing different with the one I used couple week ago. I was able to confirm the newly download ISO has no changes and it was able to installed in the TB appliance without any problem.
At this point, I knew I was pretty close to solve my issue. I pulled both disks (WD 80GB) out of the TB applicance and put them into the DELL server. I ran the 2.6.2.2 installation again and it was installed successfully.
So my final conclusion was - 2.6.2.2 installer is incompartible with some disks or some disks incompartible with 2.6.2.2 installer
To confirm my conclusion to be ture, I put the DELL hard disks into the TB applicance and ran the installation again. It hung exeactly like it hung in the DELL server. I tried all other disks in the TB appliance again and they all have the same issue. They are not bad disk since they are brand new. They are just incompatible.
My final challenge was to get the TB 2.6.2.2 installed on the DELL server with the DELL disks. The server needs to have it's original components in order to keep the warranty. I put the TB appliance disks in the DELL server and installed it with 2.6.2.2 with software RAID option. After the installation, I cloned the disk content back to the DELL disks. I put the DELL disks back to the DELL server and resized the RAID partition. Now the DELL server is running TB2.6.2.2 without any problem.
More conclusion - TB2.6.2.2 is compartible with the PowerEdge T100 Server but the installer is not. To solve the problem without engineering change in the install CD, find a compartible disk or install it with compartible disk even a USB stick and clone it back to the incompartible disk.
I have no idea why the TB installer hung with certain hard disks but hope this info can help the TB dev team to diagnose the problem.
I'm going to test the TB 2.8 Beta 2 this week with my disks to see if there is any issue with it.
 
Same Issues
Sat, 06/13/2009 - 3:22pm
I am having the same issues with installing 2.6.2.2 on a Dell Poweredge 1800 with hardware RAID1
Here's the interesting parts:
- Install CD verifies properly every time, no matter what
- Installs just fine with bios set to non-raid with a Western Digital 80GB SATA hard drive
- Installs just fine with bios set to non-raid with a Seagate 75GB SATA hard drive
- Install FAILS as soon as I put in a new Samsung 750GB SATA drive (non-raid) *
- Install FAILS if two identical Samsung 750GB SATA drives are used (hardware RAID1) *
(* - The failure is actually a "hang" after I choose US keyboard and it probes for the video card. If I ctrl-alt-del out of it, it gracefully reboots [send kill signal] which is very strange.)
So, that pretty much makes it obvious that (as jingxi02 stated), there are incompatibilities with certain hard drives.
Does ANYONE have any possible solutions for this issue? It's really frustrating because I want the security/speed of hardware RAID1 and I need at least 500GB of space for recordings. There has to be a work-around by now.. correct?
 
Member Since:
2007-09-14