mbryanr

Can you continue to run the array? Sure. But I wouldn't write to it at a minimum before replacing the drive. If you get another write failure... You will lose data. Sent from my SAMSUNG-SGH-I897 using Tapatalk 2

1463 pending sectors. Sent from my SAMSUNG-SGH-I897 using Tapatalk 2

Can't you format to FAT with the HP Format tool?

I can get the test email to work..most times, but other than that I haven't had an email sent. Here is the link to the inital report: <p1lot> http://lime-technology.com/forum/index.php?topic=12698.msg188644#msg188644

Something with the error message you got when attempting to rebuild onto the 3TB... I would run pre clear on that drive. Sent from my SAMSUNG-SGH-I897 using Tapatalk 2

One other user and myself reported the issue in the SF RC3 thread, but didn't know why it didn't send the email. Sent from my SAMSUNG-SGH-I897 using Tapatalk 2

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

Thanks Joe. I usually use my search skills to find answers. Tough to do from the phone. Sent from my SAMSUNG-SGH-I897 using Tapatalk 2

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

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

You will have to put the 3TB drive back in, then add the 2TB. But not assign the 2TB Sent from my SAMSUNG-SGH-I897 using Tapatalk 2

197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 All good on the 2TB as far as SMART goes.

Believe you can run reiserfs --check...it will have to be unmounted anyways per the link I provided.

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.

I edited my reply. Plug in the 2TB, not add it to the array <don't want to mess up the current parity>..and get the smart report.

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.

http://www.bitfenix.com/global/en/products/chassis/prodigy/ IIRC, Raj was looking for a small case with handles.

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.>

Re: tvheadend...might want to look through this thread and plugin http://lime-technology.com/forum/index.php?topic=20782.0

The main question is the Broadcom NIC. Tom provided a broadcom.ko file for another user using a BCMBCM57788 nic <yours is the 57781>...and may have already rolled it into the unRAID kernel. http://lime-technology.com/forum/index.php?topic=20998.msg187007#msg187007 I would email Tom with your question regarding the NIC.

Do you still have the 2TB drive? Sent from my SAMSUNG-SGH-I897 using Tapatalk 2

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

Why haven't you tried rc6? Sent from my SAMSUNG-SGH-I897 using Tapatalk 2

If you are running v5 and Simple Features, there is a simple profile IIRC, unMENU also provides much of this info. Last resort is to look at the syslog to get some of the basic <driver> info, but not the specific motherboard. Or...just pull the side cover off your case.

Agreed, although there can be other causes. Looking through the above syslog, a parity check was started. Same situation I had. Eventually the GUI returns. I was impatient and attempted a emhttp restart only to get the same segfault as expected. http://lime-technology.com/forum/index.php?topic=19560.msg188745#msg188745 I did a full <clean> powerdown, restart and everything was back to normal. I restarted my monthly parity check...and just let it run until it was complete.