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.

bananaboye

Members
  • Joined

  • Last visited

Everything posted by bananaboye

  1. Hi, I upgraded from 7.0.1 to 7.3.3 and 7 of my 10 array disks were flagged "wrong" (DISK_WRONG). When I downgraded to 7.0.1 everything was back to normal. I did not run New Config, format, or re-assign anything, and the data is intact on 7.0.1. I would like to upgrade safely and want to understand why this happens. Diagnostics from both versions are attached (7.3.3 taken right after the upgrade, 7.0.1 after downgrading). Hardware: LSI/Broadcom SAS2116 (9201-16e) HBA, driver mpt3sas in both versions. All 15 devices show up with the same serials and sizes in both versions, no controller/cable errors in the syslog. What I see in the 7.3.3 syslog: md: import disk1: (sda) ST20000NM007D-3DJ103_ZVT5JQD8 size: 19531823104 md: import_slot: 1 wrong md: import_slot: 2 wrong md: import_slot: 4 wrong md: import_slot: 5 wrong md: import_slot: 6 wrong md: import_slot: 8 wrong md: import_slot: 9 wrong The disks marked wrong all report a data partition starting at sector 2048: emhttpd: online: ST20000NM007D-3DJ103_ZVT5JQD8 (sda) ... gpt start: 2048 size: 19531823104 emhttpd: online: ST10000NM0016-1TT101_ZA28V9NB (sdj) ... gpt start: 2048 size: 9766434816 (same for WD60EFRX, 3x ST4000NE0025, disk2) The disks that are accepted (parity, disk3, disk7, disk10) have a partition starting at sector 64: emhttpd: online: ST20000NM007D-3DJ103_ZVT5KC0A (sde) ... gpt start: 64 size: 19531825100 On 7.0.1 all of these are imported with start 64 and the stored size, for example: mdcmd (2): import 1 sdb 64 19531825100 0 ST20000NM007D-3DJ103_ZVT5JQD8 md: import disk1: (sdb) ... size: 19531825100 So the stored size for disk1 is 19531825100, but 7.3.3 sees 19531823104 and calls the slot wrong. Same pattern on the other six. Questions: 1. Is this a known change in how 7.3.x validates the partition start/size of array disks? Is it expected? 2. What is the supported way to upgrade to 7.3.x with these disks without losing data or parity? For example, is there a setting, or do the disks need to be rebuilt one at a time? 3. Is there anything I should check or back up before trying again? Thanks! 7-0-1.zip 7-3-3.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.