Gico

Members
  • Posts

    288
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • Location
    Israel

Recent Profile Visitors

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

Gico's Achievements

Contributor

Contributor (5/14)

15

Reputation

1

Community Answers

  1. Admittedly having some OCD ("O" as in Order 😀) and being a control freak, the split level option is welcomed by my kind. Usually I don't rely on it, and I copy my media to disk shares, but in Kodi v20 a new artwork scraper plugin called Artwork Dump was introduced that regularly writes to the media folders, so this option is now important for me. Also in the bad scenario of losing a disk / data (been there), I would rather know what I lost, so prefer it to be alphabetically organized, rather than every time that I need to know if a specific media exists, I'll have to open a spreadsheet.
  2. Obviously that was it. Forgot about this restriction 🙂. Many thanks
  3. Diagnostics attached. I tried again to copy just now, December 1st 08:20 AM. MoviesShahar A-F subfolders are on disk18, G-Z are on disk19, and exactly starting with G folders is where all copies are failing. This issue occurs also in other folder (i.e. not MoviesShahar) that spans on disk18 and other disks, so definitely seems like disk related. juno-diagnostics-20231201-0824.zip
  4. I have a share (KodiMedia) that is spanned across multiple disks. This share is secured and only one user has write privilege to it. This user can write to this share with the exception of disk18: When the write is to disk18 I get a "disk is full" error. The disk has 578GB free. The share has "Manual" for split level and I'm writing to a subfolder, so I know which disk should be written to. When writing to a subfolder on a different disk there is no issue. This happens also when I make the share public. I ran "New Permission" for the share and for the disk and nothing changed. Write to the disk share always ok. Checked the xfs fs in maintenance mode and no issues reported. Any advice?
  5. I tested the memory sticks. 8 Passes of 4 sticks passed successfully without any error. 8 Passes of 4 the other 4 sticks (using the same slots as the previous 4) passed successfully without any error. 8 Passes of all the 8 sticks together passed successfully with 1 corrected ECC error. This might indicate that one of the slots being used by sticks 5-8 has an issue, but I doubt it. I don't know if this has nothing to do with the ECC errors, but the CPU fan is adjacent and actually touching one of the sticks. On my initial testing I in stalled the fan next to that stick, so the fan pushed a little the stick horizontally, and when doing the latter tests I installed the stick under the fan, so it might pushed the fan up a little, as seen in the screenshot.
  6. Didn't find anything relevant. The "Health Event Log" in the IPMI has similar errors in 2021. BIOS had only configuration of system event log, not the event log entries. Found "SMBIOS event log" which wasn't relevant.
  7. Hi. I'm testing the memory of a new server hardware and got these ECC errors this morning after about 60 hours of total interrupted memtest run. Total errors is zero so hardware overcame these issue. I didn't mean to run memtest this long, but had three power failures in my home, and the server is not connected to a UPS, so the memtest restarted and continued to test. One full test pass (~ 20 hours) was completed without any errors / ECC Errors. These errors began this morning, about 15 minutes after the third power failure. All logs (found on the memtest86 USB stick) beside the current one have no errors and no fixed ECC errors. Any recommendation? Should I start looking for a malfunctioned Dimm? Maybe run several passes (only) of these failed tests, this time with a UPS? Each pass would take about 4 hours. The hardware was bought used: MB: Supermicro HL12SSL-I CPU: EPYC 7302 + 4U fan Mem: 8X64GB Samsung PC4-2666V Registered ECC DDR4 PSU: Corsair HX1200i
  8. I'm having the same issue too and been struggling with it for an hour now: Restart, remove container without/with deleting the image, and still nothing, not even logs written to appdata/plex/Library/Application Support/Plex Media Server/Logs. Edit: Woke up this morning and the server is working ok.
  9. Just used it and worked like a charm. Thanks! To find source mdX (mine is disk9): lsblk | grep disk9 md9p1 9:9 0 10.9T 0 md /mnt/disk9 I knew that nothing writes to the array disk but tried the -no-remount-readonly switch and for some reason it didn't work and the partition was remounted as read only. ./xfs_undelete -t 2023-08-24..2023-08-25 -r 'video/*' -o /mnt/p2ppool/Temp/ /dev/md9p1 -no-remount-readonly /dev/md9p1 (/dev/md9p1) is currently mounted read-write. Trying to remount read-only. Remount successful. Starting recovery. Recovered file -> /mnt/p2ppool/Temp/2023-08-24-18-13_4297004664.matroska Recovered file -> /mnt/p2ppool/Temp/2023-08-24-18-14_4297004665.matroska Recovered file -> /mnt/p2ppool/Temp/2023-08-24-18-14_4297004666.matroska Recovered file -> /mnt/p2ppool/Temp/2023-08-24-18-14_4297004667.matroska Recovered file -> /mnt/p2ppool/Temp/2023-08-24-18-14_4297004668.matroska Recovered file -> /mnt/p2ppool/Temp/2023-08-24-18-14_4297004669.matroska Done. To remount the partition as read/write: root@Juno:/mnt/p2ppool/Temp/xfs_undelete-12.1# sudo mount -o remount,rw /dev/md9p1
  10. Stopped the array, unassigned disk5, started the array, stopped, reassigned disk5, started the array. Parity build began for disk1 & disk5, but I'm quite skeptic whether the base issue was found/solved.
  11. Diagnostics attached. One of my cache drives had CRC errors. Replaced it's data cable and it's ok now. How can I make disk5 available while rebuild is running? juno-diagnostics-20230809-0003.zip
  12. In main tab it seems it keeps reading the array disks and writing to disk1 (even after cancel). About 36 hours left.
  13. I'm sure about all errors happening after more than 6TB, but what does unraid writes to disk1 when it can't read from additional 2 disks? Is it possible that it writes incorrect data so invalidates the preclear?
  14. Data-rebuild can't be cancelled through the gui (not the first time it happens to me lately): It just continues. Any CLI command to do this?
  15. OK I'll do it when I'll get home. One comment: disk1 (6TB) was replaced by a *precleared* 16TB disk, and all errors happened after 6TB were rebuilt, so theoretically disk1 should already be valid.