Jump to content

numpkin

Members
 View Profile  See their activity

  • Posts

    41

  • Joined

  • Last visited

 Content Type 

Posts posted by numpkin

    [SOLVED] Have I Been Hacked ??? Solved

    in General Support

    Posted · Edited by numpkin
    Added files and fix

    Hi All,

     

    Just found this message in "Fix Common Problems" plug-in..... settings

     

    For assistance with any of the errors / warnings displayed here, please post a new topic in General Support
    For assistance with the plugin, including requests for additional checks, false positives, etc please post HERE

     

    On Jul 19 there were 14 invalid login attempts. This could either be yourself attempting to login to your server (SSH / Telnet) with the wrong user or password, or you could be actively be the victim of hack attacks. A common cause of this would be placing your server within your routers DMZ, or improperly forwarding ports.

    This is a major issue and needs to be addressed IMMEDIATELY

    NOTE: Because this check is done against the logged entries in the syslog, the only way to clear it is to either increase the number of allowed invalid logins per day (if determined that it is not a hack attempt) or to reset your server. It is not recommended under any circumstance to ignore this error

     

    Thanks for reading.

    Any Help Please!!!

     

    Regards

    P.S how do I insert my syslog and diagnostics files in message??

     

    tower-03-diagnostics-20210730-1039.zip tower-03-syslog-20210730-0938.zip

     

     

    Panic update:

     

    I think I've found the problem, I'll call it "Human Error" 🙂

    I opened an old linux machine and ran 'Krusader' I was trying to connect to a 'windoze m/c' which had not got the correct settings to allow the linux to connect .....

     

    What a 'noob' sorry

     

    Regards

    numpkin

    (That's why I chose that user name)

     

     

    Parity Drive Disabled

    in General Support

    Posted

    Hi johnnie.black, tee-tee jorge

     

    Thanks for the reply

     

    I had the errors building up on the previous disk (UDMA) that's why I sent it back for replacement (under warranty)..

    When I got the replacement disk and after running 'Preclear' I installed the disk, unfortunately I forgot to change the 'sata' cable :-(

    When I realised my mistake I cancelled 'Pclear' shut down the server, changed the cable, then the 'parity build' started again, with the "1032 UDMA errors" ..

     

    Things have worked ok up to this morning, when I saw the message (via GUI) that the "PARITY DEVICE IS DISABLED" the question is "How do I go Forward"?

     

    regards

     

     

    Parity Drive Disabled

    in General Support

    Posted

    Hi All and thanks for reading,

     

    My original parity was a 6TB Seagate Ironwolf which started getting UDMA errors ......

    Sent the disk back to Seagate direct, which they replaced with an '8TB Pro Ironwolf Recertified Disk' ..... as they had no 6TB available for replacement.

     

    Checked this morning 29th Jan 2020 to find that this 'new' parity show on the GUI as "PARITY DEVICE IS DISABLED" and tha the drive has write errors..

    The disk log infomatation Shows:

     

    ErrorWarningSystemArray


    Jan 27 11:16:16 Tower-02 kernel: sd 2:0:1:0: [sdd] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
    Jan 27 11:16:16 Tower-02 kernel: sd 2:0:1:0: [sdd] 4096-byte physical blocks
    Jan 27 11:16:16 Tower-02 kernel: sd 2:0:1:0: [sdd] Write Protect is off
    Jan 27 11:16:16 Tower-02 kernel: sd 2:0:1:0: [sdd] Mode Sense: 7f 00 10 08
    Jan 27 11:16:16 Tower-02 kernel: sd 2:0:1:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA
    Jan 27 11:16:16 Tower-02 kernel: sdd: sdd1
    Jan 27 11:16:16 Tower-02 kernel: sd 2:0:1:0: [sdd] Attached SCSI disk
    Jan 27 11:16:33 Tower-02 emhttpd: ST8000NE0021-2EN112_ZA184WJY (sdd) 512 15628053168
    Jan 27 11:16:33 Tower-02 kernel: mdcmd (1): import 0 sdd 64 7814026532 0 ST8000NE0021-2EN112_ZA184WJY
    Jan 27 11:16:33 Tower-02 kernel: md: import disk0: (sdd) ST8000NE0021-2EN112_ZA184WJY size: 7814026532
    Jan 27 11:16:36 Tower-02 root: /usr/sbin/wsdd
    Jan 27 11:16:38 Tower-02 emhttpd: shcmd (25): /usr/local/sbin/set_ncq sdd 1
    Jan 27 11:16:38 Tower-02 root: set_ncq: setting sdd queue_depth to 1
    Jan 27 11:16:38 Tower-02 emhttpd: shcmd (26): echo 128 > /sys/block/sdd/queue/nr_requests
    Jan 27 11:25:43 Tower-02 emhttpd: shcmd (595): /usr/local/sbin/set_ncq sdd 1
    Jan 27 11:25:43 Tower-02 emhttpd: shcmd (596): echo 128 > /sys/block/sdd/queue/nr_requests
    Jan 27 11:26:04 Tower-02 root: /usr/sbin/wsdd
    Jan 27 19:18:10 Tower-02 emhttpd: shcmd (764): /usr/local/sbin/set_ncq sdd 1
    Jan 27 19:18:10 Tower-02 emhttpd: shcmd (765): echo 128 > /sys/block/sdd/queue/nr_requests
    Jan 27 21:00:09 Tower-02 emhttpd: shcmd (790): /usr/local/sbin/set_ncq sdd 1
    Jan 27 21:00:09 Tower-02 emhttpd: shcmd (791): echo 128 > /sys/block/sdd/queue/nr_requests
    Jan 27 21:00:10 Tower-02 emhttpd: shcmd (806): /usr/local/sbin/set_ncq sdd 1
    Jan 27 21:00:10 Tower-02 emhttpd: shcmd (807): echo 128 > /sys/block/sdd/queue/nr_requests
    Jan 27 23:39:05 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#3341 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
    Jan 27 23:39:05 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#3341 CDB: opcode=0x88 88 00 00 00 00 03 a3 81 2a 00 00 00 00 08 00 00
    Jan 27 23:39:05 Tower-02 kernel: print_req_error: I/O error, dev sdd, sector 15628052992
    Jan 28 15:35:34 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#612 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00
    Jan 28 15:35:34 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#612 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e0 00
    Jan 28 15:35:35 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#613 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
    Jan 28 15:35:35 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#613 Sense Key : 0x2 [current]
    Jan 28 15:35:35 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#613 ASC=0x4 ASCQ=0x0
    Jan 28 15:35:35 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#613 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
    Jan 28 15:35:35 Tower-02 kernel: print_req_error: I/O error, dev sdd, sector 0
    Jan 28 15:35:35 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#613 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
    Jan 28 15:35:35 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#613 Sense Key : 0x2 [current]
    Jan 28 15:35:35 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#613 ASC=0x4 ASCQ=0x0
    Jan 28 15:35:35 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#613 CDB: opcode=0x8a 8a 08 00 00 00 00 74 75 45 78 00 00 00 08 00 00
    Jan 28 15:35:35 Tower-02 kernel: print_req_error: I/O error, dev sdd, sector 1953842552
    Jan 29 07:19:53 Tower-02 emhttpd: shcmd (1042): /usr/local/sbin/set_ncq sdd 1
    Jan 29 07:19:53 Tower-02 emhttpd: shcmd (1043): echo 128 > /sys/block/sdd/queue/nr_requests
    Jan 29 07:20:51 Tower-02 emhttpd: shcmd (1058): /usr/local/sbin/set_ncq sdd 1
    Jan 29 07:20:51 Tower-02 emhttpd: shcmd (1059): echo 128 > /sys/block/sdd/queue/nr_requests

     

    I've attached Sys log and Dia files, any help please ...

     

    Regards ..

     

     

     

    tower-02-diagnostics-20200129-0719.zip tower-02-syslog-20200129-0711.zip

    CPU will not throttle down when idle (Help)

    in General Support

    Posted

    Hi all, thanks for your time ......

     

    I'm using an old 'AMD Phenom II X4 920' on a test build, when I run 'fix common problems' app I get the following error ....

     

    "CPU possibly will not throttle down frequency at idle".

     

    Suggested fix:

     

    "Your CPU is running constantly at 100% and will not throttle down when it's idle (to save heat / power). This is because there is currently no CPU Scaling Driver Installed. Seek assistance on the unRaid forums with this issue".

     

    So here I am ....... and thanks for reading.

     

    regards

    ---

    Numpkin

    tower-03-diagnostics-20181015-1455.zip

    tower-03-syslog-20181015-1456.zip

    (Solved) After replacing pci-e card now disks rearanged and Parity Disks show Disabled

    in General Support

    Posted

    Hi folks,

     

    Following on from my previous post:-

    Both the Parity drives are showing "Disabled" but the Data and cache disks are showing good see attached pics before and after ....

     

    Also the after pic say that "All Data on this disk will be erased when the array is started", when I start the array it does nothing ....

     

    Is it a matter of UN-attaching the disks, shutting down, reboot then re-attaching?

     

    also Diagnostics and syslog attached

     

    Regards

     

    ---

    Numpkin

     

     

     

     

     

    Screenshot from 2017-10-24 09-31-51-UR01.png

    31102017-re-assigned-Disks-screenshot-UR-01.png

    unraid_tower-01-diagnostics-20171030-1105.zip

    unraid_tower-01-syslog-20171030-1103.zip

    (Solved) Is It possible to swap out old pci-e 8 port card and replace with new one??

    in General Support

    Posted

    On 26/10/2017 at 10:27 PM, Frank1940 said:

    If you have the case open, give it a flip as soon as you push the power switch on the case.  If it starts and runs, you have a bad fan.  (A decade +/- a couple of years ago, I had a CPU cooler fan that won't start.  I measured its size and purchased a replacement that worked until I finally retired the computer.) 

    Hiya Frank,

     

    Thanks for the reply.

     

    See my latest post ......

    Regards

    ---

    numpkin

     

    (Solved) Is It possible to swap out old pci-e 8 port card and replace with new one??

    in General Support

    Posted · Edited by numpkin
    Wrong version No

    Again Hi Folks,

     

    Sorry not answered any replies for the last couple of days .....

     

    Working out the problem, now solved .... explanation:-

     

    I bought ready flashed Dell H310 (8 port) card from e-bay.

     

    Installed this card into what I calling my "ur-03 Test Server" the mb is an old Asus M3A78-T 8gig ram and a couple of 1 & 2 TB hdd's.

    As this board has built-in VGA, I placed the card into the PCIEX16, connected the cables booted up the machine and started unRaid V6.3.5

    On this assumption (rightly or wrongly) I purchased 2 more of these cards from the same seller ....

     

    So now I have 2 more Dell H310 cards to be installed into my "unRaid Working Servers"  I'll call them UR-01 & UR-02 (corny I know) which have installed 8-Port Pci-e card.

     

    First UR-02 Server:-

     

    GigaByte GA-Z77-D3H, Intel® Core™ i3-3220 CPU @ 3.30GHz, 16Gig ram installed with Dual Parity 4TB, a mixture of 6  HDD's 1TB, 2TB & 4TB.

     

    Removed existing card, which was installed in the PCIEX4 slot, replaced with Dell H310 in the same slot ........

    Switch on machine, fan on CPU fails to start (hence my 2nd post earlier)

    removed the card, replaced with card previous card boot machine , every back to normal ...... contacted seller, gave me some info to follow,

    including using electrical tape to block pins B5-B6 "Trick" on the card (but fiddly for me) managed to do this.

    Booted machine everything seems fine .. ran the GUI from another machine .... ALL disks attached to the new card "NOT FOUND" back again to the seller, asked if this card had been tried in ur-03 machine (remember that way back), removed card and re-slotted into ur-02, started ur-02, everything worked !!!! strange.

    did the same with with the 3 card which upto now hadn't been unpacked yet. when tried, this worked on ur-03 out of the package. mmmm

    Then suddenly after a lot of e-mails back and forth, head scratching "The Lightbulb Flashed".

     

    Whats the difference between the PCI-e slots on the motherboards.

     

    ALL cards tested in ur-03 machine where fitted into PCI-e 1 (Graphics Slot) card in Gigabyte MB was not, ok re-seat into PCI-e 1 ......

     

    started up the machine, everything seems as previous working, check the GUI, Wow ALL drives show up ...... So this machine fixed, hence the SOLVED in the title .......

     

    O nearly forgot ur-01, which upto now had not been opened:-

     

    GigaByte GC-970-A-DS3, AMD FX™-6300 Six-Core @ 3500 16Gig mem installed and as ur-02 Dual Parity 4TB, a mixture of 6  HDD's 1TB, 2TB & 4TB.

     

    This machine was boring, fitted the card into PCI-e1 slot, ("Without the B5/B6 Trick") booted the machine, everything working as normal .....

     

    Right if you got this far, well thanks......

     

    Regards all

    ---

    numpkin

    (Solved) Is It possible to swap out old pci-e 8 port card and replace with new one??

    in General Support

    Posted

    43 minutes ago, itimpi said:

    If the new cards report the disk serial numbers in the same way as the previous one then it is really easy as it is just a case of swapping the drives to the new cards. 

     

    However it is a good idea to have a screen shot of the Main page just in case the new cards report serial numbers differently so that you have to do a New Config and then re-assign the drives to the correct slots to get back to the previous working state.

    Hi itimpi,

     

    thanks for the quick reply ....

     

    Always best to check first with an experienced user, yea already got screen shots so no problem there .....

    i'll give it a whirl ......

     

    regards

    ---

    numpkin

     

    [V6.3.5] After running "Fix Comman Problems" app, now getting out of memory errors

    in General Support

    Posted · Edited by numpkin
    Missed Sig

    Hi All

     

    The Title says it all really, the wording I get is

     

    Out Of Memory (errors detected on your server)
    Your server has run out of memory, and processes (potentially required) are being killed off. You should post your diagnostics and ask for assistance on the unRaid forums


    Call Traces (found on your server)
    Your server has issued one or more call traces. This could be caused by a Kernel Issue, Bad Memory, etc. You should post your diagnostics and ask for assistance on the unRaid forums

     

    Diagnostic & System Log(s) Attached

    Thank You For Your Time

     

    regards

     

    numpkin .....

     

    unraid_tower-01-diagnostics-20170705-1959.zip

    unraid_tower-01-syslog-20170705-2000.zip

    [SOLVED] After partly upgrading to larger discs, now getting parity errors!!

    in General Support

    Posted

    Hi johnnie.black

     

    Thanks Started the array unchecked the box "write corrections to parity"

    check has started ...

     

    updated system & diagnostic attached ...

     

    After the check do I have to recheck the box again ?? to allow parity to be written to as normal?

     

    respect

    ---

    numpkin

     

    updated_unraid_tower-02-diagnostics-20170613-1321.zip

    updated_unraid_tower-02-syslog-20170613-1322.zip

    [SOLVED] After partly upgrading to larger discs, now getting parity errors!!

    in General Support

    Posted · Edited by numpkin
    missed info

    Hi All that read this.

     

    A few weeks ago I started replacing my drives to larger ones WD Red 4TB on 2 separate arrays  (ur-01 and ur-02) both have the same amount of drives (2 Parity, 6 Data)

     

    I ran preclear on every new disk I purchased on another machine which i use as a tester !!! (I'll call this ur-03) everything showed up ok!

     

    Process running in parallel :-

     

    1. Run preclear on ur-03

    2. Wait 24+ hours complete.

    3. After completion remove, then add next drive to be precleared

    4. Shutdown ur-01 remove first Parity Disk replace with new precleared disk

    5. Start the array, Parity check starts. (8-10Hrs) to finish.

    6. When next precleared drive finishes repeat step (3)

    7. Shutdown ur-02 remove first Parity Disk replace with new precleared disk

    8. See step (5)

    9. Did this sequence until the Parity disks had been replaced (4)

    10. Replaced smaller disks in the array with the larger ones (4TB)

    11. Giving me replacements of 2 Parity and 2 data Drives on each machine.

     

    When I replaced the Parity 02 disk on on machine ur-02, started the machine as usual Parity check started.

    When finished Parity01 showed errors.

     

    Checked Diagnostics file  which showed UDMA_CRC_error(s) of 134

     

    Rang the company where I bought the drives for a replacement Last Friday (9th June 2017), now awaiting for pickup tomorrow (14th June 2017),

    at the same time I bought another 4TB drive so that I could have a replace the one being sent back for checking or replacement (whatever the outcome I could

    add the drive to replace a smaller disk in either machine)

     

    The New disk arrived Saturday, did the same procedure with a new disk as normal.

    Late Sunday evening parity check started.

     

    This Morning 13th June 2017 checked the array, now Parity-02 is showing errors, in fact looking at the system log I've never seen so many errors

    Red Cross X Device is disabled, contents emulated.

     

    The said file(s) have been attached .... Hope someone can help thanks

     

    Sorry it's been a long winded post and thanks for sticking with it till the end ....

     

    respect

    ---

    numpkin

     

    unraid_tower-02-diagnostics-20170613-0952.zip

    unraid_tower-02-syslog-20170613-0955.zip

    [SOLVED] Parity Drive Say's Disabled check for assistance

    in General Support

    Posted

    11 hours ago, numpkin said:

    Hi johnnie.black,

     

    Doing the "Parity-Sync/Data-Rebuild in progress"  as I type, and thanks for the extra information ......

     

    Will report back after completion ...

     

    again many thanks ....

    ---

    eric

     

    Good Morning from the UK

     

    The parity check finished this morning and seems OK !! mm

    I'll watch for any more UDMA_CRC errors as you suggested ...

     

    Attached are the latest sys/dia files.

     

    thanks again

    ---

    eric

    unraid_tower-01-diagnostics-20170530-0803.zip

    unraid_tower-01-syslog-20170530-0832.zip

×
×
  • Create New...