Pro/Forums - View Single Post

djC · 01-10-2006, 07:10 PM

OK, here are some interesting (freaky, though -read on) developments in this quest for storage space:

I was just about to go over the cloning of disk 1 (10000) of the 4100, in order to get the OS on to the 250GB disk, when I decided I should test whether the appliance would boot without ANY disks. If it did, it would mean that the OS is not on any of the HDDs.

Indeed, after removing all ATA cables, and turning on the 4100, the appliance took some time (checking the absence of the disks, I suppose) and booted normally.

Then I turned it off, connected a single 250GB and turned it back on. Indeed, after some time, there it was, a 137GB disk 1. Hmmm, I thought, let's put the original back there. Again, there it was, a single 40GB disk 1.

I concluded that probably the trick with imaging the original disk simply would not work, as the behaviour of the appliance was the same, regardless of the disk connected.

Than it came to me, that the only thing that had a chance to make it work is to fool the OS (since it's common between 4000s and 4100s) to think that this is a 4000.

I was wondering how to do that and did -again- some reading on other people's (with 4000s) posts on this forum. An interesting finding was that ALL 4000s I came across had a HW version of 2.0.1, whereas all 4100s I came across had a HW version of 2.2.1.

Being curious by nature

I decided to change the HW version, by issuing the following commands, knowing that this could render the 4100 useless:

bios unlock
bios platformbytes 2 0 1
bios lock

Indeed, the commands executed without error, and after that, clicking on the snapappliance icon displayed the new version!

Here is the interesting (and freaky) part:
I had to go all over the procedure of reinitialising disk 1 (10000) again, now that I had changed the HW version.

So, I rebooted the server....

IT WOULDN'T boot!

I tried reseting the appliance totally: Nothing.
I tried connecting the original disk 1: Nothing (this probably also indicates that there is no OS on it).
I also tried connecting disk 1 on the extra IDE port (probably there for maintenance and repair purposes) that 4100s have. Nothing.
I also rebooted my router/DHCP server and rescanned my network for clients and the appliance is simply not there.

On the front bezel two LEDs light up: the System LED flashes twice every minute and the Link LED stays on (normal, as the net cable is connected).

My thoughts are now...

- As mentioned, the 4000s boot from disk 1.
- IF, indeed, I made the appliance think it's a 4000, it is normal that it cannot boot, as it looks for the OS somewhere it does not exist (original disk 1).
- My changing of the HW version, must have no impact on normal operation, as the appliance did react normally AFTER the change, but BEFORE rebooting (which is because the OS was still in the appliance's memory).
- if I load an image of the OS into disk 1, I could probably make it boot and then check its status

My wild guess here is that, if I manage to boot using an on-disk image from a 4000 (with OS v4 on it), eventually I will have fooled the appliance to think that it is a 4000 and format the large disks in full capacity.

Otherwise... I have a 4100 m/b to hang on the wall and four 40GB disks to spare!

If all this works, I think we may have found the solution into turning stuborn 4100s to TB-stations!

Question is.... is there anybody in here to provide me with such an image???

01-10-2006, 07:10 PM	#6
djC Cooling Neophyte Join Date: Jan 2006 Location: Mediteranean Sea Posts: 6	IN NEED of a 4000 disk image OK, here are some interesting (freaky, though -read on) developments in this quest for storage space: I was just about to go over the cloning of disk 1 (10000) of the 4100, in order to get the OS on to the 250GB disk, when I decided I should test whether the appliance would boot without ANY disks. If it did, it would mean that the OS is not on any of the HDDs. Indeed, after removing all ATA cables, and turning on the 4100, the appliance took some time (checking the absence of the disks, I suppose) and booted normally. Then I turned it off, connected a single 250GB and turned it back on. Indeed, after some time, there it was, a 137GB disk 1. Hmmm, I thought, let's put the original back there. Again, there it was, a single 40GB disk 1. I concluded that probably the trick with imaging the original disk simply would not work, as the behaviour of the appliance was the same, regardless of the disk connected. Than it came to me, that the only thing that had a chance to make it work is to fool the OS (since it's common between 4000s and 4100s) to think that this is a 4000. I was wondering how to do that and did -again- some reading on other people's (with 4000s) posts on this forum. An interesting finding was that ALL 4000s I came across had a HW version of 2.0.1, whereas all 4100s I came across had a HW version of 2.2.1. Being curious by nature I decided to change the HW version, by issuing the following commands, knowing that this could render the 4100 useless: bios unlock bios platformbytes 2 0 1 bios lock Indeed, the commands executed without error, and after that, clicking on the snapappliance icon displayed the new version! Here is the interesting (and freaky) part: I had to go all over the procedure of reinitialising disk 1 (10000) again, now that I had changed the HW version. So, I rebooted the server.... IT WOULDN'T boot! I tried reseting the appliance totally: Nothing. I tried connecting the original disk 1: Nothing (this probably also indicates that there is no OS on it). I also tried connecting disk 1 on the extra IDE port (probably there for maintenance and repair purposes) that 4100s have. Nothing. I also rebooted my router/DHCP server and rescanned my network for clients and the appliance is simply not there. On the front bezel two LEDs light up: the System LED flashes twice every minute and the Link LED stays on (normal, as the net cable is connected). My thoughts are now... - As mentioned, the 4000s boot from disk 1. - IF, indeed, I made the appliance think it's a 4000, it is normal that it cannot boot, as it looks for the OS somewhere it does not exist (original disk 1). - My changing of the HW version, must have no impact on normal operation, as the appliance did react normally AFTER the change, but BEFORE rebooting (which is because the OS was still in the appliance's memory). - if I load an image of the OS into disk 1, I could probably make it boot and then check its status My wild guess here is that, if I manage to boot using an on-disk image from a 4000 (with OS v4 on it), eventually I will have fooled the appliance to think that it is a 4000 and format the large disks in full capacity. Otherwise... I have a 4100 m/b to hang on the wall and four 40GB disks to spare! If all this works, I think we may have found the solution into turning stuborn 4100s to TB-stations! Question is.... is there anybody in here to provide me with such an image???