Jump to content

electron286

Members
  • Content Count

    174
  • Joined

  • Last visited

Community Reputation

1 Neutral

About electron286

  • Rank
    Advanced Member
  • Birthday 09/27/1961

Converted

  • Gender
    Male
  • Location
    USA
  1. electron286

    6.6 - USB BOOT DRIVE FAILED

    yes, and true, I guess I was not really seeking a solution to my situation, as much as wondering if anyone knew if new keys could be used o old 4.x. And again, now I even say that I realize I really SHOULD have started a new post in the correct place! I guess I am not thinking to clearly a the moment. Two of my servers are now down, both 4.x. The first one is likely a power supply, or motherboard, it died last night, the second is the one I was asking about above, with the bad FLASH, that was running till I shut it down to move it out of the way to work n the the other failed server. So it now has taken the priority for repair. Old hardware both servers have been on-line 24/7 since March 2013, both were OLD hardware before I ever put unRAID on them!
  2. electron286

    6.6 - USB BOOT DRIVE FAILED

    Thanks, just where my mind was at. Just started puting 6.x on a new FLASH now. Will see if it boots in a little bit. I will probably take the opportunity to update to 6.x if the hardware is 64-bit, Now have a 6.x server running and verified for my uses, and another in a test configuration. I just had no reason in the past to take down this old 4.x server, and a few reasons NOT to go to 5.x. I have made quite a few install backup sets of various versions of 4.x, and 5.x however, if I needed to move to 5.x now.
  3. electron286

    6.6 - USB BOOT DRIVE FAILED

    I realize I should start a new topic probably... but... I have a FLASH that I just found is DEAD, I could not read from it, so I attempted to re-boot the server, only to find there was no way to boot anymore. 😞 Tried looking and changing the BIOS settings, NO FLASH, moved the FLASH drive to another computer, NOTHING, no flashing light to even try to be recognized it is toasted. It is very straight forward to fix this with the new 6.X platform, get a new flash, put the old key on it, etc... My problem is a little different. I was still running 4.x on this server... I am not sure if it is even 64-bit capable, since I was not upgrading I did not worry about it. I should be able to still put 6.X on a new USB FLASH drive, put my old KEY on it, since I have LOTS of backups of my keys, (just not my full configuration files, sadly), and get a new key for my new FLASH. BUT, IF my server is NOT 64-bit (of course I could get the key on another computer that is 64-bit), will I be able to use a new FLASH with NEW KEY, on the older 4.x software, and use it as I had in the past? Of course, I expect I will need to check or re-build parity to be safe, but that is minor compared to bringing my server and data back on-line. Again, sorry for not making a new post, but I thought, (probably wrong to think at the moment), that since this post was new, people may already be in the right frame of mind for this challenge and question. Thanks for any responses and ideas. I will also start doing some testing, and hopefully may have everything running again by the time I check for a reply.
  4. electron286

    User Share Copy Bug

    Yes! :-) Thanks! Just what I was looking for! I think that was the last thing I felt I needed before full deployment!
  5. electron286

    Looking for suggestions for upgrade to 24 or more drive server

    If I read your configuration correctly, it sounds like you are running 1 cable to each expander chassis. It is hard to tell from the pictures in the post, but it looks like, and from the text in the post also indicates that there are only 2 ports on the expander chassis you have. I might suggest just changing your chassis to one with FOUR ports to use for the linking. 2 Cables from your 9207-8e, to the input of the first new chassis, and the output ports on the new chassis to any additional external chassis... The types of chassis I am talking about use the combined bandwidth of the two cables to increase the available data transfer speeds. You can look at used 16, 24 and even 45 bay Supermicro chassis that are often listed on eBay and other places. Such as the series that use the Supermicro CSE-PTJBOD-CB2 power board, like the 837E16-RJBOD1. One seller of used equipment is usedserversoutlet, AKA Tams. I have NO affiliation with them, but they are in my general area, so I often buy some of my toys there. You also may opt for a larger all-in one server chassis, to again increase the data bandwidth per drive without needing to go to an external chassis, but it sounds like you have good reasons to NOT do that.
  6. electron286

    Supermicro JBOD Chassis

    There are many people using Supermicro servers now with Unraid. One of the types of cards often used are the various LSI controllers running in IT or JBOD mode. They are well built and reliable. There are some specific LSI controllers that have little quirks, but most have NO issues at all. The prices used server equipment runs at, is also well worth the try, even if you end up buying a different controller later, even if it is just a different model, usually a good controller can be bought used for well under $100. I can not comment on the m.2 drives, or the 10gb cards, as I have not looked into them, nor used them myself.
  7. electron286

    User Share Copy Bug

    Ok, I have just started to work with 6.x and I was at first confused about why I could not see any disk shares... Found where to enable them after reading up on the "problem" than saw there was a "user share copy bug" I needed to become familiar with. My take on the whole thing, now I have read this thread, I can see where people could get into big troubles by copying files from Disk to User shares and also in reverse. It has always been a potential from what I can see, at least back to the 4.x days. As others, I also ALWAYS sue disk shares to WRITE to my arrays, and often, (always for media players), use the user shares for reading, including in the past, setting the user shares to READ ONLY. On a server others have access to, I also would set DISK shares to be hidden, but set to full READ/WRITE access. Now I have my disk shares working again for my 6.5.3 test server, I am looking for a way to have them enabled, but hidden from other users casual browsing... is this possible with 6.X, or did it vanish sometime between 4.x and 6.x? Also, as some have said, this is NOT a bug really. It is just a misunderstanding of file system operations. Just like you want to avoid recursive loops, unless you are cautious with what you are doing, you really should not be playing around too much with virtual directory structures, again without proper thought put into the potential issues that could result. I think in general the decision to disable disk shares by default was a very good choice. It will help protect the majority of casual computer users, that are more frequently adopting Unraid as a home server solution. At the same time, I do not see that Unraid would be very useful to me, or at least fully meet my needs, without the ability to use Disk Shares! As a side, but related note, I always move files from a networked computer, using the DISK SHARES, (obviously since my user shares are set to read only). I use a combination of Drag and Drop, Command line, and Batch files. If moving a file or sets of files to another disk share, I make copies of the files to the new destination first, then I do a full file comparison of the original and new copies. Then and ONLY then do I delete the original file from the original disk share. I am a bit paranoid about potential file corruption, so I take the extra steps to insure it does not happen while the files are being moved due to memory, disk, or even communication losses. If I am moving a file WITHIN a disk share, to another user share that is also on that disk for example, I just do a simple move as it does not do as much to the file in the process, but perhaps I should re-think that one, as some OSes do more than others at that point.
  8. electron286

    [SOLVED] Windows 10 and SMB

    One of the things that Microsoft did was to disable older networking support, so I had to re-enable the service to allow connectivity with my older computers. There are many things that they do with each major update, to be inline with the new "current" security model. This includes setting networking option to higher security levels, and disabling older features no longer needed, (if you are in an all Windows 10 Networking environment). Registry keys are changed, moved, and renamed to make it harder for remote scripting hacks to work. There are good reasons, but they just do not work for me because I still network my older computers also. I need to do things to allow my Windows 9x and newer computers to all just work together like they always have. Of course then there are also the various game systems, and linux computers too... Windows 10 is like the ever invading army trying to push new methods to force the old fully usable computers to be retired and replaced with newer ones. I have decided with the latest aggressive onslaught, that any new upgrades or replacements definitely with NOT be Windows based as a result. So, with all the changes with each update, all I can say is you need to look into ONE symptom at a time that is impacting your use of Windows 10. Do some searches on-line, making sure to try looking at more recent posts, as older ones for the same type of problem may no longer have solutions that will work for you. You may need to do any number of registry key changes, advanced networking configuration changes, and also re-enable or even re-install a removed service to regain full functionality with other computers. Good luck. I would help more if I could, but each time the changes are different, and take significant time to dig into Windows to find the cause, then the resolution is usually not to bad... And where everyone uses their computers differently, it would not be unusual for you to need different "fixes" than I have needed. If you would like to post a little more about your specific issue(s) I could make an attempt to help you move in the right direction. Also, when looking at posts for solutions, you may want to actually look at the most recent first, and work backwards with all the changes Microsoft keeps making. It may speed up your solution.
  9. electron286

    UnRAID Manual 6 (Downloadable/Printable PDF)

    I always preferred my nice warm Amber monitors over the harsh green ones myself.
  10. electron286

    Upgrade (UK) - older SuperMicro boards?

    Sounds great! For your use, I think you will be much happier with what you bought than you would have been with the old Supermicro Server. I guess I need to look at my old servers and consider making some updates myself. Newer controllers would be a big boost on my Athlon(tm) 64 X2 server for sure. I have always loved how easy it is to upgrade hardware with Unraid, even the older 4.x versions were VERY good I felt, just had to move the drives, and/or cables around to make the array valid there. But CPU, M.B., Chipsets, Controllers, NICs, most everything will work!
  11. electron286

    Server Loses Connectivity with Network

    Just two days ago, I had a problem at work where the USB Keyboard would not work on one of the computers. It worked for initial boot, BIOS, Wndows boot selection (F8), but after that it would do NOTHING and there was no way to log into Windows. The USB Mouse was still happy though. Then I found out the computer had been moved, then hooked back up. I then started realizing that the cable for the keyboard probably had been switched to a different USB port. I looked at the motherboard, and realized that two of the rear USB ports were from the MAIN CHIPSET, and the other 4 USB ports were going to an additional support chip. In this case, it was a driver issue for the add-on chip for the 4 USB ports that the keyboard and mouse were both plugged into. Windows, as pretty much every other OS, loads and uses the drivers it has configured for the hardware on the mother board, INCLUDING ALL hardware that may already have been functional before the OS fully loads. I moved the cable for the USB Keyboard from one of the 4 ports on the add-on chip, to one of the two USB ports on the main chipset, booted the computer again and everthing started to work normally again. This is just one of many times over the years I have seen this type of behavior with USB Keyboards. There are other times, when I have not been able to find ANY USB port on the mother board that would work fully with a USB keyboard always. In one case, I had a multi-boot computer that one USB port set would work with the Keyboard in Windows but not Linux, and the other USB port set on the motherboard would work in Linux, but not Windows! Luckily, this motherboard did also have the PS2 type connections, that worked well in ALL the boot states and OSes that were loaded so all USB keyboards removed and an older PS2 type keyboard installed. I have also seen more issues with USB Dongles, than with hardwired USB keyboards. You may also have better results by moving the USB dongle to another USB port on the mother board. I always recommend to, IF USB MUST BE USED, to try to make sure the keyboard is plugged into a USB port connected to the MAIN CHIPSET not an add-on chip. USUALLY this would also mean that you would be wanting to use a USB port on the BACK of the computer, NOT one on the front of the case, or via a USB hub. The trick is which ports on the back are on the MAIN CHIPSET? Usually the motherboard manual can help you out to know which USB ports are on which chip... As a side, but related note, I have also seen better compatibility with USB keyboards with INTEL chipsets and associated drivers (including BIOS), than with other chipsets. I have not paid attention to USB DONGLES and chipset compatibility, as I really try to avoid them unless absolutely needed, and then I usually try to still have a hardwired keyboard there also as a second keyboard for when the dongle does not work... It does seem, from what I have encoutered, that the USB Dongles usually have a better chance of working well AFTER an OS has loaded and taken over than in the pre-OS environment with the BIOS drivers running however.
  12. electron286

    Server Loses Connectivity with Network

    Sadly, I have also had some new big name power supplies that were bad out of the box. It does not happen often, but it does happen.
  13. electron286

    5 minutes to boot

    hat22, It looks like you have a Gigbyte board... G41-ICH7-6A79PG0WC G41M-Combo FB 1st, I would go into your BIOS settings, and under your "Advanced BIOS Features" screen near the bottom you will likely see a setting called; "Delay For HDD (Secs)" Change it from the default setting of "0" to the maximum of "15". This will allow the BIOS to wait before attempting to send commands to the hard drives to initialize the communications between the chipset and the drives. This will insure the drives are fully ready to talk, unless there is a real problem. 2nd, if not already enabled, also enable "HDD S.M.A.R.T. Capability" on the same screen. 3rd, MAKE SURE THE "Backup BIOS Image to HDD" feature is already "DISABLED" - IF NOT YOU MAY WANT TO STOP HERE FOR A LITTLE BIT AND RESEARCH THE NASTY FEATURE AND THE HAVOC GIGABYTE HAS CAUSED US UNRAID USERS BECAUSE OF IT!!! 4th, press F10 to save... (this may not be needed here, but some BIOS versions require you to save before moving to antother screen to not loose the settings you just changed.) 5th, after looking to see of anything else needs to be changed anywhere, esc to leave the BIOS setup screens. It looks like there is a problem with the hard drive on ATA2 to me. The above steps MAY have helped, with the added delay for the hard drive to perform power up diagnostics before the mother board starts asking for responses. Another possibility could be as easy as a loose connector/bad connection. So I would next unplug the cables, then plug them back in to see if it makes any difference. You could also move the cables between drives and ports on the mother board to identify a bad cable or port on the mother board. In the BIOS settings again, you can also DISABLE any unused ports to make sure they are not also checked during POST. This can speed things up some. You can do some quick tests also by unplugging all the drives, and seeing how the system POSTs then try ONE drive at a time with additional POST time tests. You can either unplug the Unraid FLASH drive during these tests (suggested), or power off the computer after the DMI POOL has been checked when the Lime Technology Boot Selection Screen pops up. You probably should do a quick SMART test on all the drives after Unraid is booted. Then you can see a little more than the normal SMART reporting will show. A long test may also be advisable for the drive that seems suspect. If all else looks good, you may want to replace the drive, and rebuild the data on a new one.
  14. Pretty cool if you can also still use the keyboard. I do not think I could make myself do that, I love my Atari computers too much. Plus many of my Atari computers also have been upgraded with RAM and other upgrades. :-) ok... sorry for the off-topic
  15. electron286

    5 minutes to boot

    I would hook up a monitor to the server, and watch it. Then you can see what is actually happening during bootup, POST, etc. If you would like to make a detailed list of what happens, including times for each phase of booting up to the point the console login is presented. Then after that how much time before the web GUI is available on a networked computer. After that we can see what we can talk about to possibly speed things up. The time you are seeing may be NORMAL for the hardware you have, but there may be some settings that could speed some phases up.