Whaler_99
-
Posts
618 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Whaler_99
-
-
1 hour ago, itimpi said:
It looks as if a cache drive, disk14 and disk15 all dropped offline at about the same time. Is there anything they share (cabling, disk controller) that needs checking. As a result there is no SMART information for those drives in the diagnostics.
I suggest you power-cycle the server to see if those drives come back online and then post new diagnostics so we can see their state.
Thanks! I did notice the cache drive looks fine, two SDD's, and is available via \\tower\cache, but yes, going to power down and check connections, cards, etc. See if anything common between 14 and 15 and will also check regarding the SSD cache drives. Maybe they are all on the motherboard...
-
Hopefully someone can help with this one. System been fine for months, this morning notice Plex not up. Logged into, two drives red balled. Both showing exact same count of errors, which is weird.
Looks like around 11:38 last night, things went nuts, tons of disk errors and such. It weird though, that two drives fail same time, with same number of errors. Array still up as I have dual parity, but another weird one, docker won't start, like it thinks it all gone as well.
Also, if I got the VM tab, just says no VMs installed... and I do have one VM previously running.
I've attached Diag zip and screen shot from docker screen. I'm assuming either something with the controller or the cables on those two drives, or maybe even the back plane on the 3x5 cage, but I've never seen an issue with that.
-
On 6/4/2021 at 8:04 PM, trurl said:
Just pay attention during parity check to whether you have anything in the Errors column for any array disks on the Main page, and check syslog for any of those ATA errors you were seeing before. If the parity check isn't going well, you can cancel it and try again to fix the connection.
Will do, thanks!
-
<sigh> That's the thing I hate, lol. Fiddle come cables, check connections, but no way to know for sure if it's fixed without running another 26 hour parity check.
Thanks!
-
Can we stay on point here re: parity issues and disconnecting drive?
What IP range I use internally has zero bearing on that. In fact, there is no regulation stating you cannot use ANY IP range you want on your internal network. The IANA reserved some specifically for internal use, but I can use any I like. The only issue I'll ever have is if I needed to connect to a resource on the Internet that was using a 192.169.x.x IP....
-
Has anyone had much experience with these ones:
iStar BPN-DE350SS
http://www.istarusa.com/en/istarusa/products.php?model=BPN-DE350SS
I bought a case with 4 of them installed and been having weird issues. I've had one of the disk backplanes go in one and now having weird disconnect issues in another.
It's strange as I've been running other brands for years, not trayless, and not a single issue, but with these ones, seems weird. I've previously remarked not a huge fan of these as the drives are not completely secure in there, but it's not like I'm moving or otherwise touching the server while it runs...
-
8 hours ago, trurl said:
Looks like a bad connection on parity2.
Why are your IPs 192.169... ? Those are not allowed private LAN IPs.
https://en.wikipedia.org/wiki/Private_network
In fact, it looks like your server IP is actually owned by an ISP in Washington state.
OK, I'll check connections on that drive. Make sure everything is secure, etc. How do I test afterwards though without running another 25 hour parity check?
Just weird it would suddenly happen.... grrrr.....
-
I had to shut my server down due to power issues in my place. The shutdown went fine. Powered up, ran a parity check, non correcting.
Found 16583 errors. Huh? Last month parity check was fine. Nothing been changed or touched on the server in the past month,
Checking logs, I also see issues with ATA12, which looks to be the parity 2 disk, which is pretty much a brand new drive. I'm just wondering what could be causing the ATA errors and the crazy amount of parity errors?
Thanks for help!tower-diagnostics-20210603-2051.zip
-
On 5/18/2021 at 10:51 PM, JWMutant said:
Do you happen to have a link to one you have as the ones I have looked at have no way of mounting it in the case…. As in no screw holes in the side..
Sent from my iPhone using TapatalkAny 5x3 cage is designed specifically for that, for mounting in 3 5.25 slots and will have mounting holes and screws provided.
Also, if you end up mixing various 3x5 cages in a case, keep track of which extra screws you have for each one as some are slightly different threads and depths. -
3 hours ago, JWMutant said:
I think I have narrowed it down to :
https://www.icydock.com/goods.php?id=175
or
https://www.icydock.com/goods.php?id=155
I think the second one being 5 drives "May" have more of an issue with heat than the first.
Thoughts?
Given the same fan, obviously the 4 drive bay will be cooler, much more open. But, the 5x3 is still a great option and one I previously reviewed. Maintains great temps.
Also looked at images of the Vortex, notice the one with the fan moved the side? I don't think you could mount this unit flush with the front of the cage, or you could never swing the fan aside to pull a drive out. You need to have the fan and a small portion of the drive sticking our the front of the case in case you ever needed access to the drives. Overall looks like a bad design.
On a note, I have a similar design 3x2 cage, with that bottom only mount option. But the unit I have is all metal, so it's very sturdy when mounted and the fan is on the rear as well, so access via front is simiple.
-
1
-
-
8 minutes ago, JWMutant said:
I’m using the thermal take WP100 and have heard some people have issues with sag.
Sent from my iPhone using TapatalkAhh, no clue then on that case.
-
9 hours ago, ChatNoir said:
Wow, that one looks scary, lol. But I would say if that bottom piece is mounted with 2 screws on each side, should be more than secure enough. Esp if you have a decent case to bear the load.
3 minutes ago, JWMutant said:Has anyone else had any temp issues with the 5 drive icy dock.
Sent from my iPhone using TapatalkI've used two of the older models of their 5x3 and never had a temp issue. Of course it is highly dependent on ambient temperature.
-
Do you have a link to the product page? I know most of the 3x5 cages I've used a very sturdy and just a couple of screws to secure them in had been fine in many cases. That also depends as well on the quality of the case itself and the frame.
Any of the original 4 docks reviewed are all still great candidates and you can usually find them on a variety of secondary markets at a good price.
-
31 minutes ago, ljm42 said:
Sorry, we are still working through some issues with this beta. Until we get it resolved you may notice the servers go offline / come online on their own. Once it is stable they will stay online.
Sounds good, keep up the good work!
-
1
-
-
I've added three servers into the My Servers dashboard and all are showing offline. I added one just this afternoon. Was showing online... and then just as suddenly, now showing offline along with the two that have been there for about a week. I ran the unraid-api restart command on one, seemed to go through ok, but no change, all servers offline.
And as I glanced back at the My Servers tab, the one I added today is now showing online, again.
Edit - updated plugin on two of them, now showing online, one still offline for some reason.
-
Replaced the two SM cards with the LSI ones I got, also had to replace a cable that was a bit short. Just finished the correcting parity check and found zero errors. I'll now run a non correcting as suggested and ensure there are 0 errors.
-
Noted @itimpi, I'll update the monthly check now to do non correcting. Thx!
-
Thanks @trurl In the scheduler, I have it configured for monthly and the "Write corrections to parity.." set to yes.
I'm swapping the controllers this afternoon, then will run correcting parity check followed by another non-correcting one.
-
I've just recently got some LSI cards in IT mode, so that is what I will work on, swapping out those SuperMicro cards. Hopefully that will bring some stability. All the disks themselves never show any issues any more. That one dropping offline, never shows up on the dashboard. I'll swap controllers and keep an eye on it. Thanks @John_M
-
Hoping some others can take a look at my diag and give me some pointers on what might be going on.
Started off 3-4 months ago, accidently hit the side of the unraid server. This caused over the course of a few days 3 disks to go "bad" showing tens of thousands of errors. Huh... pulled disks out, tested everything ok, removed from config, re-added, recovered data from offsite unit, etc. Got things back to where they were. I also figured out in this time about the file system check, which I also ran on the disks I was having issues with.
Now though, on my monthly parity checks, it's correcting like 10K plus errors (38K+ on the last one). Which I know isn't good. I've run Short Smart tests on all disks. They all show no errors. In the logs, I see though a ton of "exception... frozen" errors, which I'm sure is not good.
Most of the smart reports look ok, other than the two parity disks, probably due to all the corrections. They are both pretty much brand new.
But otherwise, everything runs fine, disk shares are good, VM runs fine, dockers run fine. Just seems to be underlying disk/filesystem/hardware issue I need to deal with.
Thanks for looking and any advice!
-
On 12/28/2020 at 11:44 AM, Whaler_99 said:
So turns out I did update it yesterday, running version 2020.12.27 and backup ran this morning at 1:00 am and still cannot access unfortunately...
Update, last two backups I can now browse into the folder and see the ca_backup.tar files, but still messed up permissions. Cannot copy that file. Weird as the libvirt backup is fine, USB Backup is fine. Just the tower backups are inaccessible...
-
So turns out I did update it yesterday, running version 2020.12.27 and backup ran this morning at 1:00 am and still cannot access unfortunately...
-
13 hours ago, Hoopster said:
I think he means the update of the appdata backup/restore plugin that was released just today to fix permissions issues specifically.
Ahh, got it. Updated it now. I'll see how the next backup works and let everyone know. Thanks!
-
5 hours ago, Squid said:
The update will probably fix you up
Update? You mean the new version of unraid that is in RC?
Two drive fail same time with same error count and Docker error - weird
in General Support
Posted
Cannot shut down server, stuck on "retry unmounting disks share(s)".
I checked the open files plugin, one PID seemed to be stuck, looked related to my VM, the img file was stuck, but the plugin wouldn't kill it. So, SSH in, killed that. Still nothing. Log is full of:
Nov 7 12:34:22 Tower emhttpd: Retry unmounting disk share(s)... Nov 7 12:34:27 Tower emhttpd: Unmounting disks... Nov 7 12:34:27 Tower emhttpd: shcmd (171808230): umount /mnt/cache Nov 7 12:34:27 Tower root: umount: /mnt/cache: target is busy. Nov 7 12:34:27 Tower emhttpd: shcmd (171808230): exit status: 32 Nov 7 12:34:27 Tower emhttpd: Retry unmounting disk share(s)... Nov 7 12:34:32 Tower emhttpd: Unmounting disks... Nov 7 12:34:32 Tower emhttpd: shcmd (171808231): umount /mnt/cache Nov 7 12:34:32 Tower root: umount: /mnt/cache: target is busy. Nov 7 12:34:32 Tower emhttpd: shcmd (171808231): exit status: 32 Nov 7 12:34:32 Tower emhttpd: Retry unmounting disk share(s)... Nov 7 12:34:37 Tower emhttpd: Unmounting disks...SSH in again... try "unmount /mnt/cache" and just get target is busy.
Not sure how to "kill" the cache to get the server to shutdown gracefully....