mbryanr

Members
 View Profile  See their activity

  • Posts

    1294

  • Joined

  • Last visited

 Content Type 

Posts posted by mbryanr

    Samba

    in General Support (V5 and Older)

    Posted

    Have you entered new credentials/user in the Dune to access the shares? It may have been accessing the unRAID through 'root' which is no longer valid.

     

    Just enter a new user, no password required. Another user had this issue on Rc5.

     

    Sent from my SAMSUNG-SGH-I897 using Tapatalk 2

     

    write error?

    in General Support (V5 and Older)

    Posted

    First check the file system on the 3TB. Maybe you will get lucky.. And will be able to rebuild on the drive from parity.

     

    Second, if that doesn't work...

    If you can fix the file system on the 2TB drive, some, most, or all the files will be recovered.

    Edit: we're thinking the same.

    Sent from my SAMSUNG-SGH-I897 using Tapatalk 2

     

    write error?

    in General Support (V5 and Older)

    Posted

    What you could do is remove the 3TB drive. Assign the 2TB to the slot and run the new config utility. This will set a new disk configuration, and invalidate parity. I don't believe the current parity is good anyways. Then, you should be able to run the file system check.

     

    Sent from my SAMSUNG-SGH-I897 using Tapatalk 2

    write error?

    in General Support (V5 and Older)

    Posted

    If I haven't been clear...be very careful.

    I have never run into this specific problem, and don't want you to lose data.  If the 2TB drive is not recoverable, I'm not certain that you'll be able to rebuild onto a new drive from the current parity...but I don't want to lose the current parity.  It is the only hope if the 2TB is toast.

    write error?

    in General Support (V5 and Older)

    Posted

    SO...you have to keep the 3TB.

     

    You have a couple options <again, I've never run into this so...careful!>

     

    Do you have another port to plug the 2TB into <but not add it to the array>

    You could get a smart report that way....and possibly run reiserfs on that drive.

    write error?

    in General Support (V5 and Older)

    Posted

    The Smart report looks fine (RAW values = 0)

    197 Current_Pending_Sector  0x0032  200  200  000    Old_age  Always      -      0

    198 Offline_Uncorrectable  0x0030  100  253  000    Old_age  Offline      -      0

    199 UDMA_CRC_Error_Count    0x0032  200  200  000    Old_age  Always      -      0

     

    The problem is now that you have a parity reconstruction of the old 2TB drive with fs errors.  So if it tries to rebuild onto the 3TB, it is going to copy the fs error on the 3TB..hence why you get the "attempt to access beyond end of device" errors.

     

    Do you have a smart report from the 2TB drive before you removed it?

    Does the 2TB still have the files on it?

     

    If the 2TB does not indicate any smart errors...

     

    What I think should happen is this:

    1.  Re-install the 2TB drive in place of the 3TB

    2.  Run the filesystem check

    http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

    3.  Post either here or new thread with the results

    4.  Run commands per forum instructions...

     

    That would likely get 2TB operational again, assuming that there are no SMART issues (pending sectors etc)

     

    I believe that if you ran a filesystem fix on the 3TB, once you tried to rebuild it from parity it would create fs issues again.

    Although, there should be no issue or danger if you ran reiserfsck --check on the 3TB.

     

     

    <too many "thinks", "should" and "believes" for me to be 100% on these instructions.  Hopefully someone else will affirm or correct the above.>

     

     

    write error?

    in General Support (V5 and Older)

    Posted

    Post a smart report of disk5. I saw your posts earlier..didn't notice anything obvious except the write error...went to work, proceeding to forget about it. :-[

     

    Edit: Oh yeah...there was this:

    Jul 17 20:56:27 Tower kernel: attempt to access beyond end of device

    Jul 17 20:56:27 Tower kernel: sdf1: rw=1, want=4734320648, limit=4294967295

     

     

    File system check possibly? You rebuilt the new drive with this previous one... which likely had a fs error? Rebuilding wouldn't fix the problem, would copy the entire disk <including errors> and the fs would still need to be repaired.

     

    Edit2:  http://lime-technology.com/forum/index.php?topic=17358.msg156916#msg156916