Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Fefepaille

Members
  • Joined

  • Last visited

  1. Well. A week later, the new disk has implosed too. Assuming this come from cable, I got an extra 8TB on my array! From your experience, may it come from the power supply cable or the sata one? Thanks!
  2. Fingers crossed... Data-rebuild is in progress. After that, I'll do some checks on the "old" disk.
  3. Hi ! Thanks for your answer. So you're pretty sure that the LSI card is not faulty ? Where did you see that in the log ? Here ? Apr 22 00:24:21 Unraid kernel: sd 1:0:4:0: device_block, handle(0x000d) Apr 22 00:24:23 Unraid kernel: sd 1:0:4:0: device_unblock and setting to running, handle(0x000d) All drive where online and spining up. The PSU may handle it, assuming the big drop is when drives are spinning up ? Maybe it is caused by the electronic in drive itself... I ordered a new HD, just in case. Will see tomorrow with the new one. Thanks again.
  4. I'm not sure about that. It has probably been rebuild from udma crc error. Do you want me to remove it from the array and try a smart report ?
  5. Hello there, I often have disk errors, couple of minutes after the partity check starts. I usually resolve this by opening the case, moving cable, and lot of prayers ! Disks are plugged on a LSI cards. Do you think it is relied with HDs, cables, temperature, LSI card ? Is it possible to access to le LSI card log, temp, or something ? Thanks a lot... FP unraid-diagnostics-20250422-0113.zip
  6. Ok. Recovery with XFS seems to be pretty good, doin' it. Not all heroes wear capes. Thanks again.
  7. Well, UFS works pretty well. I got like.... 40GB of soup. (maybe old removed files) The rest (about 7TB) are ok, with a correct structure. I'll just "format" the drive after the backup, and the show must go on ! But I've got a last question : is the xfs file system strong enough ? Theses last 24h were painfull af, don't wan't to do this again ! Thank you again.
  8. Agreed, With the array and parity on, some of my files vanished. Do you have any tips with UFS Explorer ? => Doing a recovery. Praying for a pretty good result. Thanks again.
  9. Thanks for your quick answer ! Ok I'm trying it. If no good result, the parity can't help me ? Zeroing the disk and rebuilt it will result a data loss ? I never had very good results with recovery tools...
  10. Hi, There is an "Unmountable: Unsupported or no file system" disk in my array. (It's the disk 8, the second will be replaced tomorrow). It happened after a crash. Partitions are xfs. I tried the check_xfs command in maintenance mode, with or without the -L argument, but no way. I'm pretty scared, If someone have an idea... Should I zero the disk and rebuild it with the parity ? Thanks a lot. Here's the diag and the result of xfs_repair. _____________________________________________________ TLTR : xfs_repair didn't help me. Even the beta 7.0. Using UFS Explorer in another setup was the solution. (The only "trick" to do is to select the right system file format, xfs) Investigation still ongoing: percentage of dataloss. Pretty low I guess. xfs log.txt unraid-diagnostics-20240726-1819.zip
  11. (Solved) Hello, First of all, thank you for your work, containers, and videos. You are pimping my Unraid Server! I just installed shinobipro, successfully connected my camera, and it records when shinobi detects motion. I am trying to get notifications on email / discord, but something's wrong. I can receive the "no-motion" emails, so the config seems to be ok, but when something is detected, shinobi records this, without sending me an email. Is there a trick ? Thanks again. EDIT : I did it ! Reinstalling the whole container solved my issue. Maybe the region were too small for the detection.
  12. Hi, I had the same issue and I solved it by : - removing the deemix folder in appdata - editing container and updating the ARL Let few minutes to Deemix to be reinstalled, and I hope it will work again for you !

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.