Jump to content

mgranger

Members
  • Content Count

    147
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mgranger

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Love being able to add/replace disk easily and safely Would love to see better parity on the cache drive. The btrfs does not seem to work well with samsung ssd
  2. I am not able to login anymore. This is what i am getting in the log Starting Shinobi ... 2019-12-26T02:46:55: PM2 log: Launching in no daemon mode 2019-12-26T02:46:55: PM2 log: App [Camera-App:0] starting in -fork mode- 2019-12-26T02:46:55: PM2 log: App [Cron-App:1] starting in -fork mode- 2019-12-26T02:46:55: PM2 log: App [Camera-App:0] online 2019-12-26T02:46:55: PM2 log: App [Cron-App:1] online No "ffbinaries". Continuing. Run "npm install ffbinaries" to get this static FFmpeg downloader. No "ffmpeg-static". Available Hardware Acceleration Methods : cuvid Shinobi : cron.js started FFmpeg version : 3.3.4-static http://johnvansickle.com/ffmpeg/ Node.js version : v8.16.2 Shinobi : Web Server Listening on 8080 2019-12-26T02:46:57+00:00 Current Version : c943eedddcc441832b82767137816085f5d83443 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! This Install of Shinobi is NOT Activated !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2019-12-26T02:46:58+00:00 This Install of Shinobi is NOT Activated !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! https://licenses.shinobi.video/subscribe 2019-12-26T02:46:58+00:00 common@mgranger.com : Checking Disk Used.. 2019-12-26T02:46:59+00:00 common@mgranger.com : /opt/shinobi/videos2/ : 0 2019-12-26T02:46:59+00:00 Starting Monitors... Please Wait... Edit: After waiting a couple of hours it seemed to let me login so I think it is back to working now.
  3. I typed this in and this is the warning that came up. Should I delete the log?
  4. I would also like this. I am fearful to add more disks to my array because they will be in my array forever (unless i break my parity to remove them) Then I will have that many more disks in my array that could fail at some point. Nice feature to have.
  5. So the drive i took out of Drive 5 was a 4TB HGST drive. I have it in the unassigned devices now but it is refusing to mount. Is there a reason that this is happening? I figured I would be able to mount it using UD. I think I can reformat it now that the other disk was rebuilt but just trying to troubleshoot why this would happen.
  6. Ok the rebuild just finished. Here is the diags. I think it is ok but just want to check. I am guessing i will get read errors shortly but I guess I will just run the server until that happens. My new cables are supposed to come on Friday and I will be replacing the existing ones then. Will just have to troubleshoot from there. finalizer-diagnostics-20191204-1736.zip
  7. Well maybe this answers something. I was doing a rebuild on Disk 5 (new disk but same slot) and I got more errors on the parity and Disk 4 and Disk 3. This makes me think it has something more to do with a cable, backplane, or HBA. I have 2 power supplies so I hope it is not the but I guess it is possible. I am going to let it rebuild Disk 5 then probably shut it down until I can get new cables unless there is no risk of corrupting the data? Before I tried rebuilding the drive I tried to check all the connections to make sure they were tightly connected.
  8. Any advice on the best way to troubleshoot this? I don't really have any extra of anything to start troubleshooting with a new component. Wouldn't other disks get read errors if it was a cable or HBA issue?
  9. Last night I moved all my hard drives over to a new server I built. I finally upgraded to a chassis that has 16 bays and connects to the backplane with 2 SAS cables. I bought the chassis off ebay used but the cables were new. I have been reading that most of these errors are fixed with new cables but this a brand new cable so I hope it is not that and it would seem like it would be more than just disk 5 with errors. I will post my diagnostics but some advice would be much appreciated. I have already rebuilt disk 5 using the same drive and same spot in the chassis. I am hoping it is not a bad spot in the chassis. I noticed the drive showed up in Unassigned Devices while being spun down in the array and then shortly after I got the read error. finalizer-diagnostics-20191203-1855.zip
  10. I am upgrading in a few days so I guess once that happens I won't worry about it. Just wanted to make sure I was safe until then. Thanks.
  11. Well maybe i spoke too soon. I was getting errors where my sever could not be accessed when I woke up in them morning so I have been doing some searching online and noticed that this could be due to having 2 cache drives (both of mine are the samsung evo which could also be an issue) so I tried removing one from the settings but when I did this I know got another machine check event error. I am attaching my diagnostics finalizer-diagnostics-20191128-1438.zip
  12. i have also been having my server locking up in the morning lately. i have recently put a second SSD in my cache in the BTRFS format. here is on of the diagnostics i was able to grab before i shut the computer down. finalizer-diagnostics-20191122-0449.zip
  13. i am now getting this error. is there something i need to fix? 2019-11-26 17:38:32.630108 INFO AppDaemon Version 3.0.5 starting 2019-11-26 17:38:32.630249 INFO Configuration read from: /conf/appdaemon.yaml 2019-11-26 17:38:32.631356 INFO AppDaemon: Starting Apps 2019-11-26 17:38:32.633425 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin 2019-11-26 17:38:32.711857 INFO AppDaemon: HASS: HASS Plugin Initializing 2019-11-26 17:38:32.712072 INFO AppDaemon: HASS: HASS Plugin initialization complete 2019-11-26 17:38:32.712225 INFO Starting Dashboards 2019-11-26 17:38:32.712337 WARNING ------------------------------------------------------------ 2019-11-26 17:38:32.712393 WARNING Unexpected error during run() 2019-11-26 17:38:32.712447 WARNING ------------------------------------------------------------ 2019-11-26 17:38:32.712884 WARNING Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/appdaemon/admain.py", line 82, in run self.rundash = rundash.RunDash(self.AD, loop, self.logger, self.access, **hadashboard) File "/usr/local/lib/python3.6/site-packages/appdaemon/rundash.py", line 130, in __init__ dash_net = url.netloc.split(":") TypeError: a bytes-like object is required, not 'str' 2019-11-26 17:38:32.712939 WARNING ------------------------------------------------------------ 2019-11-26 17:38:32.713005 INFO AppDeamon Exited
  14. Thanks @johnnie.black Everything seems to be back to normal now. I switched the bay the hard drive was in (different cable) and that seemed to fix it for now.
  15. I am now taken to the IP address I put in but nothing comes up. I get an error that the site can't be reached.