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.

djhavor

Members
  • Joined

  • Last visited

  1. Just wanted to say the rebuild went off OK and all data was present on the rebuilt disks. Thanks to Jorge for all the help! Marked as solved.
  2. Will do - thanks so much! I'll report back in a day or two when it's done.
  3. Thanks, Jorge. Array now started (not in maintenance mode). Diags attached. The array now shows the correct total size (ie the 'missing' 36TB is back!). tower-diagnostics-20240403-2251.zip
  4. Ah, my mistake. Sorry about that. Will be more careful with your instructions. I've now run the above commands and as expected they revealed errors which were fixed with -L.
  5. Thanks, Jorge. That's now done on both disks (using the sdc1 -and sdd1 mount points). The GUI option for xfsrepair was not available so I used the commandline. Both disks reported errors so i reran with -L. What should I do next
  6. Thanks, Jorge. So shall I stop the array (it is currently started with the data rebuild paused) and restart in maintenance mode so I can do a filesystem check, using: xfs_repair -v /dev/mdX ?
  7. Hoping against hope that I'm not screwed here... The background to the current crisis is that I swapped out an old 12TB drive for a new 18 TB one. When I booted the server back up, one of the existing 18TB drives was showing as disabled, even though nothing had changed on this. This was likely caused by a cable issue which I fixed. I then commenced a data rebuild on both drives (the new 18TB drive which was replacing the old 12TB and the existing 18TB drive which was effectively replacing itself). All was going fine and the contents of both drives were being emulated. We then suffered a power cut in the house when the data rebuild was about 5% done. On rebooting, the two drives that were being rebuilt are now shown as 'unmountable: unsupported or no file system'. Strangely the data rebuild has restarted (from 0%) and the GUI was showing writes to those drives (even though they are presumably not mounted). The real kicker, though, is the array size has now shrunk by 36TB and the drives do not appear to be emulated anymore (ie the contents are not accessible by the network share). No errors are reported on any drives, including the two parity disks. Am I screwed or is there a way to recover any of this data? I still have the old 12TB drive I replaced which may have data on, but obviously not for the 18TB drive that was replacing itself. Diagnostics zip attached. Thanks! tower-diagnostics-20240403-1958.zip

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.