June 7, 201115 yr Hey all, I've had some insane problems over the past couple of weeks with my unRAID server and I am to the point of pulling drives out and copying over data to new hard drives. It seems that all 6 Seagates in my array have an unreal amount of Read_errors and other errors via the SMART reports. I'm pulling all these drives and going to rsync them in linux to new hard drives. As I'm doing this I'm wondering if I format these new drives as Reiserfs and after I copy the data, would I be able to have them 'just work' in unraid? That would be sweet, but I'm guessing it's not that simple... Man this is horrible and I really have no idea WTF has happened to my array, but at this point I need to start backing up these drives as I do not have a valid config
June 7, 201115 yr Any reason you can't use Joe's preclear script? http://lime-technology.com/forum/index.php?topic=13054.0 That will test the entire drive (multiple times if desired) and write the proper signature to it so Unraid can bring it online almost immediately.
June 7, 201115 yr Hey all, I've had some insane problems over the past couple of weeks with my unRAID server and I am to the point of pulling drives out and copying over data to new hard drives. It seems that all 6 Seagates in my array have an unreal amount of Read_errors and other errors via the SMART reports. I'm pulling all these drives and going to rsync them in linux to new hard drives. As I'm doing this I'm wondering if I format these new drives as Reiserfs and after I copy the data, would I be able to have them 'just work' in unraid? That would be sweet, but I'm guessing it's not that simple... Man this is horrible and I really have no idea WTF has happened to my array, but at this point I need to start backing up these drives as I do not have a valid config Although it can be a specific production run of drives that has problems, a large number of drives with errors in the same system could also be an indication of a marginal power supply, or a marginal disk controller card, or motherboard, or even memory. The issue might have started when adding "one more" drive to a system putting it over the power supply limit. If you preclear a drive, it will be partitioned as unRAID expects. If you then type this following command, it will create a reiserfs file system. mkreiserfs /dev/sdX1 (note the '1' on the end, since we want to put the file system on the 1st partition. You'll need to use the correct drive letter in place of "X" too) There is a button on the disk-management page in unMENU that will create the file-system for you if you do not want to do it on the command line. You can then load files on the drive after mounting it. (unMENU can mount it, or SNAP can mount it, of you can mount it in another linux system) Once loaded with data, the ONLY way to bring it into the array without erasing the data on it is to set a new disk configuration. The side effect of that command it to immediately invalidate parity and when you start the array it will begin a new parity calculation based on the new disk configuration.
June 7, 201115 yr Author Hey all, I've had some insane problems over the past couple of weeks with my unRAID server and I am to the point of pulling drives out and copying over data to new hard drives. It seems that all 6 Seagates in my array have an unreal amount of Read_errors and other errors via the SMART reports. I'm pulling all these drives and going to rsync them in linux to new hard drives. As I'm doing this I'm wondering if I format these new drives as Reiserfs and after I copy the data, would I be able to have them 'just work' in unraid? That would be sweet, but I'm guessing it's not that simple... Man this is horrible and I really have no idea WTF has happened to my array, but at this point I need to start backing up these drives as I do not have a valid config Although it can be a specific production run of drives that has problems, a large number of drives with errors in the same system could also be an indication of a marginal power supply, or a marginal disk controller card, or motherboard, or even memory. The issue might have started when adding "one more" drive to a system putting it over the power supply limit. If you preclear a drive, it will be partitioned as unRAID expects. If you then type this following command, it will create a reiserfs file system. mkreiserfs /dev/sdX1 (note the '1' on the end, since we want to put the file system on the 1st partition. You'll need to use the correct drive letter in place of "X" too) There is a button on the disk-management page in unMENU that will create the file-system for you if you do not want to do it on the command line. You can then load files on the drive after mounting it. (unMENU can mount it, or SNAP can mount it, of you can mount it in another linux system) Once loaded with data, the ONLY way to bring it into the array without erasing the data on it is to set a new disk configuration. The side effect of that command it to immediately invalidate parity and when you start the array it will begin a new parity calculation based on the new disk configuration. Joe, I appreciate the detailed explanation. I'm completely unsure what is giving these 9 Seagate drives problems, but the remaining 12 drives are operating fine, and even rebuilt parity over night without problem. As for power supply, I have a 750watt Corsair p/s single rail in the Norco 4224. These 9 Seagate drives were all on different cards and mobo settings in the array. I thought that I narrowed the problem down to 2x backplanes in the Norco and replaced them, but they seem to be operating fine when these Seagates are pulled from the system. I replaced all the cables inside the system as well, thinking it was a cable issue, but again with these Seagates out of the system it seems to be fine. I'm totally at a loss as to what the problem could be and I'm at the point where I need to get these drives backup and then go from there... Regarding Resierfs - I've been formating these drives within a Debian environment with mkfs.reiserfs - I assume this will not partition the drives that unRAID expects?
Archived
This topic is now archived and is closed to further replies.