droopie

Members
  • Content Count

    87
  • Joined

  • Last visited

Community Reputation

0 Neutral

About droopie

  • Rank
    Newbie

Converted

  • Personal Text
    LSI 9211-8i P20 IT Mode Dell H310

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks I did see that but it said there are two ways to try and reanable a drive, reconstruction and trusting parity. Didn't know which would better fit my case. Also I have a question, if this drive fails to reconstruct, will data be lost? Or will it be possible to reconstruct on another drive to try again? So far I don't see any errors in unraid and the 199 count hasn't gone up but I'm just worried because I have really bad luck.
  2. And to do that I stop the array, unassigned the disk, and start the array then stop and reassign to do a construction? I just want to clarify so I don't accidentally tell unraid to think it's a new drive and wipe the data. Thanks in advance!
  3. i saw there are two ways that i could re-enable a disk but i am not sure which method based on my case i should use.
  4. i have 2 parity drives on a 2 to 1 splitter on the psu. same applies to disk 1-3 are on a 3 to 1 splitter but on the other psu cable. disk 1-2 are 8gb and when the disk got disabled, all drives had finished doing the job and was actually in the spin down state while only the two parity, and disks 1-2 being spun up. the newly added drives are only 1gb so i thought since they finished the parity check and when i check the system, all other drives but the two 8gb drives were spun up and thought i was in the clear for power. forgot to mention that disks 6 is also in a 2-1 splitter which is on the
  5. would you suspect the newly added disks 3 and 5 even tho they are 1tb each? i also have a ups which according to the unraid page for it, never goes over 200watts of my 600watt power supply. saying this because i would get a lot of errors on drives from powering them using the hard drive connectors from the psu so i recently switched almost all my disks except the first 6 to molex power.
  6. so i have two LSI 9211-8i P20 IT Mode Dell H310 cards in my system. parity 1-2 and disk 1-2 are using sas cable 1 on port a of pci card 1. since it was advised to replace the cable, i just disconnected it and am using an unused sata from the other pci card 2 port a. i started the array back up and got the log. also checked all the power down the line from the disk all the way to the psu too. unplugged, plugged in. server-diagnostics-20210122-1400.zip
  7. so i bring down the array, disconnect the sata, start the array, turn off the array, replace the sata and start the array? will it rebuild or will the new cable be detected? never had to do this before so i dont know the process to re-enable the drive besides a drive rebuild.
  8. i had to rebuild my drive array to shrink the array, then, i added a 2nd parity drive. i did a parity check and got no errors. i added 1 new drive, did a partial parity check to see if i had any issues with other drives because this is where i can see the issues. saw no issues around the first 250gb so i stopped the parity check. i then added another new drive, did a parity check again and saw no issues. i then went to do another parity check, and towards the very last 2 hours at 8am, disk 1 got disabled with errors. parity check said it had 0 errors and says it com
  9. When opening a browser page and visiting the address for my unraid server, either http://tower/ or http://192.168.1.100 it tries to display a page with this trailing address /index.html?_1604992752055 Notice it happens on any browser and any device. but only before reaching the signing in for the first time page. Once I delete that string, it takes me to the login page and after signing in and revisiting the initial address of the 2 above, it loads the page normally. The page is just white at /index.html?_1604992752055
  10. works thanks! i tried to google this a year ago when i first got unraid but wasnt really needed. just have to re map the shares on windows.
  11. almost all of my shares are public except for 1 share that is set to private with only a user read/write. i am able to enter credentials on solidexplorer using my android and it works fine but on windows i cant seem to login when it asks for a username and password.
  12. yea it finally kicked in and connected. is it possible to verify the vpn ip? just wanna have some extra peace of mind that my ip isnt leaked.
  13. i dont have that line but i changed it from this: cipher aes-128-cbc to this: client cipher aes-256-gcm ncp-disable
  14. stuck on a loop after update 2020-11-04 17:44:53 library versions: OpenSSL 1.1.1h 22 Sep 2020, LZO 2.10 2020-11-04 17:44:58,550 DEBG 'start-script' stdout output: 2020-11-04 17:44:58 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2020-11-04 17:44:58,550 DEBG 'start-script' stdout output: 2020-11-04 17:44:58 CRL: loaded 1 CRLs from file -----BEGIN X509 CRL----- MIICWDCCAUAwDQYJKoZIhvcNAQENBQAwgegxCzAJBgNVBAYTAlVTMQswCQYDVQQI EwJDQTETMBEGA1UEBxMKTG9zQW5nZWxlczEgMB4GA1UEChMXUHJpdmF0ZSBJbnRl cm5ldCBBY2Nlc3MxIDAeBgNVBAs