JJNBt

Members
  • Posts

    24
  • Joined

  • Last visited

Everything posted by JJNBt

  1. Ok, Ill get one as soon as can. Thank you for the help. Would I be able to labeled this post Solved?
  2. Here is the Self SMART Extended Test, for the drive frsttower-smart-20201228-1546.zip
  3. Sorry, that was not the Self SMART Extended Test. I will upload the once its done
  4. I ran the extended SMART test, so attached is an updated diag. What would be the things that are in the Diag that show something is wrong? frsttower-diagnostics-20201228-1336.zip
  5. Sorry for it being a little late. A little busy, also wanted to run a parity scan before I updated the Diags.
  6. Attached is a updated diagnostics, Thank you. frsttower-diagnostics-20201227-0905.zip
  7. Ok, I moved all of the SATA cables from the Marvell controllers, I also made a note of it on the case. I did grab one SMART from one of the disk that was disabled. In a few days I will add a new diags. Thank you for helping me CrystalDiskInfo_20201224181658.txt
  8. ran xfs repair. -L "Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... Metadata CRC error detected at 0x46af5d, xfs_finobt block 0x16d74d588/0x1000 btree block 3/33851608 is suspect, error -74 bad magic # 0 in inobt block 3/33851608 agi_freecount 55, counted 0 in ag 3 finobt - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 3 - agno = 2 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (1:16297) is ahead of log (1:2). Format log to cycle 4. done"
  9. So I have 2 cables with 3 (4 pin molex.) One cable was powering 1.5 bays. I believe that was creating this issue, so now 2 cables are using 2 (4 pin molex) I wont be using the third molex from now on. I am currently rebuilding the drive if anyone can read the diagnostics file and can give me further information such as if any drive is failing because of potential power issues or something non related, would be great. Thank you
  10. I just recently rebuild the array, it was working fine for a few weeks until last week we had a sudden black out I had to manually shut down the system luckily I decided to use and old UPS w/ new battery's and it worked fine for a few days. When the disk went down I had YouTube-DL, Krusader and Plex on. For some reason I was not able to shutdown Krusader before I had to force shutdown the system. I have two disk on the dashboard with error's thumbs down on the smart report. If you need further information I will reply your request asap. I also grabbed diagnostics before I shut down the computer and is attached. frsttower-diagnostics-20201220-1900.zip
  11. I was able to get to work. here are my settings that worked. eth0 eth1 - I set ipv4 address assignment to automatic eth2- the 10GBE I gave it an IP of x.x.2.21 while the one on my windows pc is set to x.x.2.20
  12. eth0 Bonding was ON turned it OFF. Change ip from x.x.x.20 to x.x.x.197 for eth1. Once I entered new ip to the new eth2 I notice on mac address it tells me that interface is shutdown (inactive.) So applied change. My server seems to still be active. Once I started the array I lost connection to unraid. just for fun I tried out x.x.x.197 ip, no luck
  13. When looking at backup of unraid(so glad I did it) I notice that bonding members of bond0: eth0,eth2 and my bonding mode is at active backup (1). So I am changing ip of eth2 to x.x.x.197 since eth0 is x.x.x.199. I also change bond0: (to just) eth0. so those changes made my connection time out.
  14. Ok so... When ever I set up my 10GBE, I seem to time out of my server. I connect to my system through eth1. after I did my parity process, I notice that I did not set my 10gbe with the ip x.x.x.20 I set up the other port that is on the motherboard with the ip x.x.x.20. So I turn off the parity once it was done and switched the information on the ports even the name eth2 clicked done and connection time out a few moments later. So I am stump can it be the 10gbe card which is a mellanox card is not supported or am I doing something wrong. A good thing I made a backup of my flash so most of my settings are ok hopefully i don't need to do another parity check.
  15. Yup that fix it. I didn't even see the other port. I have the unraid trail signup page running. Thank you @itimpi @trurl for all the help.
  16. Yes i do have another port available. I will connect the other port to the router. I won't be able to give an update until IPMI firmware updates. Unless i don't need to restart the motherboard
  17. Yes i am able to connect IPMI, I am currently trying to find out on what port it is under. So are you thinking that IPMI and unraid on conflicting on ports? Do you have any recommendations to finding the ports associated to ip?
  18. I am able to connect to the motherboard with its own IP address. while I am still unable to connect to unraid with the given ip.
  19. While restarting the machine I do notice that both ports lights are on. But right before the boot process ends both lights would go off.
  20. I am still getting for both eth0 and eth 1
  21. So after looking after the invalid gate I looked inside the network file and my router to see what static ip I gave it looks like I gave it the wrong Ip an the netmask was wrong as well so I correct that. now that the ip is correct I am still unable to connect.
  22. Ok, I check both ports on the card and two ports on the router and I check it again with a seperate cable. on the top of the photo its telling me that "error : Nexthop has invalid gateway" can this be an issue? https://photos.app.goo.gl/i7jfmqa1YHR1oQTG6
  23. I have not been able to to connect to the set up screen for unraid since it has been giving me self assign ips 169.xxx.xxx.xxx. I first thought it was my USB so I got a different one from the recommended hardware a sony storage media, the first one was the kingston traveler. I was still getting the same self assigned ip. A friend of mine told me that maybe its because my mobo nic has no support, So I bought a new nic that is in the recommended list an still its giving me self assign ips. I turn off bonding which then started giving me "ip address not set" I even turn off DHCP and gave it a static ip and I still getting "ip address not set." any help will be appreciated. -unraid ver 6.7.2- asrock EP2C602 G174P Dell Intel Pro/1000 PT PCI-E Dual Port Gigabit Ethernet Network Card here is diagnostics tower-diagnostics-20131216-1015.zip