Hi guys

I was upgrading my parity drive and noticed some kernel errors in my syslog and wanted to know if I should be worried about anything.

Everything on the system is good but after browsing through my syslog I saw numerous error with super.dat file.

 

Also anything else that you guys see in my syslog thats worth mentioning would be much appreciated. I was adding a New 4TB parity and preclearing the old parity drive.

syslog.zip

So the New parity drive is working great and just did a parity check and found 0 errors. My old parity drive just finished getting precleared. Before I add my old parity to the array I want to make sure that anything in my syslog won't affect my array and disks. Does anybody know if my super.dat file will cause problems ounce I add another disk to the array? My super.dat was last modified on the 13 of October and I'm noticing errors in my syslog on that file..Much appreciated.

So the New parity drive is working great and just did a parity check and found 0 errors. My old parity drive just finished getting precleared. Before I add my old parity to the array I want to make sure that anything in my syslog won't affect my array and disks. Does anybody know if my super.dat file will cause problems ounce I add another disk to the array? My super.dat was last modified on the 13 of October and I'm noticing errors in my syslog on that file..Much appreciated.

Sounds like your flash drive may be corrupted and be in read-only mode.

 

Stop the unRAID server, check the flash drive in a window's PC via checkdsk, or scandisk.  Odds are the current parity status was not recorded properly if the file was not writable.

Sounds like your flash drive may be corrupted and be in read-only mode.

 

Stop the unRAID server, check the flash drive in a window's PC via checkdsk, or scandisk.  Odds are the current parity status was not recorded properly if the file was not writable.

 

Thanks Joe L. I ran checdsk on my usb stick and corrected all errors. its a 8gb stick. will it be ok to keep using this USB or should I get a new one?

Also is it better to have a SD card instead of a usb stick? Thanks for the help.

 

could plex media center be messing with my usb stick because I don't have a cache drive?

 

Unraid is back up now and The new parity is invalid because there was no writes to super.dat. I am going to do a parity sync and see if all goes well.. wish me luck..

So after my parity sync everything looks good but my syslog is showing some stuff I never seen before.

md: unRAID driver 2.1.4 installed

then driver removed multiple times..

 

REISERFS (device md1): found reiserfs format "3.6" with standard journal

Mserver kernel: REISERFS (device md1): using ordered data mode

Mserver kernel: reiserfs: using flush barriers

 

I did have errors on my usb stick and ran a checkdsk to fix errors. Now the usb is allowing me to write to it but the syslog is showing a lot more errors and it took a long time to mount and unmount the disks to the array. I have attached another syslog for anyone to help me out. Wan't to know what the best course of action would be before I add another disk to the array and keep my new 4tb parity disk. Thanks

syslog.after.parity.sync.zip

Which lines in the log indicate errors? I see none.

Which lines in the log indicate errors? I see none.

 

No errors. Great.

 

I did notice my drives took longer to mount and unmount, then saw this in the syslog multiple times.

md: unRAID driver removed

kernel: md: unRAID driver 2.1.4 installed

 

Also when the disk mounts I saw a lot of

REISERFS (device md1): using ordered data mode

Mserver kernel: reiserfs: using flush barriers. etc etc..

Lots of REISERFS..  Is this because my USB was not writing to the super.dat file?

 

Just want to make sure I can keep using my USB and if its O.K to add my other drive and trust the New parity. Checking the New parity drive right now..

I see only normal entries in the log.

I see only normal entries in the log.

 

Alright thanks dgaschk.. After the parity check I will add the new disk. After some time I'll upgrade to 5.0 stable..

So after adding the New Drive and Removing the old 1TB Drive from the array. Everything was going good on the rebuild but now I am showing a Red ball on my newly added drive with 300 errors.

 

I have attached my syslog and see attempt to access beyond end of device and kernel: sde1: rw=1, want=4294967296, limit=4294967295. I did run a preclear on the disk before adding it to the array and found 0 errors. Don't know if I should try to rebuild the drive again.

 

After randomly checking the files on the disk everything seems good. should I ignore the red ball and just restart the array or try to rebuild the disk again?

newsyslog.zip

Check for MB BIOS and SATA card firmware updates.

Check for MB BIOS and SATA card firmware updates.

 

Checked MB and Bios was updated to the latest firmware. No sata card firmware updates on the website.

 

The sata/PCIe  SY-PEX40039 ASM1061 Chipset (Asmedia 1061 SATA Host Controller)

Compliant with PCI-Express Specification V2.0 and Backward Compatible with PCI-Express 1.x

Compliance Serial ATA AHCI Spec. Rev. 1.3, Serial ATA Rev. 3.0

Supports Hot Plug and Hot Swap

Supports Communication Speeds of 6.0Gbps, 3.0Gbps, and 1.5Gbps

Supports 2 Ports Serial ATA

Supports Native Command Queue (NCQ)

Supports Port Multiplier

This card is bootable.

 

. I believe its connected to the parity drive and when it built the parity and validated it it found 0 errors.

Any other suggestions while I try to rebuild the drive again..?

Try moving the drive to or from the card.

Try moving the drive to or from the card.

 

Thanks will try that and see how it goes. I have added another HD. Would not enough juice from the power supply cause this to happen or just an issue with the sata card.

I'm using a Enermax EG 465P-ve. I have a total of 9 disks connected 4 are 7200 1tb and the rest are WD REDs..Also video card is Asus En6600 128mb.

The PSU is incapable of powering so many drives. 6-7 drives max on that PSU.

As per your recommendation I have tried to use different sata ports. I also have completely disconnected the PCIe to sata card and powered down one of the hard drives. So all connections are back to how I had my First install Back in January.

 

The only difference is I now have a 4TB Parity instead of the 3 TB parity. The rebuild still gave me errors but its the lowest Ive seen so far at about 100+.. My power supply has been working with all these drives before with no  problems. I think the 4TB that I added actually uses less power in standby and read/write then the other drive that was connected before. (1TBWDRE3) So Before I replace the power supply Do you guys think that there could be another issue causing the rebuild to have errors?

Thanks dgaschk and all others for the help in making this a great forum.

syslog.02.11.2013.zip

Another thing I noticed is this time the disk is red balled and the last 2 rebuilds my disk was orange balled. would that make a difference?

So After Replacing my power supply to a Corsair HX650 I still have errors on the hard drive during the rebuild . When I added the New Sata card it was connected to the parity drive and rebuilt the parity with no errors. I also verified the parity and found no errors. now when I am rebuilding my disk 4 it keeps giving me errors. Disk 4 is showing and playing the information so I think the hard drive and Pcie to Sata is ok but I could be wrong.

 

I have also tried disconnecting the pcie to sata card and only use the sata ports on the motherboard but that still gave me errors on disk 4. Disk 4 was a 1TB drive being replaced with a 3TB drive. What can you guys recommend next considering that I have had the Pcie to sata card build the parity drive with no problems? Replace sata cables.?Since changing the power supply and switching around the cables, I got the errors down from 300 to 26.   If you guys need a smart report on disk 4 let me know but I did a Quick smart report and found no errors. Also why would some rebuilds red ball and some rebuilds orange ball? Thanks

 

I also Noticed during the rebuild of disk 4, 2-3 disks show they are sleeping in the last 5-10 hours. Is that normal or are all disk active during the whole rebuild of a drive?

syslog.zip

Total size: 3 TB

Current position: 1.09 TB (36.3 %)

Estimated speed: 27.6 MB/sec

Estimated finish: 19 hours, 15 minutes

 

My Old Hard drive was a 1TB drive and I am rebuilding on a 3TB. Is the rebuild just adding zeros after the 1 TB of information?

Is that why I see some HD's going to sleep later in the Rebuild?

 

Anyone wan't to answer my last 3 posts? Should I create another thread since this has nothing to do with my USB anymore?

 

Another thing I noticed is this time the disk is red balled and the last 2 rebuilds my disk was orange balled. would that make a difference?

 

Red means a write to the drive failed and it has been taken out of service. Orange means the drive is rebuilding.

So After Replacing my power supply to a Corsair HX650 I still have errors on the hard drive during the rebuild . When I added the New Sata card it was connected to the parity drive and rebuilt the parity with no errors. I also verified the parity and found no errors. now when I am rebuilding my disk 4 it keeps giving me errors. Disk 4 is showing and playing the information so I think the hard drive and Pcie to Sata is ok but I could be wrong.

During the rebuild you are accessing an emulated version of disk4. Disk4 could be dead and the emulated disk4 would still be available. This does NOT indicate that disk4., et al., are OK.

I have also tried disconnecting the pcie to sata card and only use the sata ports on the motherboard but that still gave me errors on disk 4. Disk 4 was a 1TB drive being replaced with a 3TB drive. What can you guys recommend next considering that I have had the Pcie to sata card build the parity drive with no problems? Replace sata cables.?Since changing the power supply and switching around the cables, I got the errors down from 300 to 26.   If you guys need a smart report on disk 4 let me know but I did a Quick smart report and found no errors. Also why would some rebuilds red ball and some rebuilds orange ball? Thanks

 

I also Noticed during the rebuild of disk 4, 2-3 disks show they are sleeping in the last 5-10 hours. Is that normal or are all disk active during the whole rebuild of a drive?

This is normal.

Nov 18 16:40:33 Mserver kernel: attempt to access beyond end of device

Nov 18 16:40:33 Mserver kernel: sdi1: rw=1, want=4294967296, limit=4294967295 (Drive related)

 

 

Nov 18 16:40:33 Mserver kernel: md: md_do_sync: got signal, exit... (unRAID engine)

Nov 18 16:40:33 Mserver kernel: md: disk4 write error (Errors)

Nov 18 16:40:33 Mserver kernel: handle_stripe write error: 4294967728/2, count: 1 (Errors)

Nov 18 16:40:34 Mserver kernel: md: recovery thread sync completion status: -4 (unRAID engine)

Nov 18 16:40:34 Mserver kernel: md: recovery thread woken up ... (unRAID engine)

Nov 18 16:40:34 Mserver kernel: md: recovery thread has nothing to resync (unRAID engine)

 

Could bad cables be the cause of these errors? I have tried switching out 1 cable. All are 26AWG.

Everytime I try to rebuild my hard drive depending on how I have my cables connected I am seeing 20 50 or 200 errors in the rebuild. My parity drive is 4Tb and Disk4 is 3TB.

syslog.zip

Post a SMART report for disk4.

Post a SMART report for disk4.

 

Here is the smart report. Should I Change out my sata cables? Notice different amount of errors depending on the connections with cables or sata ports. Had the PCIe card disconnected and still got errors.

smart.txt

Report looks fine. Try new cables.