Jump to content

fitbrit

Members
  • Posts

    445
  • Joined

  • Last visited

Posts posted by fitbrit

  1. Recently a couple of 2TB drives started showing up as read-only. I decided to replace them with 3 and 4 TB drives, and then check the old drives and maybe preclear and add them back to the array if they are ok.

    Re-constructing a corrupted file-system onto a new disk will result in a new larger disk with an equally corrupted file-system.

     

    Your intention is great, but your method wrong.  Fix the file-system corruption first, then upgrade the disk.

     

    Thanks, JoeL. I am thinking that since:

    The drive is installed physically,

    The drive it replaces was about 98% full...

     

    That I should do it this way around:

    Build the data onto the new drive.

    Fix the filesystem.

     

    That way, I'll have a back up on the original drive of the files, in case fixing the filesytem results in some kind of disaster. What do you think? I am happy to take your advice and replace the original drive first if you think that would be a better and safer way to do things.

  2. Recently a couple of 2TB drives started showing up as read-only. I decided to replace them with 3 and 4 TB drives, and then check the old drives and maybe preclear and add them back to the array if they are ok. Today I replaced disk10, a Hitachi 2TB, with a Seagate 4 TB drive. My Parity drive is a 4 TB WD Black drive.

    The new Seagate drive was recognised immediately.

    On the Main page I try to check the box and start the array, to rebuild the data. However, instead of starting the process, unraid returns me to the same screen again with the array stopped ad infinitum. Is there anything I can do? Any clues as to what might be happening? Syslog attached.

    Is unraid rejecting the new disk because it possibly appears to be larger than the parity, for example? (It shows 4Tb for both).

    syslog-2013-05-31_part_1.txt

  3. Background

    I upgraded from 4.7 to 5rc3.

    I had some problems with being able to access the user shares, had to keep remapping them to drives etc.

    I decided to go back to 4.7 while trying to get answers here on what I may have done wrong.

    I copied over bzimage and bzroot.

     

    Restarted and suddenly all disks were redballed. Under devices, the disks are all in the correct places and are assigned the right slots. See attachment in next message.

    I deleted the shadow, password and smbpassword files from the flash/config folder, suspecting that these files from 5rc3 may be interfering with the ability of 4.7 to see the disks properly.

    No go.

    I tried copying the 5rc3 bzroot and bzimage files back, hoping to get a clean start again. That too showed all disks as missing.

    Finally, I went back to 4.7.

    I'm assuming that I just need to run an "initconfig - trust my parity" to get back to normal. However, I don't want to do it without getting the experts to give em the go-ahead.

     

    Thanks for any comments/suggestions.

     

     

    syslog.txt

  4. I'm migrating my current server with 20 data disks + parity + cache to a new Norco 4224 case.

    The PSU I've chosen is this:

    http://www.corsair.com/power-supply-units/professional-series-gold-power-supply-units/professional-series-gold-ax750-80-plus-gold-certified-fully-modular-power-supply.html

     

    It has 62A on a single +12V rail I'll be running two supermicro PCIex4 SAS port cards, plus 8 drives off the motherboard. Should this PSU have sufficient power for all drives and fans in a standard 4224?

    Thanks for any opinions/ recommendations.

  5.  

    Antec power supply or older/cheaper model by any chance?

     

    Peter

     

    Hi Peter,

    May I ask why you specifically asked about the Antec PSU. My current server PSU is an Antec 650W, and I've had a few problems with multiple simultaneous failed disks and other errors. I'm switching the whole server to new hardware shortly, including a better PSU, but I just wondered whether you'd encountered inherent problems with the Antecs.

     

    Sorry for threadjack, OP.

     

    There have been 2 or 3 others who have reported odd disk issues here that went away after replacing their Antec supply.

     

    Peter

     

    Thanks for the information. I'll relegate my Antec to HTPC use eventually, where no real data is actually stored.

  6.  

    Antec power supply or older/cheaper model by any chance?

     

    Peter

     

    Hi Peter,

    May I ask why you specifically asked about the Antec PSU. My current server PSU is an Antec 650W, and I've had a few problems with multiple simultaneous failed disks and other errors. I'm switching the whole server to new hardware shortly, including a better PSU, but I just wondered whether you'd encountered inherent problems with the Antecs.

     

    Sorry for threadjack, OP.

  7. I just replaced the failed disk too. After the rebuild, I got this in the main window:

     

    (Last checked on 2/15/2012 10:31:32 AM, finding 7621830 errors.)

    Unmenu says: Parity updated  7621830  times to address sync errors.

    Should I be worried? Is my (greenballed) array protected now, at least? I'm prepared to have lost some data from before; it's from here on out that I'm concerned.

     

     

    None of the drives showed any errors during the rebuild. Should I be worried. Log file attached. I have a lot of duplicate files, notifications of which have been removed from the end of the syslog..

    syslog.txt

  8. Here's mine. Anything I should worry about?

     

    ============================================================================

    S.M.A.R.T. error count differences detected after pre-clear

    note, some 'raw' values may change, but not be an indication of a problem

    54c54

    <   1 Raw_Read_Error_Rate         0x002f   200   188051    Pre-fail   Always       -       16

    ---

    >   1 Raw_Read_Error_Rate         0x002f   200   188051    Pre-fail   Always       -       27

    ============================================================================

  9. Thanks, Joe. Your script is going to be a life saver for me in the near future. For now, my Medisonic 4-bay Pro Box seems to be dead! :( None of the drives are recognised. I tried clearing two drives the old way:

     

    Everything was going great with one drive (probably because your script had got through ~50% of it already). The other drive ended up showing as "Not installed". This was the one that was giving me problems with the script based clearing too - as you predicted because they're really doing the same thing. Then, the Pro Box stopped working and I had to restore my array with 13 data disks and rebuild parity again with the newly cleared disk missing. Anyway, I have a few 750GB drives to upgrade to 1 TB or 1.5 TB soon, so I will use your script to do so. Cheers!

×
×
  • Create New...