ShadowLeague
-
Posts
42 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by ShadowLeague
-
-
After looking at the compatibility list and scouring the forums, and reddit, I haven't come across anyone talking about this motherboard. The reason why it caught my attention are the SAS3 ports and a good amount of PCIe ports. So, I'd like to make sure this board will work.
-
3 hours ago, trurl said:
Do you have any dockers that move files?
Yes. At one point, the containers moved files to a folder within 'media', but not anymore.
-
I'm usually moving stuff from my Windows laptop by doing a cut/paste in Windows Explorer
-
I'm experiencing the same for Version 6.9.2 2021-04-07
I have a `Downloads` folder set to use a cache pool. When I move stuff from it to a `Media` share, that `Media` folder is using the cache pool, too. The `Media` share is NOT configured to use any cache pool. -
I could, but there are dependencies that, frankly, I'm too lazy to address. But that would be the best way to address it, yes.
-
well that answers that question
I think I might be ok if I make the root `Media` share part of the cache pool as most of my reads/writes are going to the "high_access" folders. And I'll have mover empty the cache pool if it gets over a specified size. -
Hello!
Let's say I have a root share called `Media.` All of the contents (up to this point) are moved here; however, there are many folders in 'Media,' so no caching of any sort is enabled.
Within the 'Media' folder, I have two folders within that share that are written to on a daily basis, and can be accessed multiple times by several people. I was thinking of enabling caching for these two 'high access' folders, but I wasn't sure if a share within share would cause any issues when it comes to enabling caching. In summary, I'd like to confirm:
\Media [root share, no cache enabled, no change]\Media\high_acces1 [potential new share, enable caching ok?]
\Media\high_access2 [potential new share, enable caching ok?]
-
Great point; totally forgot about the 2TB max capacity
-
I'm considering building a backup system for my current unRAID setup. I've seen systems with 3GBps hardware; I thought about buying them since I think I could save some money vs 6 or 12GBps systems. Transfer speed wouldn't matter all that much since the backups would be a differential (what I added from last backup). Yes; the initial backup would be slow... In short, why else would I not want to go with a system that is 3Gbps for the drives?
-
On 3/14/2021 at 6:29 PM, craigr said:
Yeah, that is HBA IT only so you won't have to do a thing in software. Just plug-and-chug.
craigr
Just an FYI - I read the same thing... that I didn't have to update the firmware to P20. But, my drives weren't detected when I fired up unRAID. After updating the card to the P20 firmware, I was able to see the drives
-
17 hours ago, craigr said:
As long as the controller is HBA you shouldn't have to do anything with your configuration. Just physically relocated the drives and boot up. Are you connecting the external chassis via SAS?
craigr
Yup; with an LSI SAS9201-16e
-
I've outgrown my server and have bought an external chassis to house existing drives (and new ones down the road). I've purchased another controller that will be configured for JBOD mode. Are there any issues/concerns moving existing drives to a new controller? I think I need to ensure whatever drive # it was in the pool stays the same; same for the parity drives.
-
I mistakenly started the array and it looks like the drive contains some of the folders in their original folder. I also have a `lost+found` folder that appears to have valid data. might be a painful process, but I can comb through it. As a precaution, I'm moving the data off to another drive just in case this drive takes a dive. Thanks for the guidance.
-
Thanks - I had to use the -L option. I saw it did a ton of repairs (looking through webui), and some of it displays directory names I'd rather not share. Here's the jest of it. If you need the entire file, I'd be happy to share in a non-public manner. Now the disk is stating it's unmountable: no filesystem. I'm hesitant to mount and wipe it out without confirmation that is, in fact, the next step to hopefully recovering it.
Phase 1 - find and verify superblock... sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap ino pointer to 129 sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary ino pointer to 130 Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... Metadata CRC error detected at 0x438fd6, xfs_agf block 0x37fffffc9/0x200 Metadata CRC error detected at 0x463b36, xfs_agi block 0x37fffffca/0x200 bad uuid 9dc7ddda-8b5e-45b5-f447-b48db488263e for agi 7 reset bad agi for ag 7 Metadata CRC error detected at 0x438fd6, xfs_agf block 0x7ffffff9/0x200 Metadata CRC error detected at 0x438fd6, xfs_agf block 0x27fffffd9/0x200Metadata CRC error detected at 0x463b36, xfs_agi block 0x7ffffffa/0x200 Metadata CRC error detected at 0x438fd6, xfs_agf block 0x3ffffffc1/0x200Metadata CRC error detected at 0x463b36, xfs_agi block 0xfffffff2/0x200 Metadata CRC error detected at 0x438fd6, xfs_agf block 0x4ffffffb1/0x200bad uuid 9dc7ddda-8b5e-45b5-ba7e-0641b69b93c1 for agi 1 Metadata CRC error detected at 0x43c89d, xfs_bnobt block 0x37fffffd0/0x1000 Metadata CRC error detected at 0x463b36, xfs_agi block 0x47fffffba/0x200reset bad agi for ag 1 Metadata CRC error detected at 0x463b36, xfs_agi block 0x57fffffaa/0x200 btree block 7/1 is suspect, error -74 bad uuid 9dc7ddda-8b5e-45b5-5bc7-1412a64ff85a for agi 2 bad uuid 9dc7ddda-8b5e-45b5-2a55-c0dedb2cc954 for agi 11 invalid start block 454396897 in record 0 of bno btree block 7/1 bad uuid 9dc7ddda-8b5e-45b5-4980-1b9266bce1c5 for agi 9 reset bad agi for ag 11 reset bad agi for ag 2 Metadata CRC error detected at 0x463b36, xfs_agi block 0x27fffffda/0x200reset bad agi for ag 9 Metadata CRC error detected at 0x463b36, xfs_agi block 0x4ffffffb2/0x200 freeblk count 4 != flcount -1169734501 in ag 1 bad uuid 9dc7ddda-8b5e-45b5-fb22-ab9a32eddaba for agi 10 bad uuid 9dc7ddda-8b5e-45b5-94a2-91da728c7eda for agi 5 reset bad agi for ag 10 reset bad agi for ag 5 Metadata CRC error detected at 0x43c89d, xfs_bnobt block 0x80000000/0x1000 btree block 1/1 is suspect, error -74 Metadata CRC error detected at 0x43c89d, xfs_bnobt block 0x27fffffe0/0x1000Metadata CRC error detected at 0x43c89d, xfs_cntbt block 0x37fffffd8/0x1000bad magic # 0x9939ab0d in btbno block 1/1 Metadata CRC error detected at 0x43c89d, xfs_bnobt block 0x3ffffffc8/0x1000btree block 7/2 is suspect, error -74 invalid start block 2914046783 in record 0 of cnt btree block 7/2 btree block 5/1 is suspect, error -74 invalid start block 1535741318 in record 0 of bno btree block 5/1 btree block 8/1 is suspect, error -74 invalid start block 3322690393 in record 0 of bno btree block 8/1 agf_freeblks 2773520, counted 2773519 in ag 7 bad agbno 1385839744 for inobt root, agno 7 bad agbno 3414312916 for finobt root, agno 7 agi_count 810803484, counted 0 in ag 7 agi_freecount 2225055810, counted 0 in ag 7 agi_freecount 2225055810, counted 0 in ag 7 finobt Metadata CRC error detected at 0x43c89d, xfs_cntbt block 0x80000008/0x1000 btree block 1/2 is suspect, error -74 bad magic # 0xf0d1a620 in btcnt block 1/2 agf_freeblks 3174056389, counted 0 in ag 1 agf_longest 2571388690, counted 0 in ag 1 agf_btreeblks 1611498779, counted 0 in ag 1 Metadata CRC error detected at 0x43c89d, xfs_cntbt block 0x27fffffe8/0x1000 btree block 5/2 is suspect, error -74 invalid start block 1923816173 in record 0 of cnt btree block 5/2 Metadata CRC error detected at 0x43c89d, xfs_cntbt block 0x3ffffffd0/0x1000 btree block 8/2 is suspect, error -74 invalid start block 637827189 in record 0 of cnt btree block 8/2 agf_freeblks 15829760, counted 15829759 in ag 8 bad agbno 2383254389 for inobt root, agno 9 bad agbno 3968673061 for finobt root, agno 9 agi_count 3154604573, counted 0 in ag 9 agi_freecount 2703483900, counted 0 in ag 9 agi_freecount 2703483900, counted 0 in ag 9 finobt agf_freeblks 371708, counted 371707 in ag 5 bad agbno 1777622622 for inobt root, agno 5 Metadata CRC error detected at 0x46ad5d, xfs_inobt block 0x80000010/0x1000 btree block 1/3 is suspect, error -74 badly aligned inobt rec (starting inode = 3326860449) ir_freecount/free mismatch, inode chunk 1/1179376801, freecount 173 nfree 0 invalid inode count, inode chunk 1/1179376801, count 37 ninodes 24 bad agbno 2294816774 for finobt root, agno 1 agi_count 4128, counted 4101 in ag 1 agi_freecount 21, counted 193 in ag 1 agi_freecount 21, counted 0 in ag 1 finobt Metadata CRC error detected at 0x438fd6, xfs_agf block 0x1/0x200 Metadata CRC error detected at 0x463b36, xfs_agi block 0x2/0x200 bad uuid 9dc7ddda-8b5e-45b5-3477-a700a148ac9b for agi 0 reset bad agi for ag 0 freeblk count 6 != flcount 207153230 in ag 0 Metadata CRC error detected at 0x46ad5d, xfs_inobt block 0x100000008/0x1000 btree block 2/3 is suspect, error -74 badly aligned inobt rec (starting inode = 8475978649) bad starting inode # (8475978649 (0x2 0xf9352b99)) in inobt rec, skipping rec bad agbno 510119067 for finobt root, agno 2 agi_count 3968, counted 4043 in ag 2 agi_freecount 77, counted 87 in ag 2 agi_freecount 77, counted 0 in ag 2 finobt Metadata CRC error detected at 0x46ad5d, xfs_finobt block 0x28c9ab338/0x1000 btree block 5/26433132 is suspect, error -74 bad magic # 0x2dfffa98 in inobt block 5/26433132 agi_count 2119379929, counted 0 in ag 5 agi_freecount 4048445688, counted 0 in ag 5 agi_freecount 4048445688, counted 0 in ag 5 finobt Metadata CRC error detected at 0x43c89d, xfs_bnobt block 0x500c08a48/0x1000 btree block 10/1577299 is suspect, error -74 invalid start block 3546133177 in record 0 of bno btree block 10/1577299 bad agbno 3559777358 for inobt root, agno 11 bad agbno 1782342956 for finobt root, agno 11 agi_count 2822670932, counted 0 in ag 11 agi_freecount 319440009, counted 0 in ag 11 agi_freecount 319440009, counted 0 in ag 11 finobt Metadata CRC error detected at 0x43c89d, xfs_cntbt block 0x52bf639f8/0x1000 btree block 10/92194633 is suspect, error -74 invalid start block 2586548467 in record 0 of cnt btree block 10/92194633 agf_freeblks 31820914, counted 31820884 in ag 10 Metadata CRC error detected at 0x46ad5d, xfs_inobt block 0x4ffffffc8/0x1000 btree block 10/3 is suspect, error -74 badly aligned inobt rec (starting inode = 25420430994) bad starting inode # (25420430994 (0xa 0xeb2cfe92)) in inobt rec, skipping rec bad agbno 4252378456 for finobt root, agno 10 agi_count 4160, counted 4347 in ag 10 agi_freecount 15, counted 199 in ag 10 agi_freecount 15, counted 0 in ag 10 finobt Metadata CRC error detected at 0x43c89d, xfs_cntbt block 0x2018caee0/0x1000 btree block 4/3249632 is suspect, error -74 bad magic # 0x28be99cc in btcnt block 4/3249632 agf_freeblks 1072128, counted 0 in ag 4 agf_longest 106153, counted 0 in ag 4 agf_btreeblks 4, counted 2 in ag 4 Metadata CRC error detected at 0x43c89d, xfs_bnobt block 0x8/0x1000 btree block 0/1 is suspect, error -74 bad magic # 0x71dd9a7 in btbno block 0/1 Metadata CRC error detected at 0x43c89d, xfs_cntbt block 0x10/0x1000 btree block 0/2 is suspect, error -74 bad magic # 0xac3fbda0 in btcnt block 0/2 agf_freeblks 4294169013, counted 259214 in ag 0 agf_longest 4226175622, counted 92667 in ag 0 agf_btreeblks 1887445875, counted 4 in ag 0 bad agbno 1315257652 for inobt root, agno 0 bad agbno 1345328407 for finobt root, agno 0 agi_count 3478294320, counted 0 in ag 0 agi_freecount 3835584455, counted 0 in ag 0 agi_freecount 3835584455, counted 0 in ag 0 finobt sb_icount 0, counted 36107 sb_ifree 0, counted 744 sb_fdblocks 3417573298, counted 151228568 root inode chunk not found Phase 3 - for each AG... - scan and clear agi unlinked lists... found inodes not in the inode allocation tree found inodes not in the inode allocation tree found inodes not in the inode allocation tree - process known inodes and perform inode discovery... - agno = 0 bad CRC for inode 128 Bad flags2 set in inode 128 inode 128 is marked reflinked but file system does not support reflink bad CRC for inode 131 bad (negative) size -6865318305617900790 on inode 131 bad CRC for inode 128, will rewrite imap claims a free inode 128 is in use, correcting imap and clearing inode cleared root inode 128 bad CRC for inode 131, will rewrite bad (negative) size -6865318305617900790 on inode 131 cleared inode 131 correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap - agno = 1 - agno = 2 - agno = 3 Metadata CRC error detected at 0x44d70d, xfs_bmbt block 0x20179ef68/0x1000 Metadata corruption detected at 0x435c33, xfs_inode block 0x2011b22a0/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x2011b22c0/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x2017976a0/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x2017976c0/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x2017976e0/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x201797700/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x201799ca0/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x201799cc0/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x201799ce0/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x201799d00/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x2017a0020/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x2017a0040/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x2017a3e60/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x2017a3e80/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x2017a6c20/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x2017a6c40/0x4000 - agno = 4 Metadata CRC error detected at 0x44d70d, xfs_bmbt block 0x20179ef68/0x1000 btree block 4/3096049 is suspect, error -74 bad magic # 0x8cadd3ff in inode 8590157704 (data fork) bmbt block 1076837873 bad data fork in inode 8590157704 cleared inode 8590157704 bad CRC for inode 8608490176 bad magic number 0x2f54 on inode 8608490176 bad version number 0xffffffd1 on inode 8608490176 inode identifier 13615366143686386256 mismatch on inode 8608490176 bad CRC for inode 8608490177 bad magic number 0x9700 on inode 8608490177 bad version number 0x44 on inode 8608490177 inode identifier 6120755948910744761 mismatch on inode 8608490177 bad CRC for inode 8608490178 bad magic number 0x80d5 on inode 8608490178 bad version number 0xfffffff3 on inode 8608490178 inode identifier 3254102953752242707 mismatch on inode 8608490178 bad CRC for inode 8608490179 bad magic number 0xbca8 on inode 8608490179 bad version number 0x2f on inode 8608490179 inode identifier 12037120777945602494 mismatch on inode 8608490179 bad CRC for inode 8608490180 bad magic number 0xf0c5 on inode 8608490180 bad version number 0x78 on inode 8608490180 inode identifier 13032550265502662767 mismatch on inode 8608490180 bad CRC for inode 8608490181 bad magic number 0xcfe7 on inode 8608490181 bad version number 0x10 on inode 8608490181 inode identifier 15349309774536052618 mismatch on inode 8608490181 bad CRC for inode 8608490182 bad magic number 0x92e6 on inode 8608490182 bad version number 0xffffffe3 on inode 8608490182 inode identifier 8416647903581055172 mismatch on inode 8608490182 bad CRC for inode 8608490183 bad magic number 0x228d on inode 8608490183 bad version number 0xd on inode 8608490183 inode identifier 11477456201708827091 mismatch on inode 8608490183 bad CRC for inode 8608490184 bad magic number 0x1fbf on inode 8608490184 bad version number 0xffffffdf on inode 8608490184 inode identifier 2781657589882828282 mismatch on inode 8608490184 bad CRC for inode 8608490185 bad magic number 0x5f9f on inode 8608490185 bad version number 0x17 on inode 8608490185 inode identifier 10802432031393697895 mismatch on inode 8608490185 bad CRC for inode 8608490186 bad magic number 0xfa3a on inode 8608490186 bad version number 0xffffff98 on inode 8608490186 inode identifier 6619025381081967690 mismatch on inode 8608490186 bad CRC for inode 8608490187 bad magic number 0xa44c on inode 8608490187 bad version number 0x78 on inode 8608490187 inode identifier 4572966310690235980 mismatch on inode 8608490187 bad CRC for inode 8608490188 bad magic number 0x5fb5 on inode 8608490188 bad version number 0x50 on inode 8608490188 inode identifier 12079066686168554224 mismatch on inode 8608490188 bad CRC for inode 8608490189 bad magic number 0x48a4 on inode 8608490189 bad version number 0x5f on inode 8608490189 inode identifier 648377241230310267 mismatch on inode 8608490189 bad CRC for inode 8608490190 bad magic number 0x5341 on inode 8608490190 bad version number 0xffffffa2 on inode 8608490190 inode identifier 15388574406960749289 mismatch on inode 8608490190 bad CRC for inode 8608490191 bad magic number 0x74d1 on inode 8608490191 bad version number 0xfffffff1 on inode 8608490191 inode identifier 4318804125124646133 mismatch on inode 8608490191 bad CRC for inode 8608490192 bad magic number 0xb184 on inode 8608490192 bad version number 0x49 on inode 8608490192 inode identifier 4580656399028656995 mismatch on inode 8608490192 bad CRC for inode 8608490193 bad magic number 0xb1a1 on inode 8608490193 bad version number 0x5d on inode 8608490193 inode identifier 2434589425854479768 mismatch on inode 8608490193 bad CRC for inode 8608490194 bad magic number 0xd108 on inode 8608490194 bad version number 0xffffffb7 on inode 8608490194 inode identifier 1807491588415454315 mismatch on inode 8608490194 bad CRC for inode 8608490195 bad magic number 0xf499 on inode 8608490195 bad version number 0x77 on inode 8608490195 inode identifier 8639868923973105692 mismatch on inode 8608490195 bad CRC for inode 8608490196 bad magic number 0xb5b on inode 8608490196 bad version number 0xffffffcd on inode 8608490196 inode identifier 4827273619262000047 mismatch on inode 8608490196 bad CRC for inode 8608490197 (v1.02).zip" at block 7 offset 1952 in directory inode 8658972106 references non-existent inode 8608490182 clearing inode number in entry at offset 1952... <---- tons of entries like this disconnected inode 25848218042, moving to lost+found disconnected inode 25848223241, moving to lost+found disconnected inode 25848223242, moving to lost+found disconnected inode 25848223248, moving to lost+found disconnected inode 25848223249, moving to lost+found disconnected inode 25848223250, moving to lost+found resetting inode 13713319146 nlinks from 5 to 3 resetting inode 13718182623 nlinks from 6 to 3 resetting inode 13718182624 nlinks from 3 to 2 Metadata corruption detected at 0x44d608, xfs_bmbt block 0x20179ef68/0x1000 libxfs_writebufr: write verifier failed on xfs_bmbt bno 0x20179ef68/0x1000 Maximum metadata LSN (2050624958:1251565917) is ahead of log (1:2). Format log to cycle 2050624961. releasing dirty buffer (bulk) to free list! done -
One of my drives was failing and I added a new drive to the array (currently getting cleared). The goal was to move content from the failing drive to the new one using the unbalance app. The failing drive says its contents is emulated but I can't see any of the existing files that I know are on that drive. Diagnostics are attached - please let me know if anything else is needed.
Supermicro X11DAC, C621 chipset: yes/no?
in Motherboards and CPUs
Posted
Should I be concerned with the onboard SAS, or should it run just as well had I bought a card running in IT mode?