DevXen

Awesome. I'll update tomorrow. Thank you.

i didn't see it in the release notes. but does this resolve the adaptec 7000 series card issues that .6 had. i had to roll back to .4 to fix it,. it was an issue with the then current version of the kernel i guess. but if it's not fixed then I guess i'm stuck on .4 still.

just saw this all over my logs. any idea how to fix it? Mar 2 15:59:52 MediaXen kernel: clocksource: timekeeping watchdog on CPU12: hpet wd-wd read-back delay of 108603ns Mar 2 15:59:52 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 102736ns, clock-skew test skipped! Mar 2 16:47:46 MediaXen flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 2 16:59:55 MediaXen kernel: clocksource: timekeeping watchdog on CPU18: hpet wd-wd read-back delay of 66279ns Mar 2 16:59:55 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 104761ns, clock-skew test skipped! Mar 2 17:05:44 MediaXen kernel: clocksource: timekeeping watchdog on CPU21: hpet wd-wd read-back delay of 62577ns Mar 2 17:05:44 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 102806ns, clock-skew test skipped! Mar 2 17:15:01 MediaXen kernel: clocksource: timekeeping watchdog on CPU6: hpet wd-wd read-back delay of 61530ns Mar 2 17:15:01 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 179911ns, clock-skew test skipped! Mar 2 17:24:10 MediaXen kernel: clocksource: timekeeping watchdog on CPU1: hpet wd-wd read-back delay of 56850ns Mar 2 17:24:10 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 178514ns, clock-skew test skipped! Mar 2 17:52:08 MediaXen kernel: clocksource: timekeeping watchdog on CPU20: hpet wd-wd read-back delay of 97707ns Mar 2 17:52:08 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 117263ns, clock-skew test skipped! Mar 2 17:59:45 MediaXen monitor: Stop running nchan processes Mar 2 19:02:57 MediaXen kernel: clocksource: timekeeping watchdog on CPU18: hpet wd-wd read-back delay of 106927ns Mar 2 19:02:57 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 106228ns, clock-skew test skipped!

2 issues... 1. Starting with my backup last week I started getting errors for directories it says aren't there. Event: Appdata Backup Subject: [AppdataBackup] Error! Description: Please check the backup log! Importance: alert '/mnt/disks/SSD/appdata/apache-php/logs' does NOT exist! Please check your mappings! Skipping it for now. --- '/mnt/disks/SSD/www' does NOT exist! Please check your mappings! Skipping it for now. --- '/dev/shfs' does NOT exist! Please check your mappings! Skipping it for now. --- '/mnt/disks/Docker_SSD/plex-utills/logs' does NOT exist! Please check your mappings! Skipping it for now. *Side note I've never had a docker_ssd mapping or drive* --- '/tmp/xteve' does NOT exist! Please check your mappings! Skipping it for now. ---- 2. Last week it took 4 and a half hours. Which is typical.. But that one last night took over 8 hours. Nothing has changed on my server in the last week. Event: Appdata Backup Subject: Appdata Backup Description: Backup done [4h, 29m]! Importance: normal The backup was successful and took 4h, 29m! --- Event: Appdata Backup Subject: Appdata Backup Description: Backup done [8h, 5m]! Importance: normal The backup was successful and took 8h, 5m!

I got a new server on eBay. Holds more drives and such and I would like to double check that I can move from Adaptec ASR-72405 RAID controller (in hba mode) To: AOC-S3008L-L8e HBA (in it mode) Without any problems. I've read a few posts of people that have started the adaptec in simple mode in accident and it erased the drives on boot..and others I've read they had to rebuild the data on each drive 1-2 at a time. Cause the raid card keeps the partition outside of the drive I guess. (Not adaptec specifically and I dunno if they had their cards in hba mode) I did replace my adaptec card when the current newest update had issues with the series 7 cards. (I rolled back the version.) But shen I got the new adaptec card I had to reassign each card as it assigned random different characters to the serial number of each drive.. So I just went to check if I can move from the adaptec in hba mode to this new card in IT mode. Also if anyone knows how to check it's in IT mode. That would be great too. Thank you, -Dev

How serious of an issue is this? It keeps happening with different CPU numbers? It keeps coming up in my logs online it said to very it to hpet which I did but it's still doing it. Jan 1 06:05:11 MediaXen kernel: clocksource: timekeeping watchdog on CPU3: hpet wd-wd read-back delay of 62158ns Jan 1 06:05:11 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 176069ns, clock-skew test skipped! Jan 1 08:14:43 MediaXen kernel: clocksource: timekeeping watchdog on CPU18: hpet wd-wd read-back delay of 69771ns Jan 1 08:14:43 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 118520ns, clock-skew test skipped! Jan 1 08:56:06 MediaXen kernel: clocksource: timekeeping watchdog on CPU17: hpet wd-wd read-back delay of 55873ns Jan 1 08:56:06 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 179422ns, clock-skew test skipped! Jan 1 10:14:01 MediaXen kernel: clocksource: timekeeping watchdog on CPU7: hpet wd-wd read-back delay of 65022ns Jan 1 10:14:01 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 121942ns, clock-skew test skipped!

Just tried that. Thank you.

hey I've been getting this in my syslog over and over. not sure how to fix it? root: ddns-updater: Could not download icon https://github.com/DiamondPrecisionComputing/unraid-templates/blob/main/templates/img/ddnsgopher.png?raw=true

Awesome..I found it. In thank you..10k filesize.. But it's there.

I'm not sure if this is an issue but I just did my first scheduled backup with this new plugin. And I have VM meta checked as yes. But I couldn't find that or the libvert backed up anywhere in the backups. But as it says VM meta I'd assume it's not backing up the libvert anymore and just the meta data it uses to create the VMs? Either way I want able to find any VM related backup files. But my flash backup was there.

This absolutely fixed my issue. was able to rebuild both drives that had been disabled. and all is good. any idea on how i can follow that to know when the driver in the kernel will be updated to fix this? so i know when i can upgrade my unraid again?

Here I just found this.... https://docs.unraid.net/unraid-os/manual/troubleshooting/#manually-upgrading-or-downgrading-an-unraid-release

Yeah I need to downgrade too. I was on 6.11.5 and upgraded to the latest I think 6.12.6. so I can't revert to 6.12.4 not sure how I would go About that.

My hba card went out (I think) so I got a new one. Put it in. Set it to HBA mode. All my drives said wrong. Looking it up online it said it said to do a new config and that should fix it. However it says on the parity drives all the data will be overwritten. One of my drives was in the middle of rebuilding so it needs to be rebuilt. Here's some History... I got a notification that 2 drives were disabled due to write errors. So I replaced them let them rebuild. 2 days later I woke up to an email saying 2 drives were disabled due to read errors, one being one that I replaced. - I ran chkdsk on Uber 2 I already replaced looking for bad sectors. Took like a week but not drives were fine.. So I decided to rebuild one of the disabled drives on it's self. Things were going well so I left. They got an email that another drive had gotten over 300 read errors.. like an hour later. So I shut down the server until I could replace my controller card. So now I've replaced it. All the drives said they were wrong when j tried to assign them. But looking it up online it said to do a new config. But now I'm assigning them it says all existing data on will be overwritten when array starts. I saw I can click at the bottom parity is valid.. will that stop it from being overwritten when I start it. and do I then stop it. Unassigned the disk that needs to be rebuilt then start the array then stop it then reassign. It. Then start the array to rebuild it? knowing it needs to rebuild and onto has partial data will that cause an issue when I start the array? thanks, -Dev

No. I tried with the first ones that had write errors and the smart tests stuck At 100% and would never finish. But the diagnostics have the smart info for each drive I saw so that's good. Here's a little back story... (Didn't put it here cause I already posted a different post about it. But here... On Sat I had 2 drives disabled for write errors. Then I swapped them out and rebuilt data separately on them. Took one out ran an extensive chkdsk looking for bad sectors. It didn't find any. The second one still has like 6 days to go on it's check but so far no errors. And then today I woke up to 2 drives disabled due to read errors. One brand New one I replaced on Sat and a different drive in the array. About 3 hours into the rebuild on one of the drives I got 2 more drives with read errors. So at that point I turned my server off. Thinking it's the hba controller card or the cables. But it would be strange for multiple cables die at the same time. They are really thick cables. Here's a pic.