Jump to content

nsp24

Members
  • Posts

    42
  • Joined

  • Last visited

Posts posted by nsp24

  1. Ok so due to the errors and the possibility it was a cable or power issue I decided to swap the Motherboard as I had one I had taken out of my windows Machine I have also ordered a new PSU which is coming tomorrow  which will have plenty of Sata power connectors.

     

    Now I dont really know what I'm looking for but the Syslog seems a lot better to me the only thing I have not set up at the moment is the Cache drive as I need to read up on setting that up, I will attach the file and please let me know if there is any issues.

     

    Can I just say thank you for all the help!!

    tower-diagnostics-20211218-1629.zip

  2. Ok so the data rebuild has finished and its saying completed with no errors but on the main screan Parity 1 is saying 125 errors.

    looking at the sys log there are a load of read errors on disk0

    Also that annoying "lost interrupt" message appeared again.

     

    Dec 17 22:38:13 Tower kernel: ata2: lost interrupt (Status 0x50)

     

    Please advise what to do the server seam to be working fine and I'm moving files around again which is what I was trying to do when I started having problems.

     

    tower-diagnostics-20211218-0552.zip

  3. 20 minutes ago, trurl said:

    At the very end of syslog, don't know if they are continuing.

    Dec 17 17:32:57 Tower kernel: ata2: lost interrupt (Status 0x50)
    Dec 17 17:32:57 Tower kernel: ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    Dec 17 17:32:57 Tower kernel: ata2.01: failed command: READ DMA EXT
    Dec 17 17:32:57 Tower kernel: ata2.01: cmd 25/00:00:70:30:24/00:04:0b:00:00/f0 tag 0 dma 524288 in
    Dec 17 17:32:57 Tower kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    Dec 17 17:32:57 Tower kernel: ata2.01: status: { DRDY }
    Dec 17 17:32:57 Tower kernel: ata2: soft resetting link
    Dec 17 17:32:57 Tower kernel: ata2.00: configured for UDMA/133
    Dec 17 17:32:57 Tower kernel: ata2.01: configured for UDMA/133
    Dec 17 17:32:57 Tower kernel: ata2: EH complete
    

    This is parity

    Sorry not sure what you mean?

     

  4. 19 minutes ago, JorgeB said:

    Always good to make sure.

    Ok The system feels so much faster and has already done 8.4% in under 0ne hour where it had taken about 10 hours to do 9%, here is my log files can any experts have a look and see what you think? It all means nothing to me!!

  5. 35 minutes ago, JorgeB said:

    Try yet a different SATA cable, could also be a power issue.

    ok I have swapped cables around tested PSU with a tester all good, also removed and checked power cables and I have noticed the tinging noise has stopped and the rebuild has started again and is saying 10 hours instead of 7 days. is it worth checking syslog to see if the error is still there? 

  6. 4 minutes ago, JorgeB said:

    This is parity2, also de SATA controller is in IDE mode, and that's not ideal, but your board likely doesn't support AHCI.

    I will look at that thanks, parity 2 is a relatively new drive 6 months Max what do you suggest I do? this is all very complicated and frustrating!!

     

    Thanks Nick 

  7. Ok I have replaced every cable to all the drives and also put them in different ports both Parity drives go to the motherboard, im now getting 

     

    Tower kernel: ata6: lost interrupt (Status 0x50)
    Dec 17 15:53:01 Tower kernel: ata6.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    Dec 17 15:53:01 Tower kernel: ata6.01: failed command: READ DMA
    Dec 17 15:53:01 Tower kernel: ata6.01: cmd c8/00:20:00:00:00/00:00:00:00:00/f0 tag 0 dma 16384 in
    Dec 17 15:53:01 Tower kernel:         res 40/00:01:00:00:00/00:00:00:00:00/10 Emask 0x4 (timeout)
    Dec 17 15:53:01 Tower kernel: ata6.01: status: { DRDY }
    Dec 17 15:53:01 Tower kernel: ata6: soft resetting link
    Dec 17 15:53:01 Tower kernel: ata6.00: configured for UDMA/133
    Dec 17 15:53:01 Tower kernel: ata6.01: configured for UDMA/133

     

    how do I work out which drive this is ?

     

    tower-diagnostics-20211217-1607.zip

  8. 2 minutes ago, itimpi said:

    You are continually getting messages like :

    Dec 17 10:08:41 Tower kernel: ata5: lost interrupt (Status 0x50)
    Dec 17 10:08:41 Tower kernel: ata5.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    Dec 17 10:08:41 Tower kernel: ata5.01: failed command: READ DMA EXT
    Dec 17 10:08:41 Tower kernel: ata5.01: cmd 25/00:f8:18:26:93/00:03:13:00:00/f0 tag 0 dma 520192 in
    Dec 17 10:08:41 Tower kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    Dec 17 10:08:41 Tower kernel: ata5.01: status: { DRDY }
    Dec 17 10:08:41 Tower kernel: ata5: soft resetting link
    Dec 17 10:08:41 Tower kernel: ata5.00: configured for UDMA/133
    Dec 17 10:08:41 Tower kernel: ata5.01: configured for UDMA/33
    Dec 17 10:08:41 Tower kernel: ata5: EH complete

    in the syslog.  I believe ata5 is the parity disk.  This suggests either a connection problem (most likely) or the drive itself playing up.

    Ok thanks Should I pause the Rebuild and try a new cable? I have been getting the problem t6hat I cannot access the tower from my PC and I assume the server has crashed, could this be related to this?

  9. Hi, I am having a few issues with my server and have swapped a hard drive that had errors and the Rebuild speed has been 2.7MB/sec or less is this usual as its done 9.2% since last night and is reporting 7 days and 16 hours to complete? 

     

    Thanks Nick.

×
×
  • Create New...