vitovega

Members
  • Posts

    21
  • Joined

  • Last visited

Everything posted by vitovega

  1. Just to tie this up. I power-cycled both my Unifi Switches and was then able to access the Unraid GUI...and both Parity and Disk1 Rebuild was fully complete. So on to trouble shooting network issues! Thanks everyone for all your help
  2. So i thought that during rebuild i would be able to access my files but i noticed that the network shares weren't connected on my pc and plex was still telling me "files not found", so i rebooted my pc and plex server (I did nothing with the unRaid box) and oddly was then unable to access unraid over GUI or ssh (i tried on my android without luck as well). I was looking at the gui several different times today including right before i restarted my pc and it was about 51% of the way through rebuilding after 13+ hours. Do you have a suggestion for how to proceed from here? My current plan is to wait for at least enough time to pass for the array to be rebuilt (i figure tomorrow evening or Saturday) but then what should I do if I'm still unable to access the gui or ssh? hard reset? that's what I did before i had the disabled disks the first time.... I suppose i should plug a monitor into the server. fwiw it appears to be running fine with no error lights or beeping...
  3. Thankfully it shows a used and free space amt...thank you for the peace of mind
  4. fwiw, my running theory to the issue i had with the beeping is that the server was (forcefully) shut down during a accurate alert to a hot CPU2/AIO cooler/fan header not working and kept alerting on boot until it got to a certain part in the boot process and something could be reset. I dunno if this is crazy or stupid but it's the best i can come up with cause its not been without beep for 15 hours or so.
  5. oh fiddlesticks, I got the email this morning that you posted and it just showed "that's it..." and I didn't see the rest and went for it. How WOULD i have gone about checking that the emulated disk was still mounting? it seemed to have...and it's currently rebuilding parity/data-rebuild in process and its 9.8% done. What should i be on the look out for?
  6. Well i re-ran all the cables, reinstalled the fan wall, triple checked all the connections and it instantly beeped constantly the second i turned it on (it had been off for 4 days, so overheating seemed very unlikely). I tried a bunch of different headers for the AIO but eventually I just let it run as I was messing around in the IPMI (and cause it seemed to be booting effectively and didn't even feel warm). Well low and behold before unraid GUI could be accessed the beeping stopped and it's been running for over 2 hours without any further beeping. My server-related discord server suggested I update the BMC (and possibly BIOS). But personally feel I should rebuild the array first but I'm TERRIFIED. Can i just confirm with you that this are my steps? select no disk on both the Parity and Disk1 then Start the Array Stop array Reassign both disks to their previous slots start array again finally sleep easy? I simply can't select "no device" and start the array unless someone smarter than me tells me that's the correct move.
  7. YIKES! wow thanks for that! I'm glad i shut down my rig so fast when it was beeping, hopefully there was no permanent damage done. we'll find out tonight! Do you have any suggestions for what signs et al to look for if there WAS permanent damage? is it like memory issues where it's super hard to diagnose?
  8. Eep I didn't know that! What sort of catastrophic failure? Leaks? Unfortunately replacing it with anything but the same model will require me to remove the whole mobo and I'm not sure I'm ready to do that if it can be simply replaced... But thank you for the info! I might not even be able to replace with the same model without removing the mb. If it comes to that I'll just get a fan. Thanks once again for the advice
  9. unfortunately nothing like that. I checked the IPMI and cpu2 is overheating. so i'm going to try a different fan header and see if I can hear the pump going on the AIO cooler and if not replace? In order to recable the hard drives I had to remove the radiators from the fan wall and then the fan wall and think i knocked out the cpu header when I was reattaching...
  10. thanks! unfortunately my Unraid box has been making a constant, very loud beeping sound ever since i replaced the Sas cables. Something in the IPMI about cpu2 overheating...
  11. @JorgeB could you please provide a link or how-to to rebuild the parity and re-add disk1?
  12. Got the cables, but didn't have the time/energy to do it last night, def by the close of the weekend (Agh mother's day!). But something that was bothering me...If one of the CRC errors is old on those 2 drives....why did the drive get disabled?
  13. Thanks for that color! Is there a patirticular order i should rebuild Disk1 and re-sync the parity? or since they can be done simultaneously it doesn't matter (any benefit to doing them separately)? And finally, when i'm rerunning those SATA cables, do I need to keep track of which cable goes to which drive/port on the Card? Or will unraid sort that out without me trying to replicate the same runs...?
  14. Of course my apologies. I also forgot to mention that there was no useful info in the log that I could find. Simply 2 errors stating the disk was disabledser7en-diagnostics-20230510-1126.zipser7en-diagnostics-20230510-1126.zip
  15. I was unable to access my unRaid via WebUI or SSH so I needed to force a shut down (I know:(, should've tried to plug in a Keyboard/monitor). When it came back up, 2 of the drives were Disabled (1 of my 2 parities and Disk1). A year or so ago (it's a 3 year old rig without any other issues I can think of) I got an UDMA CRC error count on a drive that resolved when I opened the box and pushed in all the connectors. Each of the disabled drives again reads a UDMA CRC error but opening the box and pushing in the connectors didn't magically bring them back this time. Upon closer inspection it looks like the tension and heat maybe stretched the blue sheathing of the SATA cables and is exposing some metal underneath. I bought all new cables and they come in tomorrow. Seems like it's probably a good idea to replace the cables in any event, but i'd really like to get a better understanding of the problem to make sure I'm addressing the right one. Is there a way i can confirm this is the issue before doing it? Should I replace these drives while I'm rerunning the cables (I already have replacements)? Also advice on a work flow for what to do inside unRaid after I've replaced the SATA cables et al and, hopefully, the drives are .... reenabled? rediscovered? I'm sorry i'm not sure the nomenclature...obviously:)
  16. @diarnu I've had notifications on this thread for almost a year hoping for some nugget of information to help me solve this and my (probably foolish) patience has paid off! thank you so much for sharing the solution, worked perfectly. I experienced everything you referenced, including the issue in your addendum post. Thanks again
  17. again, I'm no expert, but maybe a permissions issue on the flash drive?
  18. I didn't know about the command @cinereus used but when I used it in my terminal i got an error: Linux 4.19.107-Unraid. root@Ser7en:~# sensors Error: File /etc/sensors.d/sensors.conf, line 2: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 4: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 6: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 8: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 12: Undeclared bus id referenced sensors_init: Can't parse bus name I dunno if this means it's corrupted but this is what's in that file it's complaining about: root@Ser7en:~# cat /etc/sensors.d/sensors.conf # sensors chip "nct7904-i2c-0-2d" ignore "temp2" chip "nct7904-i2c-0-2d" ignore "temp3" chip "nct7904-i2c-0-2d" ignore "fan2" chip "nct7904-i2c-0-2d" ignore "fan4" chip "coretemp-isa-0000" label "temp1" "CPU Temp" chip "nct7904-i2c-0-2d" label "temp1" "MB Temp" I'm not sure if this was created by the temperature plugin but I suspect it was...
  19. @bally12345 I literally just installed both the package and perl so i'm on the latest.
  20. same issue as well! Supermicro X9DRH-iTF w/ 2x Intel Xeon E5-2650v2. I have sensors populate when following the wiki's instructions but they all disappear when I click done. An uninstall/reinstall of the plugin did nothing, but a reboot brought it to the same state, all my sensors present but whenI click Done they all disappear and nothing is configured.