lungnut

Thanks again. Your last suggestion worked like a charm!

Wow, thanks so much. Way easier than what I've been attempting. One last question, though. This allows me access to my files via my home network. But since I don't have a IP address that I've assigned to my server, how do I access the Unraid GUI via my browser? I used to be able to input http://192.168.1.38/Main into the address bar and access it (because I assigned that IP to it). Thanks again. I can't tell you how much I appreciate this.

Hello, I've had an Unraid server for 16 years (time flies) and have updated it sparingly. It is currently running headless v6.5. I only use it as a data server--nothing else is running. I don't have a great tech brain, but I can follow instructions. Here's my problem: I swapped internet providers to AT&T Fiber. I haven't been able to connect to my server since. I have logged into the internet using the ethernet connection that my server uses. Using the info I got from running ipconfig, I have changed my network.cfg to the following: # Generated network settings USE_DHCP=no IPADDR=192.168.1.38 NETMASK=255.255.255.0 GATEWAY=192.168.1.254 I've done this before, having swapped ISP's (and physically moved) several times over the past 16 years, but for whatever reason, I am failing today. Any suggestions? I have no idea where to go from here.

Hi, CreZo---everything went flawlessly. Good luck!

Interesting—wouldn’t have guessed this. I will definitely run a parity check after adding the drives. Thanks!

With three brand new drives, I’m thinking it’s better to clear them. I’m not in any big rush, so I don’t mind spending the time. As for the new config setting, thanks so much. This is exactly why I made the post.

I have successfully dealt with a host of recent issues in my 20-drive system. I’ve bumped my parity drive up to 8TB from 6TB and I have moved the data off three of my smaller drives onto a couple of my larger drives (currently I have a mix of data drives ranging from 1.5TB to 6TB, with ten 3TB in the middle). The plan is to remove those three older (and now empty) drives and replace them all with 8TB drives (preferably XFS-formatted). Before I do something really stupid, I’d like to review the process. I have never “shrunk” my array in the ten years I’ve had it; I’ve only added drives. 1) Power down and remove the three smaller drives (again, to be clear, I have emptied these drives of all data). 2) Power up and those drives will now be (I think) reported as missing, and the array will not have started. 3) In the Tools tab, run New Config. This essentially tells Unraid that the missing disks are intentionally missing and that everything is okay, right? 4) Rebuild the parity (I think this will probably begin automatically?) 5) After parity has completed, power down and add the three new drives. 6) Power up, assign the new drives, and start the array. The new 8TB drives will be added after they are cleared and XFS-formatted. This will take several (many?) hours. Is all that correct? Thanks!

johnnie: All right! Finally--I am back up. I'm so thankful. I've attached my syslog in case you have the time to give it a quick glance. I think I'm good? Moving forward, I thought I would move to 12TB drives and retire all of my 1.5TB, 2TB, and 3TB drives, but after weighing the cost of 12TB drives vs. 6TB drives, I think I'll stick with 6TB drives and do the same at way less cost. It will take six of them to retire all 15 of my smaller drives. Question(s): I am right in thinking that I should upgrade to 6.5 first before doing this, right? Also I believe Unraid also now supports dual parity, so it also seems a good idea to add another parity as soon as I have an empty slot in my Norco case, yeah? Oh, and johnnie--in looking at your profile, you have me beat as a forum member by four days (December 2007). But it's amazing how much more you know than I do; I feel ashamed, hahaha. Again, thanks so much for helping me out. I can't tell you how much I freaking appreciate it. syslog_180329.txt

johnnie: I swapped disk14 and disk10's positions in my chassis and started another rebuild. So far, this one has been going okay, I think? There were a handful of errors on yet another disk, disk13, but I think those are sorted? I actually have no idea. I am 31% into the rebuild. I'm attaching a jpg and my syslog. Am I okay to allow this to continue? It has slowed down considerably and another odd thing is that even though my other 1.5TB drives have gone to sleep (because my rebuild is beyond their size at this point), the "trouble" drive disk14 hasn't yet gone to sleep. I thought that was odd. (Note: I'm about to go into work and won't be able to check in on things for about 11 hours or so). And to jowi: My plan after this is to go up to a 12TB parity and then replace one of my 1.5TB with another 12TB, and then copy all of my other smaller, older drives' data onto that new disk. I am not in a position where I can easily dispose of the data that are on these drives. Yes, I should have paid better attention and should have replaced those drives earlier, but I am where I'm at right now trying to make the best of it. Do you really think I'm in an un-salvageable state with my data? syslog_180328AM.txt

Swapped the cable for the backplane of disk14 and tried to rebuild. Unfortunately, the errors started accumulating around 7% thru the rebuild. Syslog attached. Any other ideas? I really appreciate the help. SMART_180326.txt

And, finally, the results of the extended SMART test (attached). Looks like no errors? Is there any way to get this drive up and running successfully? Because if I am reading the situation correctly, if I can't get this drive back up, I might lose all the data on both disk14 and disk16, right? If there is ANY way to avoid that, I cannot tell you how appreciative I'd be. SMART_Extended.txt

Ah, didn't realize about my syslog being so short. This will be better. Since my syslog is full of individual sector errors for disk14, it's rather long and (probably) redundant. So I offer three sizes. The full one is really unwieldy. Just to be clear: all three start from the beginning, the difference is in how "far" they go. NOTE: I have to zip them in order to upload them because of their size, sorry. I am going to run the extended SMART now. Thanks so much for the syslog_three-lengths.zip

Not sure if this is the same info I just posted as smart.txt in my previous post, but just in case this is different information or just plain easier to read, here's the SMART report from my telnet session. Disk14_SMART.txt

And here is the SMART report for disk14. smart.txt

I really need to learn how to read a syslog. Sorry to waste your time. I was under the impression that the syslog file on my thumb drive was always updated to the last restart. I am attaching the real one now. I will search on how to pull a SMART report for disk14 and post it once I've figured it out. Serversyslog.txt

Motherboard: SUPERMICRO MBD-X9SCM-F-O CPU: Intel Core i3-2120 3.3GHz RAM: Kingston 4GB DDR3 1333 SATA Controllers: LSI 9211-8i (X 2) (these two just replaced two SUPERMICRO AOC-SASLP-MV8's, see below) Case: Norco 4220 Unraid: v5.0.4 (largest disk size 6TB) Hello, Last week I attempted a parity check. No reason other than it had been nearly a year since my last one. During the parity check, eight of my disks went offline and when I rebooted, they came back but one was redballed (disk16, a 6TB drive). I replaced the red-balled drive and attempted to rebuild but again the same eight disks went offline and the rebuild failed. All of the offline disks were connected to one of my SATA controllers (a Supermicro SASLP). I tried to replace the bad card with a SAS2LP, but the speed of the rebuild was atrocious. So I did some reading and decided to replace both my SATA cards with the LSI cards that are listed above. My rebuild from that point went great, tooling around at 100 MB/s. However, at approximately the 3% mark, another one of my disks started reporting a ton of errors, disk14, a 1.5TB drive (also the temperature of this drive was replaced with an asterisk). The rebuild progress still seemingly continued, but the new drive (the one that replaced the redballed drive) was no longer accumulating "writes" and the "errors" drive was accumulating errors. I hope this makes sense. I stopped and tried again. Same thing. Right around the 3% mark, the redballed drive stopped accumulating writes and the other drive's temp was replaced with an asterisk and it was reporting errors. When I refresh the GUI, the errors keep mounting, and the redballed drive is no longer being written to. At this point I realized that a lot of my drives were running really hot. So I looked at my fan situation and tried to improve them (I had moved recently and some of the fans in my case had become unattached to their anchors). I tried my rebuild again, and overall temps were reduced by about 8 degrees per disk. That was an improvement, but unfortunately, the same thing happened again. I have attached a screenshot of my GUI and also my syslog. I am going to stop the current rebuild. It is currently at 405GB (7%), but the red-balled drive isn't being written to and the only thing that seems to be happening is the errors for the green-but-troubled drive are ticking upwards. I need a plan. What I would give to get out of this without losing data! Please help if you have any ideas. Serversyslog.txt

Thanks everyone! The --rebuild-tree has completed and the drive seems to be healthy. I ended up with about 130 orphan files, but I'm pretty confident I can figure out what they are and where they go when I have the time. I'm currently running a parity check. Thanks again!

Thanks for teaching me that!

I am hoping that someone could take a look at the attached PNG and help me understand the results and perhaps advise with the next step (I can't copy & paste from the command interface in Windows, sorry). EDIT: It seems that because it is suggesting that I use the --rebuild-tree command, that I should follow the instructions found in the Wiki, right? From the Wiki: Sorry for my caution--I just don't want to make a stupid mistake, and I know all too well that I am capable of doing just that. Thanks!

Brilliant! I should have known I would have gotten something like that wrong. Thanks so much.

(My understanding of all of the below is a bit shaky, so bear with me if I use some terms incorrectly) My Unraid (v5.0.4) has 20 disks and five shares. Two of these shares ("Edit" and "Files") both have disk7 (a WD 6TB drive) as part of their shares. Neither of these shares will allow me to write to them. My syslog (attached) seems to indicate that disk7 is indeed the culprit: Mar 25 22:06:58 Server shfs/user: shfs_mkdir: mkdir: /mnt/disk7/Edit/Eliminators/Eliminators Titles (5) Input/output error Mar 25 22:06:58 Server kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 3942 does not match to the expected one 2 Mar 25 22:06:58 Server kernel: REISERFS error (device md7): vs-5150 search_by_key: invalid format found in block 322254819. Fsck? Mar 25 22:06:58 Server kernel: REISERFS (device md7): Remounting filesystem read-only I went into Maintenance Mode and tried to run reiserfsck check on md7 via telnet. However, when I get to the "Do you want to run this program?" prompt and answer "Yes" I receive this: Failed to open the device '__check/dev/md7': No such file or directory Strange (or maybe not strange) sidenote If you notice, you will see that there are two underscores in front of check in that command line above. Despite all the instructions that I found seemingly using two checks (reiserfsck --check/dev/md7), that never worked for me and only brought up a large menu of commands. Only when I used "reiserfsck __check/dev/md7 " did the "Do you want to run this program?" prompt come up. I'm not sure what to do next? I'd really appreciate if anyone could offer me some guidance. Thanks so much. syslog.txt

Sooooo I suppose my syslog shows nothing amiss.

Hello! We have a few Unraid builds in our video post-production office and are having problems with one of them. Our office is a mix of Mac's and PC's, and the issues seem to be happening across all of them. The issue is when we are copying or reading large files from the server, the speed will slow dramatically at a point, and then we will lose the server connection altogether. Our other Unraid boxes are fine, it's just this one that's giving us problems. We recently replaced a bad disk, but we were having problems before that. I've never been able to read a syslog and make any sense out of it. I would really appreciate it if someone could take a look and let me know if there are any obvious issues. Thanks so much! syslog_Tower2.txt

Thanks trurl and Fireball3 for the help. Turned out that the flash drive was corrupt. The Windows checkdisk fixed the issue. Thanks, trurl!

Unraid v5.0.5 I had reason to have my office's Unraid powered down for about a month. I'm now trying to get it back online and I'm having a problem connecting. I can access the WebGUI fine via all of the connected computers, but no machine on my network (a mix of Windows 7 and Mac computers) can connect to the server share. I "disconnected" the mapped network drive and have been trying to map it again. Each time I get this message from Windows: The mapped network drive could not be created because the following error has occurred: An unexpected network error occurred. When I type \\Tower into the Explorer window, I get the following message: \\Tower is not accessible. You might not have permissions to use this network resource. Contact the administrator of this server to find out if you have access permissions. An unexpected network error occurred. Here are the things I have tried to no avail: -In the SMB settings, set the Local Master to "Yes" -Rebooted everything several a lot of times -Renamed the server from "Tower" to "Tower2" -Even though this problem is pervasive on all my machines, I edited the hosts file on one of my Win7 machines per the troubleshooting guide to include the 192.168.x.y.<tab>hostname edit This is my second of two Unraid boxes on my network. The first one is up and running just fine (after being offline just like the problem server for about a month). There is no hostname conflict between the two servers, in case you are wondering. They each have unique hostnames. I've attached my syslog. I clumsily created it by copying all of the text in the WebGUI and pasted it into Notepad. Thanks for any and all help! syslog.txt