Jump to content

HAMANY

Members
  • Posts

    61
  • Joined

  • Last visited

Posts posted by HAMANY

  1. 5 minutes ago, JorgeB said:
    Oct 10 23:22:19 Tower kernel: ata10: reset failed, giving up
    Oct 10 23:22:19 Tower kernel: ata10.00: disabled

    Disk9 dropped offline again, did you replace both cables?

     

    Yes I did. Let me replace the whole SATA power cables and try again. I'm using StarTech SATA power splitter

    Thank you for your response. If you've any other suggestions for the SATA and power cables, please let me know.

  2. Hi all,

     

    It started with Disk 9 suddenly getting "UDMA CRC Error Count" and it got disabled. I changed the sata cable/port and rebuilt the array. After few hours Disk 7 got disabled because of read errors, and Disk 8 had also 300k+ read errors but wasn't disabled.

     

    I think there is something wrong with my setup, as I'm getting a lot of UDMA CRC Errors on different drives from time to time. I started losing believe on it. 

     

    I've 14 drives connected to:

    - Motherboard 6x Sata ports

    - 1x SAS card 2 ports to 8 Sata 

    - 1x Sata card with 2 Sata ports

     

    Based on your experience, what is your recommended next action?

    Thank you.

     

    tower-diagnostics-20221009-1751.zip

  3. On 11/20/2020 at 4:11 PM, HAMANY said:

    Hi,

    Any file downloaded through ruTorrent docker gets written in my storage with read-only permission 0755, although the $profileMask is already 0777 in (config.php).

    Any idea what is wrong?

    Fixed by changing the PUID and PGID in the docker settings to 1000 for both.

     

    Now looking for a way to stop the docker from creating the 3 folders (completed, incoming, watched) after every restart.

  4. 10 hours ago, JorgeB said:

    Flash drive is still dropping offline:

     

    
    ct 21 00:40:57 Tower kernel: usb 1-12: reset high-speed USB device number 2 using xhci_hcd
    Oct 21 00:40:57 Tower kernel: usb 1-12: device firmware changed
    Oct 21 00:40:57 Tower kernel: usb 1-12: USB disconnect, device number 2
    Oct 21 00:40:57 Tower kernel: print_req_error: I/O error, dev sda, sector 20088
    Oct 21 00:40:57 Tower kernel: Buffer I/O error on dev sda1, logical block 18040, lost async page write
    Oct 21 00:40:57 Tower kernel: print_req_error: I/O error, dev sda, sector 42090
    Oct 21 00:40:57 Tower kernel: Buffer I/O error on dev sda1, logical block 40042, lost async page write

     

     

    It seems that my flash drive is died. I got a new USB and I have a recent flash drive backup from CA Backup.

    What is the best why to start?

  5. 29 minutes ago, Squid said:

    When you do that, you should try the flash in another port, ideally USB2.  It dropped offline yesterday, and is probably the root of your problem.

    I've moved the USB to another port and started the server again.

     

    I've tried to resume the preclear for both drives. One of them worked and the other didn't.

    Is there anyway to make sure that the second drive is really "precleared" ?

     

    image.png.ccd31314576574b2104bc6aad4956716.png

     

    Thanks a lot.

  6. Hi,

     

    I started preclear for 2 new 8TB drives yesterday. The pre-read is done, and the clearing was on 50% last time I checked.

    Now when I access Unraid GUI I get the top menus with empty pages (Screenshot). Also the layout of the GUI was changed.

    The docker containers are working, the SMB shares are working but they are very slow and not usable.

    Tried different browsers in different PCs already. Disabled Adblock.

    Similar issue here

     

    My question is, before I try to reboot the server, is there anyway to check the stats of the pre-clearing through ssh? It should be completed after 1-2 hours if it didn't stop already. Diags are attached.

     

    Thank you.

     

    Unraid Version: 6.8.3

    CPU: AMD Ryzen 7 2700X

    Mobo: MSI X470 GAMING PLUS (MS-7B79)

    Memory: 16 GiB DDR4

     

    tower-diagnostics-20201020-1709.zip

  7. 4 hours ago, itimpi said:

    This does not look too good:

    While reallocated sectors are not necessarily a problem as long as the numbers stays constant anything other that a small number is often a good indication that the drive's health may be suspect.  You might want to run an extended SMART test on the drive to see how that goes.

     

    3 hours ago, johnnie.black said:

    It passed the short test, you should run a long one, but if Seatools passed it should also pass, it did fail a long test before, so there were issues before.

     

    Thank you both for your reponse.

    I will re-run the extended SMART and SeaTools again just to make sure.

     

    The drive is still under warranty, but I can't create an RMA without the SeaTools log showing the problem.

  8. On 6/1/2020 at 1:18 PM, johnnie.black said:

    That looks more like a power/connection issue, swap/replace cables and try again.

    Thank you Johnnie!

    The drives are now more stable after changing one of the power cables (4pins to SATA).

     

    However, I''m getting read and SMART errors in one of the 8TB Seagate drives (Disk 10 - sdi)

    I did a full scan using SeaTools but it didn't report any errors! Also it passes the SMART extended self-test.

    Could it be a connection issue also?

     

    The diagnostics file is attached. 

    Appreciate your support.

     

    Thank you.

    tower-diagnostics-20200706-0948.zip

  9. Just now, johnnie.black said:

    You can set up a syslog server, though that's used more for troubleshooting when the server keeps crashing or similar, for this kind of problem you just need to download the diagnostics before rebooting.

    Noted.

     

    The server is up and my files looks fine.

    Should I assign the 2 disks again and start rebuilding?

  10. 31 minutes ago, johnnie.black said:

    You rebooted since the errors so we can't see what happened, for now I would recommend unassigning both disabled disks and starting the array, check that both emulated disk mount correctly and contents look OK.

     

    Thanks for the quick response. Will try this now.

    Edit: Done, the files looks fine.

     

    Is there anyway to prevent the logs from being removed with rebooting, and keep them for few days?

  11. Actually 3 disks! 

     

    First it started with Parity 1 with (UDMA CRC error count)

    I changed the SATA cable and connected it to another SATA port in the motherboard, and started rebuilding.

    While rebuilding, Disk 2 got disabled with +2000 IO errors. Rebuilding was not interrupted, I think because I have 2 Parities.

    Rebuilding completed, Parity 1 disk became green again. Disk 2 has red ball.

    After few hours, Disk 3 got disabled.

     

    Disk 2 - ST8000DM004-2CX188_WCT0M8D4 (sdm) (errors 2)
    Disk 3 - ST8000DM004-2CX188_WG8011AG (sdl) (errors 2048)

     

    Parity 1 is connected like this: motherborad -> 5.25 to 3.5 converter -> HDD

    Disk 2 and Disk 3 are connected to LSI SAS HBA through the same port.

     

    What is the best way to proceed? I believe losing another disk would cause data lose.

    I have a spare pre-cleared disk but it has (60 Reported uncorrect), not sure how it got pre-cleared without issues.

     

    Please let me know if need more info. I know I did a mistake by shutting down the server before getting the logs, I wanted to check the connections and was too scared to lose another disk.

     

    Thanks.

     

     

    Unraid Version: 6.7.2

    CPU: AMD Ryzen 7 2700X

    Mobo: MSI X470 GAMING PLUS (MS-7B79)

    Memory: 16 GiB DDR4

     

    image.thumb.png.3a30391f8979c1879f48693d1a999ac5.png

     

    image.png.4333bdb6ce7c0981ea6e62893704f163.png

     

    tower-diagnostics-20200528-1303.zip

  12. Hi,

     

    I got the error (Unmountable: No file system) on Disk 2 the same time when Disk 1 was rebuilding. (After facing this issue)

    I waited for Disk 1 rebuild to finish, then restart the array/server, but the Unmountable message on Disk 2 still appears.

     

    I went through this documentation and executed this command (-nv) in maintenance mode and got the below response:

    Phase 1 - find and verify superblock...
            - block cache size set to 707800 entries
    Phase 2 - using internal log
            - zero log...
    zero_log: head block 654523 tail block 654519
    ALERT: The filesystem has valuable metadata changes in a log which is being
    ignored because the -n option was used.  Expect spurious inconsistencies
    which may be resolved by first mounting the filesystem to replay the log.
            - scan filesystem freespace and inode maps...
            - found root inode chunk
    Phase 3 - for each AG...
            - scan (but don't clear) agi unlinked lists...
            - process known inodes and perform inode discovery...
            - agno = 0
            - agno = 1
            - agno = 2
            - agno = 3
            - agno = 4
            - agno = 5
            - agno = 6
            - agno = 7
            - process newly discovered inodes...
    Phase 4 - check for duplicate blocks...
            - setting up duplicate extent list...
            - check for inodes claiming duplicate blocks...
            - agno = 0
            - agno = 3
            - agno = 6
            - agno = 1
            - agno = 2
            - agno = 4
            - agno = 7
            - agno = 5
    No modify flag set, skipping phase 5
    Phase 6 - check inode connectivity...
            - traversing filesystem ...
            - agno = 0
            - agno = 1
            - agno = 2
            - agno = 3
            - agno = 4
            - agno = 5
            - agno = 6
            - agno = 7
            - traversal finished ...
            - moving disconnected inodes to lost+found ...
    Phase 7 - verify link counts...
    Maximum metadata LSN (1:654601) is ahead of log (1:654523).
    Would format log to cycle 4.
    No modify flag set, skipping filesystem flush and exiting.
    
            XFS_REPAIR Summary    Wed Aug  7 21:00:27 2019
    
    Phase		Start		End		Duration
    Phase 1:	08/07 21:00:13	08/07 21:00:13
    Phase 2:	08/07 21:00:13	08/07 21:00:14	1 second
    Phase 3:	08/07 21:00:14	08/07 21:00:21	7 seconds
    Phase 4:	08/07 21:00:21	08/07 21:00:21
    Phase 5:	Skipped
    Phase 6:	08/07 21:00:21	08/07 21:00:27	6 seconds
    Phase 7:	08/07 21:00:27	08/07 21:00:27
    
    Total run time: 14 seconds

     

    I would like your suggestion in how I can proceed with fixing this issue?

    Please let me know if you require any further information.

    Thank you.

     

     

    Unraid Version: 6.7.2

    CPU: AMD Ryzen 7 2700X

    Mobo: MSI X470 GAMING PLUS (MS-7B79)

    Memory: 16 GiB DDR4

     

    image.thumb.png.555c1f194fdddd3542d908da88448eec.png

     

    tower-diagnostics-20190807-1747.zip tower-smart-20190807-2047.zip

  13. On 8/1/2019 at 9:10 PM, johnnie.black said:

    Best option is to use a file recovery tool, UFS explorer has been used with more or less success by others users before in similar situations.

    UFS managed to restore around 5.6TB of data, but unfortunately everything is corrupted.

    The good thing is that I know what has been deleted and I can re-download them gradually, in addition to the lessons learn.

     

×
×
  • Create New...