ct1996
-
Posts
46 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by ct1996
-
-
Hello, I ordered 3 new hard drives, 1 to replace a failing one and two for upgrading storage.
Replacing the failing one provided no problems, I did it by itself before adding the two new drives.However, when I went to add the other two drives, the server would turn on / run, but unraid was not accessible. In addition, it seemed like whenever both drives were connected, the server didn't "properly start up" - for example, when I clicked the power button on front, it instantly powered off with no beeps. When the server is running properly, it has a few beeps and takes maybe 30-45 seconds to actually turn off when you click the power button.
So, I tested each Cable and Drive independently, and everything was fine. I plug in Drive A with Cable A, server starts up, WebUI is accessible, new drive exists. Same story when I plug in Drive B with Cable B. So both cables and drives are proven to be OK. However, when I plug them both in at the same time, the server does its weird "improper" startup, and WebUI is inaccessible...
Frankly, my case is an absolute mess of cables and stuff, so i'm not sure where exactly Cable A and Cable B source their power from. I *THINK* one is on the sata rail, and one is on the molex rail, but they both might be on the molex rail? (Using Molex->Sata converters) Is it possible i'm overloading the molex rail? (I know the PSU itself isn't overloaded, I run at ~250Watts peak and I have a 450W PSU)
I don't know what to check, at this point, lol. Any advice would be greatly appreciated.. -
Hey, I added two drives to my server today... However, when I booted it back up, I only saw one drive. So I powered off again, changed how those two new drives received power, and tried to boot back up to see if that fixed it. However, when I booted back up, I was no longer able to connect to Tower//, and after a few restarts i'm still not able to connect to Tower//, which means I can't bring the server online or do anything... Any suggestions?
Update:
I used a cheap, MOLEX - to - 2SATA splitter, and for some reason, even being plugged into the system prevented it from booting. Who knows why. -
Hope this is allowed, bump. Still not sure how to approach this issue
-
Hello, I installed my UPS a few months ago and everything was fine up to a couple weeks ago. Ever since I get a bunch of errors stating that communications has been lost, and then restored, over and over.
I have attached my diagnostics as well as a photo of the errors popping up. I also receive tons of emails with these errors.
Please advise? Do I need to send the UPS back?tower-diagnostics-20181206-0300.zip
Update:
I recently added another small power-draw to the circuit my system was on. After removing this, all the symptoms of the UPS and the other gaming PC I had on the breaker, disappeared. -
Hello, my system just ran a parity scan and came back with 3022 errors. I have not ran a parity scan since it had an unclean shutdown. Parity is now valid, and everything seems good to go.
Just wondering if I should be worried - a search led me to a similar post about a person tripping over their power cord and shutting it off, causing these errors.Thanks all. (And i've invested in a UPS, haha!)
edit: added diagnostics
-
Updated this docker and experiencing lots of problems now. WebUI shows speeds as 'udnefined', and lots of stuff (eg, torrent name, size, etc) are all blank.
Removed the docker/reinstalled, Tried again with additional step of deleting all appdata for qbittorrent, problem persists... Not sure what else to do. -
3 minutes ago, johnnie.black said:
You can ignore those errors, it's because SAS drives don't spin down, it's a current known issue.
You can also disable spin down to get rid of them for now.
Well, such is life. They are spun up 24/7 for seeding anyways. Only the parity I really care about and it sounds like ya'll are doing what you can.
Thanks you and the other poster for time. Have a good night -
28 minutes ago, saarg said:
If you have it now, then run the diagnostics and post the zip here.
Sorry folks, i'm realizing now just how bad my original wording was. I really do apologize. The diagnostics above is exactly what you've stated, I just personally felt it didn't contain much because the error is spammed every few seconds and has been going on for an unknown amount of time. I don't know how to get logs from when the error begins because I don't know exactly what is causing it, or when it starts. (thats what my terrible wording was trying to imply)
Edit:
I have confirmed its related to spinning the disks down. I set default spindown delay to 'Never' and my log is silent. So, i'm guessing the errors occur somewhere around 20mins after unRAID starts. Lol!
I use this RAID controller: SAS9201-8I LSIPerhaps it is related to my issue. The only drive i've ever sucessfully seen spin down is one of my SATA drives, which obviously isn't on the controller. What a bummer if it is related...
-
Sorry if I was unclear johnnie.black, the errors are currently being spammed in my log. I just said they're useless because they've been spammed for an unknown amount of time, and so the only info in there I copy-pasted in my post.
I'll assume you already know know this and i'm being dumb, so after the next reboot i'll post back with a new log (before/after, just to be safe)
-
Sep 12 23:42:26 Tower kernel: mdcmd (183756): spindown 7
Sep 12 23:42:26 Tower kernel: md: do_drive_cmd: disk7: ATA_OP e0 ioctl error: -5
Sep 12 23:42:26 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Sep 12 23:42:28 Tower kernel: mdcmd (183757): spindown 0
Sep 12 23:42:28 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Sep 12 23:42:28 Tower kernel: md: do_drive_cmd: disk0: ATA_OP e0 ioctl error: -5
Sep 12 23:42:28 Tower kernel: mdcmd (183758): spindown 7
My log being spammed over and over with this junk.
Varies between Disk 0 and Disk 7.
Disk 0 is (I think) my parity drive - seems to be working great (no smart errors..)
Disk 7 is my 7th disk, (of course!), and it also.. *seems* to be working good? I have space settings set to fill-up, and disk 6 isn't full yet so I haven't really been able to check its performance.
Only similarity between these drives is their lack of use (I am writing to my cache pool so parity isn't necessary, and disk 7 isn't up to bat for storing data yet)
So it seems like unraid *wont* spin these disks down?
I don't really care, just curious why/what's going on. Most of my disks are spun 24/7 anyways.. but these two should be spun down I think.Edit:
I added diagnostics but they're probably useless. I restarted my unraid box yesterday and within first few mins of booting didn't get these issues. (So restarting and getting new logs probably won't help, either.)
Any advice? -
1 minute ago, itimpi said:
That is not the Min Free Space setting - those is the utilisation warning settings. The Min Free Space is a size value (e.g. 20G) and is recommended to be more that the largest file you are likely to write.
Ah, I dug around and found the setting under Global Share settings. It is at 20GB, i'll change that to 90GB when I stop the array next 🙂
Thankyou for the advice -
1 minute ago, itimpi said:
What do you have set for the Min Free Space for the cache drive? When the free space drops below this value then Calibre will stop writing new files to the cache drive and instead write them directly to the array. This may impact performance for such files as they are now constrained by array write speeds but should at least keep things under control.
They were previously at :
Warning disk usage: 99%Critical disk usage: 100%
That was probably the issue. I set it Warning: 80%, Critical: 90%, hopefully that is much safer!
-
17 hours ago, johnnie.black said:
You won't be able to restart while a balance is running, do it when it finishes.
You can stop the mover by typing:
mover stopThanks a bunch for your help. The unraid box is now up and running again perfectly. I didn't even have to restore appdata or do anything, just a restart after mover/balancer ran fixed everything. You're the man!!
Is there any way to prevent this happening again? Or should I just be extra careful to not let my cache drive pool get full? -
31 minutes ago, johnnie.black said:
All the syslog files are filled with the same repeating error, but the start of the problem is not visible, reboot, use the server for a few minutes and post new diags.
Sorry to be obnoxious - this is with the mover running and that command I just posted also "running" - right? Its safe to restart?
I'm nervous because mover *seems* to be working, and I have some sensitive data i'd rather let finish moving if restarting is gonna mess up my cache (I know how sensitive BTRFS can be)
Edit:
that command finished, its output is : Done, had to relocate 158 out of 586 chunks (log still being spammed however)
Edit2:
Its late, i'm gonna head to bed and try restarting tomorrow. Hopefully it will be fixed, as mover will have ran and the balance is already done. I'm praying a restart fixes it at this point, lol.
Thanks for your help and assistance so far.
-
17 minutes ago, johnnie.black said:
Please post your diagnostics: Tools -> Diagnostics
tower-diagnostics-20180911-0204.zip
I already ran
btrfs balance start -dusage=75 /mnt/cache
hopefully that wasn't a big mistake 😕
-
Hello, I just recently added a 500gb SSD to my cache pool (existing 128gb SSD), and formatted it as JBOD in BTRFS following the outlined procedure. Everything was great, and I had about 580gb available, with the other stuff used by my docker image/appdata .
Anyways, I was downloading a bunch of stuff today and didn't keep an eye on my drive, and now everything is goin' haywire. Currently, only plex and my torrent docker are working OK. Plex does its temp transcoding on the array (I was gonna change this but its whats saving me right now i'm sure lol). And rtorrent doesn't do any writes, so i'm betting thats why it's okay.
I manually started mover, deleted some torrents that i'll re-download later, and now I have about 80gb of free space. My log is spittin' these out like crazy though:Sep 11 01:01:19 Tower shfs: share cache full
Sep 11 01:01:19 Tower shfs: share cache full
Sep 11 01:01:20 Tower kernel: mdcmd (452131): spindown 7
Sep 11 01:01:20 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Sep 11 01:01:20 Tower kernel: md: do_drive_cmd: disk7: ATA_OP e0 ioctl error: -5
Sep 11 01:01:21 Tower kernel: mdcmd (452132): spindown 7
Sep 11 01:01:21 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Sep 11 01:01:21 Tower kernel: md: do_drive_cmd: disk7: ATA_OP e0 ioctl error: -5
Sep 11 01:01:22 Tower kernel: mdcmd (452133): spindown 7
Sep 11 01:01:22 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Sep 11 01:01:22 Tower kernel: md: do_drive_cmd: disk7: ATA_OP e0 ioctl error: -5Trying to update a docker image shows the cache is in read-only (or at least thats what it says)
I really don't wanna restart the server, but will if necessary.. I'm continuing to let mover run, and hoping that's enough.
Anybody with more experience please advise?? I was reading about potentially running a balance command, but not sure if that applies here.. ThanksEdit: Everything broken now. Gonna let my appdata finish backing up then try the balance command - hopefully its OK for a multi drive cache..
-
3 minutes ago, johnnie.black said:
If your copying/paste the command try typing it, some users had similar issues recently where it's pasting extra characters.
Woohoo!! Tons of read activity and the Balance screen updated to show activity!
Thanks
-
Hello, I ran
-dconvert=single -mconvert=raid1in the balance window for my first cache device, and my syslog reported :
QuoteSep 7 14:55:21 Tower ool www[2505]: /usr/local/emhttp/plugins/dynamix/scripts/btrfs_balance 'start' '/mnt/cache' '-dconvert=single -mconvert=raid1 '
However, nothing seems to be happening. No writes / reads to either disk (I just added the 2nd one, shouldn't have any data on it) , and still shows the balance information as RAID1 and available space as 2x my smallest drive. Do I just need to let it do its thing for a few hours or is something wrong?
Oh, I also tried running the balance command again, to no avail.. -
21 hours ago, johnnie.black said:
If current cache is btrfs you can add and change the profile later.
Thankyou. My single 128GB SSD is indeed BTRFS. I will add/format the 500gb and then add those commands you outlined. Thanks for being so knowledgeable about BTRFS! And double thanks for sharing that!! Marked as solved
-
So after some googling I found johnnie blacks post about various formats for cache pool devices, raid0,raid1,jbod, etc
I have a 128gb Ssd that I currently use for docker appdata only.. I transfer data too much/too fast to bother with enabling cache, and having it always be full, and whatever. So I bought a 500gb ssd to supplement and I want to add it to my array, and enable cache.
Do I have to lose the data thats currently on my 128gb? I obviously can back it up (it already is), but maybe was hoping I didnt have to
anyways, is add drive to cache pool, let it format/wipe the new drive (not the old 128gb!!) , and then set the options in both drives to the commands specified by johnnie black, the correct procedure?thanks folks
-
Update, I actually already had SMBV1 disabled, so I tried enabling it. (Through Windows Features menu) Doing so prompted a restart and allowed me to login to the server using my credentials. However, I still do not have write access..
Edit:
Problem solved. My users (in the unraid GUI) somehow got reset to "read-only". Maybe I set it like that for testing. Anyways, I can do writes again.
to recap...
I went into Windows Features (Search "features" in Cortana/Taskbar) , turned on SMBV1.0 and disabled the newer version of Samba (probably not necessary)
And then I just made sure the accounts had R/W access from unraid GUI for the share in discussion, and boom.
Attached a picture and marked the post as solved. Thanks Frank!!!
-
14 hours ago, Frank1940 said:
Not sure if you have one of the Win10 issues or just a more general SMB/Linux user permission problem. (You have the 'generic' Error Message that Windows throws up with all SMB problems.) You might want to start with the general permission problems and see if any of issues discussed apply to you. The way Windows handles logins (sometimes in the background) and the fact that each computer/user can only only log into SMB only once can really cause confusion that stumps even the experts at times.
https://lime-technology.com/forums/topic/25064-user-share-problem/?tab=comments#comment-228392
Next thing to look at is whether you can access the shares in question from any other OS's.
Why didn't you use the 'Docker Safe New Permissions' Tool? This utility is installed by the 'Fix Common Problems' plugin.
Now for the Win10 problem is general. Start by reading these threads:
If those don't help, post back and be sure to include what version of Win10 you are using (1803, 1709, etc) and the variety (Home, Pro, etc.). Unfortunately, Win10 is not a single animal but several quite different ones (in places)!
Thank you for your help Frank, I actually came across that posting while googling and tried it to no avail. I am able to do proper reads/writes on my Macbook, so it appears to be a Win10 problem.. (isn't it always??)
I don't use the new permissions tool because it gave kind of a scary warningQuoteThis is a mandatory one-time action to be taken after upgrading from a pre-5.0 unRAID server release to unRAID v5 or a later release. Select ALL DISKS when performing this one-time action.
and, to be honest, I need to run chmod every few days, due to my torrent docker creating folders that I can't read/write to, which chmod fixes. Probably another issue to address but I just want my write access back on Win10 ?
I read the second post you attached - I believe this is my issue. On my previous install, I had Windows 10 (Pro) installed for months before I used Samba. I'm guessing SMBV1 was uninstalled and then when I tried to use it, a newer version of Samba (SMBv2???) was used instead. Great, flawless, no problems.
However, I reset my Windows10 and used Samba the same night, leading me to the problems i'm in now.
Windows 10 Pro, version 1803
I am going to begin looking at removing SMBV1, please offer any other advice if that isn't the correct direction.
And again, thank you for your help. -
Hello, I reset my Windows 10 PC (Fresh install), and can no longer write to my samba shares. I figured it was because I was not logged in (Guests only have read access), and now i'm stuck at the login menu, and I cannot login as a user or as root. Windows explorer says Access Denied.
I think this might have something to do with me running "chown -R 0777 /mnt/user/Media/" the other day, instead of "chmod -R 0777 /mnt/user/Media", but honestly i'm not sure.I went ahead and ran this : chown -R nobody:users /mnt/user/Media , however still can't login to my private network share. (Set it to private to force credentials prompt)
Please advise ?
QuoteFULL ERROR:
\\tower is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. bla bla bla -
Hi, read some older topics in which it was discussed that Hard linking was added to unraid, but another saying it was planned to be removed...
Wondering if this still works, at least in my usecase?
link TV series from folder /downloads/ to /library/tv/showname , and then rename all the files in /library/tv/showname, without messing up anything in /downloads/(both in same user share)
And of course this shouldn't take any extra disk space, right?
Thanks for your input guys, just hoping this is possible!
Weird behavior with hard drives, not sure if Unraid related.
in General Support
Posted · Edited by ct1996
11 when it is still able to Launch (7 data, 1 parity, 1 unassigned, 2 cache pool) and 12 when I am no longer able to. I just checked my psu (Evga 450 BT Bronze), and its a single rail PSU, so that idea is out the window. My last thought is that maybe I didn't pay close enough attention, and either Cable A or Cable B was used twice, and one of the cables is the problem after all... I'm ordering a Molex-to-SATA power cable that a different community of server builders strongly recommends, hopefully this will fix the issue.. Though I don't know how it could! If it were simply a bad quality cable, I don't know why the server wouldn't start at all..
Edit: With a parity rebuild operation in progress, and two people transcoding Plex, my UPS shows me pulling 280 watts. So I really don't think its an overloading issue...