Pro/Forums - View Single Post - Help with 4100 Cracked Raid

blue68f100 · 10-23-2006, 01:20 PM

Differerent firmware may allocate more sectors for the smart data to use when errors are reported. All of this activity happen at the controller level and we never see it. In the old days there was a sheet that came with the drives showing where the bad track/sectors were located at. You had to enter this data manually. Now days mfg do not check for bad sectors. They just allocate abunch to be used by smart data. Which is proably the difference in the capacity size.

10-23-2006, 01:20 PM	#18
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: Help with 4100 Cracked Raid - Trying to replace 1 Drive Differerent firmware may allocate more sectors for the smart data to use when errors are reported. All of this activity happen at the controller level and we never see it. In the old days there was a sheet that came with the drives showing where the bad track/sectors were located at. You had to enter this data manually. Now days mfg do not check for bad sectors. They just allocate abunch to be used by smart data. Which is proably the difference in the capacity size. __________________ 1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820