Leaderboard

https://lime-technology.com/forum/index.php?topic=49613.msg475716#msg475716 The Perc 6/i is not convertible to IT mode. Try to get the 1078 IR firmware (preferably the DELL software) to recover the card.

I'm more comfortable doing this as the patched file comes from the official site, so ive now managed to build an image (yes it was a faff) that includes the patched file. it has a particular tag to distinguish itself from a normal build, the tag is "patched", if you want to use this image and don't know how to reference tags then please see the faq link below Q11 (verisonyouwant = patched in this scenario) :-

You should use CA to install plug-ins and dockers. Then you have less problems like this

The thing that is bad is the number of Pending Sectors (i.e. sectors that cannot be read reliably) being non-zero. It is possible that some might be ‘false positives’, and disappear if you tried a pre-clear on the disk, but it is unlikely that all of them will disappear (at least permanently). If another disk failed then a non-zero value of Pending sectors on the parity drive would result in significant corruption of the rebuilt drive. you MIGHT get away with using it outside the array for non-critical data but I would be very wary of doing so as Pending Sectors can lead to silent data corruption.

If possible use a 2TB disk since this is how this procedure was tested and used so far, but if you don't have one I can modified and it still should work. Shutdown, swap disk 13 with original disk, use a new/spare 2tb disk for disk9. -Tools -> New Config -> Retain All -> Apply -assign missing disks (9 and 13) -check both "parity is already valid" and "maintenance mode" before starting the array -start the array (disk9 can show up as unmountable or with other data depending on what's there, ignore for now*) -stop array, unassign disk9 -start array, check emulated disk 9 mounts and contents look correct -stop array, reassign disk9 -start array to begin rebuild *edit: this was true previously but new procedure now first starts the array in maintenance mode so there's no mounting.

For those suffering from lockups etc after the backup is completed, during the removal stage of old dated backup sets, I am currently testing (in between my work's unreasonable demands upon my time) a slightly different way of starting the deletion process. I still have never been able to replicate the issue, but I have come up with a theory as to what might be going on (and why the lockup's don't occur if manually removing the directories via the command line using an identical command)

That disk is bad. I would replace ASAP. BTW, you should understand that passing any type of screening test does not guarantee that a hard disk will last any given period of time. It could fail three minutes after completing the test or it could last ten years. Preclear testing will usually catch those disks which are going to fail very early in life (~100 hours--- often called infant mortality) but three plus months is not an infant mortality type of failure. You just got hit with a bit of bad luck with that disk. Luckily, it should be in warranty.