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.

gooner_47

Members
  • Joined

  • Last visited

Everything posted by gooner_47

  1. It passed the extended SMART test (attached) Samsung_SSD_870_EVO_500GB_S5Y1NF1R403281P-20221230-1044.txt
  2. I've had the occasional notification about reallocated sectors on the cache disk recently. Is this anything to worry about? nebula-diagnostics-20221230-0921.zip
  3. I mean the server/PC case. I shucked the drive, which Unraid didn't recognise at first, so then I had to tape up the sata pin 3 and it was fine.
  4. Disk is in the case and parity is syncing, eta 2 days. Is this the check you're referring to?
  5. Any general guidance on the best way to check this disk before I shuck it? I'm on mac and have the disk connected via usb still in its enclosure I've tried WD life guard and it does not find the drive (apparently a common problem) I've tried smartctl and it says "operation not supported by device" (apparently it can't be used on external drives) I've seen badblocks recommended very regularly but it seems it was not originally designed for large disk sizes and the -b 4096 flag won't help anymore I'm aware of Unraid's preclear but I'd need to have shucked the drive first to use that Edit - hmmm, just read about someone who ran badblocks over USB 3 on a 12TB drive and it took about a week. I only have USB 2 and a 20TB, it sounds like the time taken to do this with it still in the enclosure may be way too long, even if I could get it running. Should I just shuck it then use preclear in Unraid to check for drive problems?
  6. 20TB on the way (thanks credit card!). Pretty good deal on the WD Elements drives for any UK folks reading - £304.99, works out to £15.25/TB. https://www.amazon.co.uk/Elements-Desktop-External-Hard-Drive/dp/B09TYZCN61/ref=cm_cr_arp_d_product_top?ie=UTF8&th=1 Will this work? Turn off machine Remove old parity drive and replace with new 20TB on same sata port Start machine Stop array Assign 20TB to parity and let it build
  7. "Errors occurred - Check SMART report" The report is attached, is this a replacement situation?! And if so, how urgently does this need to be done? Not a great time, money-wise, as I'm sure others are experiencing. Also (and as 6TB is now on the lower end of drive capacity) in the interests of future-proofing - considering the parity drive needs to equal or exceed the largest data drive, and space saving inside the chassis, should I buy as big as I can afford, to allow me to buy bigger data drives than just 6TB going forward? WDC_WD60EZRX-00MVLB1_WD-WXP1H643RWPX-20221101-1057.txt
  8. Thanks. The error was after the SMART extended test. Would it give any useful information to run another extended test now and post more diagnostics? Should I be looking to replace this drive regardless?
  9. Parity drive has a read error. Diagnostics attached. What's the best course of action? nebula-diagnostics-20221101-0718.zip
  10. Bump on this. Just a suggestion for that setting in case it's any improvement, but if it's more suited as it is, then all good. Also just wanted to say thanks very much for guiding me through the process, very much appreciated.
  11. What does Unraid set this to by default? As I’m pretty sure I wouldn’t have changed this setting without knowing the consequences. If it sets it to “Yes”, wouldn’t it make more sense, based on the advice in this thread, to default it to “No”?
  12. Is that this setting? "Write corrections to parity disk"
  13. I can see further research is definitely required as I believed differently. Parity seems less capable than I originally thought. With reference to my post above - does the parity only become corrupt if it runs after the drives corrupts? i.e. would parity be intact in the following situation: all drives fine (no corruption) run parity and it completes successfully drive x fails STOP parity from running (so it does not know about the corruption) In that scenario would parity have more success in rebuilding the drive? If so, is it almost better to only run parity checks on demand (as opposed to an automated schedule), when you know 100% there are no problems with any of your drives?
  14. I do. They run on a monthly schedule The last successful run was on the 4th September. Is it possible that the 2 subsequent runs (by which point I believe the drive problems had surfaced) corrupted things?
  15. I will educate myself further once I get past this problem. Particularly I would like to try and understand why parity in this case doesn't appear to have helped. I was under the impression that a parity drive (while absolutely not negating the need for a backup) was able to (effectively) bring a drive back from the dead with no loss of data, but this doesn't seem to be the case? I would like to know what I could have done differently, if anything, to avoid this situation.
  16. Does that include the lost+found folder? Will that still be available after rebuilding disk 3 onto the new disk?
  17. Ok, what are the steps to do this? Does this copy the emulated disk contents onto the new disk, making that disk 3? Is there a way to find out which data could have been lost, without mounting the old drive? How will I know without going to the actual overall share and attempting to open the file? Will it show, but just fail to open? Or will it not show at all?
  18. nebula-diagnostics-20221019-1205.zip
  19. Connected old disk 3, changed UUID in UD settings. Click Mount button and the button text changed to Mounting for about 5 minutes, but it didn't seem to work, button changed back to Mount again. Also noticed writes are increasing, is this expected?
  20. Does the array start automatically when booting the machine? If so will that cause any problems if the old disk 3 is connected? i.e. will these steps work in order to connect the old disk and then mount it with UD: Shut down system Connect old drive Boot up system (will array auto start?) Stop array Mount old disk 3 with UD Compare contents of old disk 3 with emulated disk 3 to determine whether to use that data or not
  21. Using what method? Finder? That's how I would usually copy my files. But in finder I already see all of the files I would be expecting. Or do you mean do it somehow within the Unraid UI itself? And if so to which location specifically? - only the emulated disk 3? - or by going to Shares and clicking the file explorer icons on each of the shares in there? What's confusing me is I see repeating folders/data when clicking on each of the disks individually Disk 1 Disk 2 Disk 3
  22. Copy everything from the old disk to... where? Sorry I'm not fully understanding what we're doing with this process, and how I'm able to even see content on the emulated disk 3. I was expecting to add the new drive, format it and add it to the array, then run parity check which would fill that empty drive with the data that should be there. Just need a little more explanation to help get my head around this and what I do with the data I'm copying from the old drive. And when does the new drive get formatted and used?
  23. OK I've started the array in normal mode and the emulated disk mounted. The new replacement drive is still unformatted and unassigned. This is what I see when I click on the file explorer for the emulated disk., which is only a subset of the directories on the NAS as a whole - does this mean this is what's stored just on this disk? There are a few folders here which exist, but do not have the contents I would expect to see (and that I do see when comparing to what I can see in finder), is this ok? I also see lots in the lost and found folder. What exactly do I do with these?
  24. On this screen, when I click the "Check" button, nothing happens. It does not open a filesystem check window. I do not get any notification from Chrome that a popup is being blocked either, so not sure what is going on there. Running your command from the console gave the following: root@Nebula:~# xfs_repair -v /dev/md3 Phase 1 - find and verify superblock... - block cache size set to 237856 entries Phase 2 - using internal log - zero log... zero_log: head block 37421 tail block 37421 - scan filesystem freespace and inode maps... Metadata CRC error detected at 0x439496, xfs_agf block 0x7ffffff9/0x200 agf has bad CRC for ag 1 Metadata CRC error detected at 0x4643f6, xfs_agi block 0x7ffffffa/0x200 agi has bad CRC for ag 1 bad magic # 0x0 for agf 1 bad version # 0 for agf 1 bad sequence # 0 for agf 1 bad length 0 for agf 1, should be 268435455 bad uuid 00000000-0000-0000-0000-000000000000 for agf 1 bad magic # 0x0 for agi 1 bad version # 0 for agi 1 bad sequence # 0 for agi 1 bad length # 0 for agi 1, should be 268435455 bad uuid 00000000-0000-0000-0000-000000000000 for agi 1 reset bad agf for ag 1 reset bad agi for ag 1 bad agbno 0 for btbno root, agno 1 bad agbno 0 for btbcnt root, agno 1 bad agbno 0 for refcntbt root, agno 1 agf_freeblks 938, counted 0 in ag 1 bad agbno 0 for inobt root, agno 1 bad agbno 0 for finobt root, agno 1 agi_freecount 24, counted 0 in ag 1 agi_freecount 24, counted 0 in ag 1 finobt agi unlinked bucket 0 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 1 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 2 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 3 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 4 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 5 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 6 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 7 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 8 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 9 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 10 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 11 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 12 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 13 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 14 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 15 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 16 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 17 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 18 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 19 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 20 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 21 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 22 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 23 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 24 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 25 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 26 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 27 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 28 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 29 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 30 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 31 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 32 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 33 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 34 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 35 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 36 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 37 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 38 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 39 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 40 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 41 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 42 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 43 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 44 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 45 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 46 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 47 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 48 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 49 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 50 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 51 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 52 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 53 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 54 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 55 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 56 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 57 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 58 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 59 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 60 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 61 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 62 is 0 in ag 1 (inode=2147483648) agi unlinked bucket 63 is 0 in ag 1 (inode=2147483648) sb_icount 2176, counted 1792 sb_ifree 227, counted 186 sb_fdblocks 1350187333, counted 1100481525 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 entry "TV Shows" in shortform directory 128 references non-existent inode 2147483780 junking entry "TV Shows" in directory inode 128 entry "Logs" in shortform directory 131 references non-existent inode 2147483776 junking entry "Logs" in directory inode 131 entry "Images" in shortform directory 131 references non-existent inode 2147483778 junking entry "Images" in directory inode 131 entry "m3u8" in shortform directory 132 references non-existent inode 2147483777 junking entry "m3u8" in directory inode 132 entry "config" in shortform directory 148 references non-existent inode 2147483785 junking entry "config" in directory inode 148 entry ".." at block 0 offset 80 in directory inode 183 references non-existent inode 2147483781 entry "templates-user" in shortform directory 2053967 references non-existent inode 2147485032 junking entry "templates-user" in directory inode 2053967 - agno = 1 - agno = 2 entry ".." at block 0 offset 80 in directory inode 4294967424 references non-existent inode 2147483776 entry "727" at block 0 offset 416 in directory inode 4294967424 references non-existent inode 2159524292 clearing inode number in entry at offset 416... entry "750" at block 0 offset 768 in directory inode 4294967424 references non-existent inode 2147485006 clearing inode number in entry at offset 768... entry "760" at block 0 offset 944 in directory inode 4294967424 references non-existent inode 2147485025 clearing inode number in entry at offset 944... entry "762" at block 0 offset 976 in directory inode 4294967424 references non-existent inode 2147484995 clearing inode number in entry at offset 976... entry "766" at block 0 offset 1040 in directory inode 4294967424 references non-existent inode 2147485016 clearing inode number in entry at offset 1040... entry "770" at block 0 offset 1104 in directory inode 4294967424 references non-existent inode 2147484998 clearing inode number in entry at offset 1104... entry "779" at block 0 offset 1248 in directory inode 4294967424 references non-existent inode 2147487307 clearing inode number in entry at offset 1248... entry "781" at block 0 offset 1280 in directory inode 4294967424 references non-existent inode 2147487315 clearing inode number in entry at offset 1280... entry ".." at block 0 offset 80 in directory inode 4294967429 references non-existent inode 2147483781 - agno = 3 entry "backup-20220808.231132" at block 0 offset 1456 in directory inode 6446624904 references non-existent inode 2159524289 clearing inode number in entry at offset 1456... - agno = 4 entry ".." at block 0 offset 80 in directory inode 8589934720 references non-existent inode 2147483776 entry "726" at block 0 offset 416 in directory inode 8589934720 references non-existent inode 2159524290 clearing inode number in entry at offset 416... entry "731" at block 0 offset 496 in directory inode 8589934720 references non-existent inode 2159524304 clearing inode number in entry at offset 496... entry "752" at block 0 offset 832 in directory inode 8589934720 references non-existent inode 2147485030 clearing inode number in entry at offset 832... entry "758" at block 0 offset 928 in directory inode 8589934720 references non-existent inode 2147485021 clearing inode number in entry at offset 928... entry "765" at block 0 offset 1040 in directory inode 8589934720 references non-existent inode 2147485019 clearing inode number in entry at offset 1040... entry "772" at block 0 offset 1152 in directory inode 8589934720 references non-existent inode 2159524327 clearing inode number in entry at offset 1152... entry "773" at block 0 offset 1168 in directory inode 8589934720 references non-existent inode 2147485001 clearing inode number in entry at offset 1168... entry "777" at block 0 offset 1232 in directory inode 8589934720 references non-existent inode 2147487303 clearing inode number in entry at offset 1232... entry "backup-20220818.011555" at block 0 offset 1896 in directory inode 6446624904 references non-existent inode 2147485003 clearing inode number in entry at offset 1896... entry ".." at block 0 offset 80 in directory inode 8589934771 references non-existent inode 2147483778 entry "a5" at block 0 offset 128 in directory inode 8589934771 references non-existent inode 2147483804 clearing inode number in entry at offset 128... entry "8d" at block 0 offset 224 in directory inode 8589934771 references non-existent inode 2147483806 clearing inode number in entry at offset 224... entry "ad" at block 0 offset 320 in directory inode 8589934771 references non-existent inode 2147483809 clearing inode number in entry at offset 320... entry "9a" at block 0 offset 416 in directory inode 8589934771 references non-existent inode 2147483813 clearing inode number in entry at offset 416... entry "37" at block 0 offset 512 in directory inode 8589934771 references non-existent inode 2147483815 clearing inode number in entry at offset 512... entry "53" at block 0 offset 608 in directory inode 8589934771 references non-existent inode 2147483818 clearing inode number in entry at offset 608... entry "31" at block 0 offset 704 in directory inode 8589934771 references non-existent inode 2147483820 clearing inode number in entry at offset 704... entry "1d" at block 0 offset 800 in directory inode 8589934771 references non-existent inode 2147483822 clearing inode number in entry at offset 800... entry "d4" at block 0 offset 896 in directory inode 8589934771 references non-existent inode 2147483824 clearing inode number in entry at offset 896... entry "78" at block 0 offset 1024 in directory inode 8589934771 references non-existent inode 2152013001 clearing inode number in entry at offset 1024... entry "84" at block 0 offset 1120 in directory inode 8589934771 references non-existent inode 2152013003 clearing inode number in entry at offset 1120... entry "58" at block 0 offset 1216 in directory inode 8589934771 references non-existent inode 2152013007 clearing inode number in entry at offset 1216... entry "7e" at block 0 offset 1312 in directory inode 8589934771 references non-existent inode 2152013009 clearing inode number in entry at offset 1312... entry "6a" at block 0 offset 1328 in directory inode 8589934771 references non-existent inode 2152013013 clearing inode number in entry at offset 1328... entry "e3" at block 0 offset 1424 in directory inode 8589934771 references non-existent inode 2152013015 clearing inode number in entry at offset 1424... entry "61" at block 0 offset 1568 in directory inode 8589934771 references non-existent inode 2152013020 clearing inode number in entry at offset 1568... entry "b4" at block 0 offset 1664 in directory inode 8589934771 references non-existent inode 2152013023 clearing inode number in entry at offset 1664... entry "04" at block 0 offset 1728 in directory inode 8589934771 references non-existent inode 2152013026 clearing inode number in entry at offset 1728... entry "76" at block 0 offset 1824 in directory inode 8589934771 references non-existent inode 2152013029 clearing inode number in entry at offset 1824... entry "41" at block 0 offset 1920 in directory inode 8589934771 references non-existent inode 2152013032 clearing inode number in entry at offset 1920... entry "81" at block 0 offset 2016 in directory inode 8589934771 references non-existent inode 2152013035 clearing inode number in entry at offset 2016... entry "03" at block 0 offset 2112 in directory inode 8589934771 references non-existent inode 2152013037 clearing inode number in entry at offset 2112... entry "b7" at block 0 offset 2288 in directory inode 8589934771 references non-existent inode 2152013046 clearing inode number in entry at offset 2288... entry "66" at block 0 offset 2384 in directory inode 8589934771 references non-existent inode 2152013052 clearing inode number in entry at offset 2384... entry "a2" at block 0 offset 2480 in directory inode 8589934771 references non-existent inode 2156991488 clearing inode number in entry at offset 2480... entry "0a" at block 0 offset 2576 in directory inode 8589934771 references non-existent inode 2156991492 clearing inode number in entry at offset 2576... entry "da" at block 0 offset 2608 in directory inode 8589934771 references non-existent inode 2156991495 clearing inode number in entry at offset 2608... entry "0e" at block 0 offset 2704 in directory inode 8589934771 references non-existent inode 2159524299 clearing inode number in entry at offset 2704... entry "45" at block 0 offset 2816 in directory inode 8589934771 references non-existent inode 2159524312 clearing inode number in entry at offset 2816... entry "b3" at block 0 offset 2912 in directory inode 8589934771 references non-existent inode 2159524315 clearing inode number in entry at offset 2912... entry "fe" at block 0 offset 2992 in directory inode 8589934771 references non-existent inode 2159524319 clearing inode number in entry at offset 2992... entry "59" at block 0 offset 3088 in directory inode 8589934771 references non-existent inode 2159524321 clearing inode number in entry at offset 3088... entry "f9" at block 0 offset 3120 in directory inode 8589934771 references non-existent inode 2159524323 clearing inode number in entry at offset 3120... entry "b2" at block 0 offset 3184 in directory inode 8589934771 references non-existent inode 2159524325 clearing inode number in entry at offset 3184... entry "60" at block 0 offset 3264 in directory inode 8589934771 references non-existent inode 2159524333 clearing inode number in entry at offset 3264... entry "83" at block 0 offset 3376 in directory inode 8589934771 references non-existent inode 2159524338 clearing inode number in entry at offset 3376... entry "11" at block 0 offset 3504 in directory inode 8589934771 references non-existent inode 2159524344 clearing inode number in entry at offset 3504... entry "aa" at block 0 offset 3552 in directory inode 8589934771 references non-existent inode 2156991517 clearing inode number in entry at offset 3552... entry "54" at block 0 offset 3712 in directory inode 8589934771 references non-existent inode 2147485044 clearing inode number in entry at offset 3712... entry ".." at block 0 offset 80 in directory inode 6446624941 references non-existent inode 2147483780 entry "[email protected]" in shortform directory 6446624956 references non-existent inode 2147485017 junking entry "[email protected]" in directory inode 6446624956 entry ".." at block 0 offset 80 in directory inode 8655897962 references non-existent inode 2147483781 - agno = 5 entry "Location, Location, Location" at block 0 offset 552 in directory inode 10737418370 references non-existent inode 2159524342 clearing inode number in entry at offset 552... entry "Married at First Sight" at block 0 offset 912 in directory inode 10737418370 references non-existent inode 2156991531 clearing inode number in entry at offset 912... entry "This Is 40 (2012)" at block 0 offset 288 in directory inode 10737418371 references non-existent inode 2159524317 clearing inode number in entry at offset 288... entry "Elvis (2022)" at block 0 offset 392 in directory inode 10737418371 references non-existent inode 2159524307 clearing inode number in entry at offset 392... entry ".." at block 0 offset 80 in directory inode 10737418426 references non-existent inode 2147483781 entry ".." at block 0 offset 80 in directory inode 10772335335 references non-existent inode 2147483780 entry ".." at block 0 offset 80 in directory inode 10807526525 references non-existent inode 2147483780 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 entry ".." in directory inode 183 points to non-existent inode 2147483781, marking entry to be junked bad hash table for directory inode 183 (no data entry): rebuilding rebuilding directory inode 183 - agno = 1 - agno = 2 entry ".." in directory inode 4294967424 points to non-existent inode 2147483776, marking entry to be junked bad hash table for directory inode 4294967424 (no data entry): rebuilding rebuilding directory inode 4294967424 entry ".." in directory inode 4294967429 points to non-existent inode 2147483781, marking entry to be junked bad hash table for directory inode 4294967429 (no data entry): rebuilding rebuilding directory inode 4294967429 - agno = 3 bad hash table for directory inode 6446624904 (no data entry): rebuilding rebuilding directory inode 6446624904 entry ".." in directory inode 6446624941 points to non-existent inode 2147483780, marking entry to be junked bad hash table for directory inode 6446624941 (no data entry): rebuilding rebuilding directory inode 6446624941 - agno = 4 entry ".." in directory inode 8589934720 points to non-existent inode 2147483776, marking entry to be junked bad hash table for directory inode 8589934720 (no data entry): rebuilding rebuilding directory inode 8589934720 entry ".." in directory inode 8589934771 points to non-existent inode 2147483778, marking entry to be junked bad hash table for directory inode 8589934771 (no data entry): rebuilding rebuilding directory inode 8589934771 entry ".." in directory inode 8655897962 points to non-existent inode 2147483781, marking entry to be junked bad hash table for directory inode 8655897962 (no data entry): rebuilding rebuilding directory inode 8655897962 - agno = 5 bad hash table for directory inode 10737418370 (no data entry): rebuilding rebuilding directory inode 10737418370 bad hash table for directory inode 10737418371 (no data entry): rebuilding rebuilding directory inode 10737418371 entry ".." in directory inode 10737418426 points to non-existent inode 2147483781, marking entry to be junked bad hash table for directory inode 10737418426 (no data entry): rebuilding rebuilding directory inode 10737418426 entry ".." in directory inode 10772335335 points to non-existent inode 2147483780, marking entry to be junked bad hash table for directory inode 10772335335 (no data entry): rebuilding rebuilding directory inode 10772335335 entry ".." in directory inode 10807526525 points to non-existent inode 2147483780, marking entry to be junked bad hash table for directory inode 10807526525 (no data entry): rebuilding rebuilding directory inode 10807526525 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected dir inode 149, moving to lost+found disconnected dir inode 183, moving to lost+found disconnected dir inode 2044968, moving to lost+found disconnected dir inode 2044978, moving to lost+found disconnected dir inode 2044988, moving to lost+found disconnected dir inode 2053954, moving to lost+found disconnected dir inode 4294967424, moving to lost+found disconnected dir inode 4294967428, moving to lost+found disconnected dir inode 4294967429, moving to lost+found disconnected dir inode 4294967439, moving to lost+found disconnected dir inode 4294968315, moving to lost+found disconnected dir inode 4320009343, moving to lost+found disconnected dir inode 4322098254, moving to lost+found disconnected dir inode 4322098272, moving to lost+found disconnected dir inode 4330355292, moving to lost+found disconnected dir inode 4330355326, moving to lost+found disconnected dir inode 6446624928, moving to lost+found disconnected dir inode 6446624933, moving to lost+found disconnected dir inode 6446624941, moving to lost+found disconnected dir inode 6446626830, moving to lost+found disconnected dir inode 6537114832, moving to lost+found disconnected dir inode 6537114834, moving to lost+found disconnected dir inode 6537114836, moving to lost+found disconnected dir inode 6537114840, moving to lost+found disconnected dir inode 6537114867, moving to lost+found disconnected dir inode 6537114872, moving to lost+found disconnected dir inode 6537315531, moving to lost+found disconnected dir inode 8589934720, moving to lost+found disconnected dir inode 8589934723, moving to lost+found disconnected dir inode 8589934768, moving to lost+found disconnected dir inode 8589934771, moving to lost+found disconnected dir inode 8654827287, moving to lost+found disconnected dir inode 8654827295, moving to lost+found disconnected dir inode 8654827320, moving to lost+found disconnected dir inode 8654827323, moving to lost+found disconnected dir inode 8655897436, moving to lost+found disconnected dir inode 8655897441, moving to lost+found disconnected dir inode 8655897459, moving to lost+found disconnected dir inode 8655897962, moving to lost+found disconnected dir inode 10737418426, moving to lost+found disconnected dir inode 10744666244, moving to lost+found disconnected dir inode 10772335300, moving to lost+found disconnected dir inode 10772335305, moving to lost+found disconnected dir inode 10772335314, moving to lost+found disconnected dir inode 10772335335, moving to lost+found disconnected dir inode 10772335340, moving to lost+found disconnected dir inode 10807526513, moving to lost+found disconnected dir inode 10807526525, moving to lost+found disconnected dir inode 10807526527, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 128 nlinks from 9 to 8 resetting inode 4294967424 nlinks from 41 to 33 resetting inode 6446624904 nlinks from 32 to 30 resetting inode 6446624956 nlinks from 3 to 2 resetting inode 8589934720 nlinks from 41 to 33 resetting inode 10737418370 nlinks from 18 to 16 resetting inode 10737418371 nlinks from 16 to 14 resetting inode 8589934771 nlinks from 234 to 195 resetting inode 131 nlinks from 7 to 5 resetting inode 132 nlinks from 4 to 3 resetting inode 148 nlinks from 3 to 2 resetting inode 398 nlinks from 2 to 51 resetting inode 2053967 nlinks from 3 to 2 XFS_REPAIR Summary Tue Oct 18 12:25:50 2022 Phase Start End Duration Phase 1: 10/18 12:25:48 10/18 12:25:49 1 second Phase 2: 10/18 12:25:49 10/18 12:25:49 Phase 3: 10/18 12:25:49 10/18 12:25:50 1 second Phase 4: 10/18 12:25:50 10/18 12:25:50 Phase 5: 10/18 12:25:50 10/18 12:25:50 Phase 6: 10/18 12:25:50 10/18 12:25:50 Phase 7: 10/18 12:25:50 10/18 12:25:50 Total run time: 2 seconds done
  25. I have removed -n, clicked Check and am in the same situation as my previous post. Nothing changes on the page, visually nothing is happening.

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.