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.

Smoketrain

Members
  • Joined

  • Last visited

  1. I have cloned one of the incorrect drives to the new 18TB drive and ran now I am going to do the next step from your instructions: What is read only mode, I see maintenance mode, but not read only mode?
  2. Thank you for your response, I am still learning unraid so I have some questions on how to proceed. The 10TB and 4TB drives will need to be fixed based on your last response. To test that process out, I can clone each drive and test the fix first. Can I clone the 10tb drive to an 18tb drive and test the fix there or do I need to clone a 10tb to a 10tb? I have not used DD before, is this the correct format? dd if=/dev/sdd of=/dev/sdb bs=64M conv=noerror the 10TB drive is listed as sdd, the 18TB drive is listed as sdb.
  3. ok and what about the 4tb one?
  4. root@Tower:~# gdisk /dev/sdc GPT fdisk (gdisk) version 1.0.10 Warning! Disk size is smaller than the main header indicates! Loading secondary header from the last sector of the disk! You should use 'v' to verify disk integrity, and perhaps options on the experts' menu to repair the disk. Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Warning! One or more CRCs don't match. You should repair the disk! Main header: OK Backup header: ERROR Main partition table: OK Backup partition table: ERROR Partition table scan: MBR: protective BSD: not present APM: not present GPT: damaged **************************************************************************** Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. **************************************************************************** Command (? for help):
  5. tower-diagnostics-20250328-1407.zip
  6. root@Tower:~# hdparm -N p19532873728 /dev/sdc /dev/sdc: setting max visible sectors to 19532873728 (permanent) max sectors = 19532873728/19532873728, HPA is disabled root@Tower:~# hdparm -N p7814037168 /dev/sdd /dev/sdd: setting max visible sectors to 7814037168 (permanent) max sectors = 7814037168/7814037168, HPA is disabled root@Tower:~# hdparm -N /dev/sdc /dev/sdc: max sectors = 19532873728/19532873728, HPA is disabled root@Tower:~# hdparm -N /dev/sdd /dev/sdd: max sectors = 7814037168/7814037168, HPA is disabled
  7. root@Tower:~# hdparm -N /dev/sdc /dev/sdc: max sectors = 19532871615/19532873728, HPA is enabled root@Tower:~# hdparm -N /dev/sdd /dev/sdd: max sectors = 7814035055/7814037168, HPA is enabled Sorry about that, so you want me to do the commands hdparm -N p19532873728 /dev/sdc and hdparm -N p7814037168 /dev/sdd Are you saying that doing these commands will remove the HPA partition and then by doing the other commands again, we will see if the HPA partition has been removed?
  8. Update: We did update the bios and we did find in the updated setting the place to turn off HPA (Bios to HDD). We verified that it is disabled. We then started up unraid and the 2 drives were still unmounted. Attached are the latest diagnostics. tower-diagnostics-20250327-2212.zip tower-diagnostics-20250327-2212.zip
  9. I was just checking the HPA link you gave us, that works fine, but the actual removal guide links for the HPA does not work anymore. Im just going to throw this out there but we have a Gigabybye GA-EX58-UD5P motherboard and we checked and we could not find an HPA setting in the bios, We are running original firmware. There is new firmware that we are upgrading to in order to see if that fixes things.
  10. no thats the whole issue, the two drives are not mountable even though I changed nothing with them
  11. What I did was I did a new config for the sever. I had read somewhere that when adding new drive you had to do that so thats why the server was able to start again.
  12. We found how to set up AHCI in the bios and we have turned that on and disabled IDE, have rebooted computer and have re-run diagnostics (attached) and we still have two drives that are unmountable (see screenshot). tower-diagnostics-20250326-1711.zip
  13. these are pluged directly onto the motherborad

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.