cliewmc

Hi JB, as an update, disk2 is up and I found hundreds of thousands of pdf, xlsx, docx files in 'lost+found' folder. I have deleted them. It turned out these were created by Ransomware Protection. I would advise not to set "Recreate Bait Files" if doing reboots because they take some time to create. During file creations and a reboot happens, these get trapped inno-man's land, and end up unlinked. In subsequent xfs_repair checks, more of these have been found. I had taken off the parity disk and set it to 'no device'. I have proceeded to preclear it to use as a normal data disk - don't trust it to be a parity disk. I am readying a replacement in the meantime. My NAS is now running without parity for the time being. Regards.

disk2: Is this how xfs_repair ends? Answer: Yes. In this case, what is the sequence for recovery? Reboot server to and found disk2 is now mounted! parity: Yes, those are the reallocated sectors I told you about and I would replace that disk. Answer: Okay, noted. I will set out to use new cable first, rebuild (now that disk2 is recovered), then change it. Thanks JB, it's a relief that disk2 is up! Progress is positive. cL

Thanks for the advice. I have not done that in a long time, and left the system to do it for me. Luckily, the 'previous' folder had the info in there. I will schedule regular backups from now on. Thank you again. Regards. cL

Hi JB, the xfs_repair was from the GUI. I found that I clicked on Main, then go back to the disk2 screen, the results were displayed. It's not good, it's 2,700 pages long in Word document. Extract of portions of it looked like this: --- start --- Phase 1 - find and verify superblock... 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... agf_freeblks 98235484, counted 98235466 in ag 0 - 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 data fork in regular inode 2153876768 claims used block 269477115 correcting nextents for inode 2153876768 --- entry ".master through with-08.06.17.pdf" at block 0 offset 2312 in directory inode 180545041 references free inode 5368712851 clearing inode number in entry at offset 2312... clearing inode number in entry at offset 640... --- rebuilding directory inode 3227471378 entry ".." in directory inode 3227471387 points to free inode 4294969678 bad hash table for directory inode 3227471387 (no data entry): rebuilding rebuilding directory inode 3227471387 entry ".." in directory inode 3227471388 points to free inode 4294969678 bad hash table for directory inode 3227471388 (no data entry): rebuilding rebuilding directory inode 3227471388 --- list!releasing dirty buffer (bulk) to free list!releasing dirty buffer (bulk) to free list!releasing dirty buffer (bulk) to free list!releasing dirty buffer (bulk) to free list!releasing dirty buffer (bulk) to free list!releasing dirty buffer (bulk) to free list!releasing dirty buffer (bulk) to free list!releasing dirty buffer (bulk) to free list!releasing dirty buffer (bulk) to free list!releasing dirty buffer (bulk) to free list!releasing dirty buffer (bulk) to free list!releasing dirty buffer (bulk) to free list!done --- end --- Disk2 is really dead . My next hope is that I can rescue the parity drive with a new cable and try to rebuild a new drive to replace disk2. I might still be in trouble as the parity has some errors: (see attached files) #Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 5 Reallocated sector count 0x0033 100 100 050 Pre-fail Always Never 1240 Will keep you informed. Thank you for your advice. cL NAS1_2parity_settings.pdf

Parity: Tried to reconnect cable but same issue so I will need to get new cables to test. Disk2: Running the xfs_repair -L and it's taking a long time - still running after 2 hours... with this message: Phase 1 - find and verify superblock... so I suspect the disk has a lot of errors and may not be recoverable. I'll wait until tomorrow to see if we will see the end of the repair. I remember reading that it's only a few minutes to half an hour.

OMG, I copied the root files from a previous install & it works - so it must be one of the primary files, either bzroot or bzimage file must be corrupt. I am now able to boot into the login screen! Went on to Replace Key, and Installed the new key. I am back in business. Thank you for advice given. Closed. cL

Yeah, you are right. Please read my latest post. It looks like when I was upgrading to the new version 6.40 (before the start of my problem), the USB died, and some files became corrupted. So it appears I may need to use latest unRAID download and rebuild my current disks array with a new install. Can you point me the way?

Thanks JB & CHBMB for your swift response. Indeed. I thought it was the boot sector corruption, so using the old USB I made it bootable again. It fired up but failed at the login screen. At least I was able to bootup. Again it kept disappearing and coming back when plugged in the Windows PC. Tried reformating the old USB - it says cannot reformat it, so confirm it is DEAD. Using the new USB, copy the existing files across and on boot, it had the problem with booting up. Next I tried to run Make_bootable (as administrator), but it just disappeared without the DOS window. I then copied the downloaded latest version of the unRAID and copied Make_bootable into the USB stick, and also SYSLINUX directory. This time it was able to boot up but stuck at this screen. I tried earlier running a clean install of unRAID and was presented with #Tower login. When I looked at webgui, all disks were unassigned (of course!), I decided to wait for your expertise with the above. New USB + original files + new syslinux. What shall I do next?

Hi there, I just upgraded to the latest version of the unRAID but on reboot, I found there was an error at the BIOS level that says no boot device. I have gone into the BIOS and set the default boot to be USB. It still has the same message: no boot device (see screenshot). I suspect the USB may be faulty. I unplugged the USB and place it in a Windows PC, and managed to copy the data off it, it kept disappearing and then coming back. I was prompted that it had errors and advised to scan. I scanned it and it says it has errors. I suspect it's a faulty USB. 1) Shall I reformat the USB, and copy the files back to it? 2) Buy a new USB stick & request for a replacement key? Any advice will be helpful. Regards. cL

Thanks JB, will do, will report my results later. Appreciate the support. [phew! sigh of relief] cL

Here are the diag reports, before & after reboot. Thanks. cL clnasty-diagnostics-20180130-0921.zip clnasty-diagnostics-20180130-0928.zip

Hey jb, thanks for the swift response. I’ll work on the diags. Thanks. cL

Hi there, this is my issue: Parity (Disk DSBL) and one data disk2 (Unmountable No File System) Is there any way I can recover the Parity? I believe disk2 is completely dead based on the error report. All the file systems are xfs. I have attached logs but can provide more if they are not the correct ones. Any advice I can get would be greatly appreciated. Regards. cL NAS1_1main.pdf NAS1_2parity_settings.pdf NAS1_3disk2_settings.pdf clnasty-smart-20180129-1455.zip clnasty-smart-20180129-1432.zip

Instead of starting a new thread, I think my preclear failed question may be related. I am attaching some files, including diagnostics file. All my software is up-to-date The hard drive has been precleared at least 4 times and each time, it stops at 82-89% at the first Pre-read cycle. Any advice will be appreciated. Regards. cL clnasty3-diagnostics-20170419-2031.zip clnasty3-preclear_screenshots,etc.zip

Can someone please advise which version of preclear plugin & unassigned disk plugin I can go back to so that I can preclear my disks? Not very good with the tech stuff, I presume unassigned disk is a requirement for preclear plugin. Any help will be greatly appreciated. There's an archive here: https://github.com/gfjardim/unRAID-plugins/blob/master/archive/

Try removing all the entries in "Quick Access". These are recent files that was accessed by the Win10 PC, that keeps an entry under Quick Access. It solved my problems. Hope that helps.

Advice for pictures (as promised?) I'm in the midst of building my DS380 but the wires are a mess, there's very little space to manoeuvre my fat fingers. I'm interested in how you manage the wiring. Thanks. Chris

Thank you mr-hexen, trurl & itimpi for your advice. unRAID 6 have resolved it. I had to change the network.cfg to set up the STATIC IP for it to work. However, the orange light is still showing on the NIC even tho' I am reach it from the network. I will looking towards PhAzE for the plugins. I will be a happy man after I get all my drives: 1x parity & 2x data disks assigned properly. Right now I managed to see only 1x data drive & managed to preclear it. It's another topic if I can't resolve by opening up the NAS to check the connectivity for the other 2 disks. Consider this thread closed. Thanks guys! cL

Okay, may just try that. I thot beta 6 64bit may have too many unsupported plugins so I did not go with it. As a contingency, I have another mobo Asus H97-Plus which has an Intel NIC. I'll check out v6 first, otherwise I will have to replace the mobo. Thanks for your help.

Seems that this Qualcomm Atheros AR8171 NIC is unsupported. A similar post elsewhere from Jan-2014. http://lime-technology.com/forum/index.php?topic=31333.0 Is there any hope that the next unRAID version will support this? If so, when can we expect it to be out?

Sorry, I am new to accessing the syslog. I'm attaching it here. Thanks for the support. syslog.txt

hi there, I have a new unRAID server built, the mobo is H97M-ITX/ac with an integrated NIC Qualcomm Atheros AR8171. I got the above error message. In the other post: http://lime-technology.com/forum/index.php?topic=24392.0, there's a real possibility that the unRAID version v5.0.5 (latest version) may not support the NIC. I have tried solutions to set up a static IP via this post: http://lime-technology.com/wiki/index.php/Configuration_Tutorial#Verifying_Network_Connectivity, by editing the static IP in the network.cfg, but to no avail. I get an orange/ green on the NIC (server) and green/ green on the network hub, so I think my NIC is not communicating to the network. I cannot detect the server from a network PC. Can you assist with my problem? Grateful for the support. Regards.

Thanks a heap, guys, and trurl for your comment. I left out this all-important statement in my New Flash device upgrade: Before ejecting your flash, restore the 'config' directory from your back up. I have successfully rebooted using the old install after 'make bootable' command. I'll proceed carefully for the 5.0.5 next. Thanks again.

Hi there, I upgraded from a working 5.0.4 unRAID system to 5.0.5 using the clean install USB drive option, following instructions. Included simple features. I have a LSI M1015 8port PCIe card. On reboot, the drives were not visible. I went into bootup and changed the boot sequence to UEFI: USB disk. On bootup, it shows 'tower' login and only 3-4 primary disks, all unassigned. I had about 9 disks in total, with the remaining 5 on the M1015 card, now not visible. Recovery mode. Copied original 5.0.4 files back into USB drive, I incl overwriting the hidden file. The bootup failed with 'boot error' no matter what sequence is set. Panic Question: while I investigate further, will the array and data be still intact? Did the first boot using 5.0.5 cause any change to the unRAiD array? So far I had just been working on the USB drive. I figured my problem may be the recovery mode back to original may be flawed. I intend to make bootable using the 5.0.4 make bootable but Run as Administrator. I will try it first and post. Please answer my panic question first. Thanks! Sent from my iPhone using Tapatalk

Thanks dgaschk for the response, the 2nd disk took about 6-7 hrs to clear, and 5 mins to format. Both the disks are now in the array, and all green balls!!! Interesting that you said that the signature is no longer valid, and clearing will not start. It took only 6-8 hours to get a disk online, does it mean that pre-clear is no longer efficient? It took 24 hrs to pre-clear. Based on this experience, reading up in the forum, and your response, they have provided me with more knowledge about unRaid. Happy for you to close the question. Thanks for the support. cliewmc