srirams

Members
  • Posts

    11
  • Joined

  • Last visited

srirams's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I'd like to run an hour of parity check every week on Tuesday mornings. I've set the increment resume time as: 0 5 * * 2 and the pause time as: 0 6 * * 2. I am unsure what to use for the scheduled parity check. With 12tb drives, I'd need to start about two parity checks a year. If I use the same as the increment resume time (eg: 0 5 * * 2), will the parity check reset to 0% each time? Also, if I start a parity check using a script (parity.check nocorrect), is it considered a scheduled, manual or automatic check?
  2. Can you give me the output of: lsscsi -t -g
  3. I'm also affected by this bug. Even manually editing the smart-one.cfg so that the correct values appear in the web gui, those values are not applied to alerts... see screenshot below:
  4. Its a bug: Still present in 6.9.2....
  5. Yes... that's the page from the screenshot, unless I'm missing something... Yes, as shown in the screenshot I've set the thresholds at 65/70 for dev4, but still get an alert at 63 (for dev4).
  6. But this would change it for all the disks, correct? I only want to change the threshold for this one particular device...
  7. I've bought a sun oracle f80 flash accelerator which I'm using with the unassigned devices plugin, but I'm getting frequent "device overheated" alerts even though I've increased the warning thresholds.... Is there another setting I'm missing to disable these alerts for only this disk?
  8. Thanks, although if it's not going to be a problem, I think I will leave it be. Yes, sorry, I left out that I formatted with ext4 before adding to the array.
  9. I'm able to reproduce this using a new drive: New drive: root@trantor:~# gdisk -l /dev/sdv GPT fdisk (gdisk) version 1.0.5 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sdv: 23437770752 sectors, 10.9 TiB Model: WDC WD120EDAZ-11 Sector size (logical/physical): 512/4096 bytes Disk identifier (GUID): 9FD27D35-A843-4727-A701-4B422479775D Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 23437705182 Partitions will be aligned on 2048-sector boundaries Total free space is 4029 sectors (2.0 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 23437703167 10.9 TiB 0700 Elements Adding this to the array gives me a message about unsupported partition layout. Partitioning and formatting the disk like I used to do using: gdisk /dev/sdv o -> new gpt n -> new partition w -> write to disk using all defaults gives me: root@trantor:~# gdisk -l /dev/sdv GPT fdisk (gdisk) version 1.0.5 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sdv: 23437770752 sectors, 10.9 TiB Model: WDC WD120EDAZ-11 Sector size (logical/physical): 512/4096 bytes Disk identifier (GUID): 4116A97E-4ECA-4C4A-A0E2-5E2F6C568519 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 23437770718 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector) End (sector) Size Code Name 1 2048 23437770718 10.9 TiB 8300 Linux filesystem Now, when I try to add this disk to the array, all I get is a message about unsupported filesystem. I then format this in unraid, and the start sector is kept at 2048. root@trantor:~# gdisk -l /dev/sdv GPT fdisk (gdisk) version 1.0.5 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sdv: 23437770752 sectors, 10.9 TiB Model: WDC WD120EDAZ-11 Sector size (logical/physical): 512/4096 bytes Disk identifier (GUID): 4116A97E-4ECA-4C4A-A0E2-5E2F6C568519 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 23437770718 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector) End (sector) Size Code Name 1 2048 23437770718 10.9 TiB 8300 Linux filesystem root@trantor:~# xfs_info /dev/sdv1 meta-data=/dev/sdv1 isize=512 agcount=11, agsize=268435455 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=0 = reflink=1 data = bsize=4096 blocks=2929721083, imaxpct=5 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1 log =internal log bsize=4096 blocks=521728, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 trantor-diagnostics-20210327-1001.zip
  10. I'm building my array and converting all my disks to xfs. I'm adding the disks to the array, letting unraid format them (to XFS) and then copying data over (I have no parity yet). For the majority of the disks, the partition starts at sector 64, however for two disks the start sector is 2048 (I beleive these were previously ext4). Is this going to be a problem for when I add parity disks? root@tower:~# gdisk -l /dev/sdd GPT fdisk (gdisk) version 1.0.5 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sdd: 23437770752 sectors, 10.9 TiB Model: WDC WD120EMAZ-11 Sector size (logical/physical): 512/4096 bytes Disk identifier (GUID): 1334C70E-9F04-4727-9279-2C9036E38A27 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 23437770718 Partitions will be aligned on 64-sector boundaries Total free space is 30 sectors (15.0 KiB) Number Start (sector) End (sector) Size Code Name 1 64 23437770718 10.9 TiB 8300 root@tower:~# gdisk -l /dev/sdj GPT fdisk (gdisk) version 1.0.5 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sdj: 23437770752 sectors, 10.9 TiB Model: WDC WD120EDAZ-11 Sector size (logical/physical): 512/4096 bytes Disk identifier (GUID): C05405D7-6676-4EE3-9C3E-520742D748C9 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 23437770718 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector) End (sector) Size Code Name 1 2048 23437770718 10.9 TiB 8300 Linux filesystem
  11. This plugin allows the toggling of the led locator lights found in certain enclosures. Only tested on my Supermicro BPN-SAS2-846EL connected to a LSI 2008 HBA. Install: https://raw.githubusercontent.com/srirams/unraid-enclosure-led/master/plugin/enclosure-led.plg