Pro/Forums - View Single Post

DC4 · 09-15-2006, 11:31 PM

Here are my results. Some useful steps and a couple of errors on my part that might reveal inner workings.

HD Upgrade
4x30GB Quantum Fireball ==> 4x320GB 7200.10 ATA-100 Seagate

OS Upgrade
(3.1.608 ==> 3.4.807)
==========
1. On version 3.1.608 there was no admin option available to upgrade the OS. So I used the command line tool called OSUpgrade.exe.
To get OSupgrade.exe, I ran the SnapOS 4.0.860 PATCH executable (the download available publicly on Adaptec's knowledgebase). This extracted files to a folder, one of them was UTIL_ZIP.exe. I ran the extracted UTIL_ZIP.exe to unzip the OSUpgrade.exe utility and copied to c:\snap.
2. Opened a DOS prompt in Win2k ("Start/Run/cmd", CD \snap)
3. Entered the command ---> osupdate <snap-server-name> <my_password> "c:\snap\snapos_34807.sup"
4. I noticed failures were transmitted after installation of the OS (fsck error=12). Even though the Snap still contains the 30GB drives that were working fine with previous OS. I knew this was not likely a file system problem with the hard drive, but considered it was perhaps from a corrupted OS installation or bad .sup file (stay tuned).
5. I installed new 7200.10 Seagate drives (being careful to set one drive as master and the other as slave for each IDE channel, just like the 30GB drives had set).
6. Format the drives.
6a. I powered on the snap server. NOTE: My snap server began validating the newly inserted drives so access to the snap ui takes a bit and formatting/validation has to complete first.

Skip 6b if your snap server appears to begin formatting the drives.

6b. If your snap server does not begin validation, perhaps due to a configuration setting (e.g., being set to auto-repair disk errors on startup), you may need to manually format the drives. If so, navigate to http://<your-snap-server-name>/config/debug and run the command co de info

Then use the four devices in the results that have the label "Single disk" and for each, executed a reinit. For example:
co de format 10000 /reinit
co de format 10008 /reinit
co de format 10010 /reinit
co de format 10018 /reinit

7. During this process I saw same report of error fsck (file system not found - format) from Step 4. This is when I realized that my snap server was already validating/formatting. Each 320GB drive took approx 10 minutes to format.

FYI - Whether I attempted the short or long version of the first command (10000 /reinit) I got an error (but now figure that it occurs if the referenced device is already busy).

--DO NOT CREATE A RAID 5 CONFIGURATION YET --
7a. When it finished formatting, I WRONGLY selected Disk Utilities / Configure Disks / Create a Disk Configuration / RAID 5 / check-marked each of the 4 drives / clicked Next. After this finished, it reported a single drive 320GB AND a "large partition RAID5" 910GB. And the RAID5 icon was red, with a report of the same error fsck error=12, this time on the "RAID" drive.
7b. I removed RAID5 configuration, which began a reformat of all drives (completed successfully, all sizes are reported again at 320GB).
--CONTINUE --

FYI - I believe the fsck error I got was caused by the OS being unable to install parts of itself on my new drives (especially seeing as they didn't even exist when I'd run the OS upgrade in step 3).

8. I flailed around a bit before figuring this out (though it is QUITE sufficiently covered in this forum :) ). But at this point, I just needed to re-install the SnapOS. This time using the cool new Admin option in 3.4.807 available at:

http://<your-snap-server-name>/config?Func=OSUpdateSend

9. The OS upgrade window said to wait for a restart and was kinda weird when the page timed out, but I followed instructions and didn't close the browser or navigate anywhere, but just refreshed the page. It finally reported success and I clicked OK.

10. I noticed that help pages were now available and realized that the files must get stored in a hidden system folder on the drive(s).

11. For kicks, I ran co de format 10018 /reinit which completed successfully but left the drive with 7 files instead of its original 11 files.

12. When it finished formatting, I selected Disk Utilities / Configure Disks / Create a Disk Configuration / RAID 5 / check-marked each of the 4 drives / clicked Next. After this finished, it reported a single "large partition RAID5" 910GB. And the RAID5 icon is GREEN, with no reports of errors. It is now 6% complete with "Rebuilding the backup disk" which probably is normal for a RAID5 performance, or partly because I left the 128MB DRAM in there... hmm..

HATS OFF TO PHOENIX, KLOCKWORK, BLUE, AND KLINGLER WOOT!

09-15-2006, 11:31 PM	#312
DC4 Cooling Neophyte Join Date: Sep 2006 Location: Seattle Posts: 9	Re: Snap OS 3.4.805, anyone? Here are my results. Some useful steps and a couple of errors on my part that might reveal inner workings. HD Upgrade 4x30GB Quantum Fireball ==> 4x320GB 7200.10 ATA-100 Seagate OS Upgrade (3.1.608 ==> 3.4.807) ========== 1. On version 3.1.608 there was no admin option available to upgrade the OS. So I used the command line tool called OSUpgrade.exe. To get OSupgrade.exe, I ran the SnapOS 4.0.860 PATCH executable (the download available publicly on Adaptec's knowledgebase). This extracted files to a folder, one of them was UTIL_ZIP.exe. I ran the extracted UTIL_ZIP.exe to unzip the OSUpgrade.exe utility and copied to c:\snap. 2. Opened a DOS prompt in Win2k ("Start/Run/cmd", CD \snap) 3. Entered the command ---> osupdate <snap-server-name> <my_password> "c:\snap\snapos_34807.sup" 4. I noticed failures were transmitted after installation of the OS (fsck error=12). Even though the Snap still contains the 30GB drives that were working fine with previous OS. I knew this was not likely a file system problem with the hard drive, but considered it was perhaps from a corrupted OS installation or bad .sup file (stay tuned). 5. I installed new 7200.10 Seagate drives (being careful to set one drive as master and the other as slave for each IDE channel, just like the 30GB drives had set). 6. Format the drives. 6a. I powered on the snap server. NOTE: My snap server began validating the newly inserted drives so access to the snap ui takes a bit and formatting/validation has to complete first. Skip 6b if your snap server appears to begin formatting the drives. 6b. If your snap server does not begin validation, perhaps due to a configuration setting (e.g., being set to auto-repair disk errors on startup), you may need to manually format the drives. If so, navigate to http://<your-snap-server-name>/config/debug and run the command co de info Then use the four devices in the results that have the label "Single disk" and for each, executed a reinit. For example: co de format 10000 /reinit co de format 10008 /reinit co de format 10010 /reinit co de format 10018 /reinit 7. During this process I saw same report of error fsck (file system not found - format) from Step 4. This is when I realized that my snap server was already validating/formatting. Each 320GB drive took approx 10 minutes to format. FYI - Whether I attempted the short or long version of the first command (10000 /reinit) I got an error (but now figure that it occurs if the referenced device is already busy). --DO NOT CREATE A RAID 5 CONFIGURATION YET -- 7a. When it finished formatting, I WRONGLY selected Disk Utilities / Configure Disks / Create a Disk Configuration / RAID 5 / check-marked each of the 4 drives / clicked Next. After this finished, it reported a single drive 320GB AND a "large partition RAID5" 910GB. And the RAID5 icon was red, with a report of the same error fsck error=12, this time on the "RAID" drive. 7b. I removed RAID5 configuration, which began a reformat of all drives (completed successfully, all sizes are reported again at 320GB). --CONTINUE -- FYI - I believe the fsck error I got was caused by the OS being unable to install parts of itself on my new drives (especially seeing as they didn't even exist when I'd run the OS upgrade in step 3). 8. I flailed around a bit before figuring this out (though it is QUITE sufficiently covered in this forum :) ). But at this point, I just needed to re-install the SnapOS. This time using the cool new Admin option in 3.4.807 available at: http://<your-snap-server-name>/config?Func=OSUpdateSend 9. The OS upgrade window said to wait for a restart and was kinda weird when the page timed out, but I followed instructions and didn't close the browser or navigate anywhere, but just refreshed the page. It finally reported success and I clicked OK. 10. I noticed that help pages were now available and realized that the files must get stored in a hidden system folder on the drive(s). 11. For kicks, I ran co de format 10018 /reinit which completed successfully but left the drive with 7 files instead of its original 11 files. 12. When it finished formatting, I selected Disk Utilities / Configure Disks / Create a Disk Configuration / RAID 5 / check-marked each of the 4 drives / clicked Next. After this finished, it reported a single "large partition RAID5" 910GB. And the RAID5 icon is GREEN, with no reports of errors. It is now 6% complete with "Rebuilding the backup disk" which probably is normal for a RAID5 performance, or partly because I left the 128MB DRAM in there... hmm.. HATS OFF TO PHOENIX, KLOCKWORK, BLUE, AND KLINGLER WOOT!