greybeard

I have a 19 dirve 6.6.6 array. 1 x 8 TB Parity 18 x 2 TB MBR unalligned ReiserFS data drives. 1 empty drive bay. I also have 4 x new 8 TB drives so what I want to get to is 2 x 8 TB Parity 3 x 8 TB GPT alligned XFS data drives. 8 x 2 TB XFS data drives. Don't think it makes any difference if these are GPT or MBR. Pretty sure I can not replace a 2 TB ReiserFS unalligned data drive with an 8 TB XFS allinged drive just by doing a disk swap and rebuild. So here is my idea for how to get converted. Create a 3 x 8 TB array on a spare box. From Win10 system, copy date from 11 of the 2 TB drives to the 3, 8 TB drive array. (The 2 TB drives are all 98% full. I know that is not best practice.) From Win10 system, verify copied data. (I have a way to do this.) Shut down both arrays. Create a new config with Replaced parity drive with a new 8 TB drive. Replaced 3 of the 2 TB drives with the 3, 8 TB drives I copied the data to. Remove the other 8, 2 TB drives, i copied the data off of, from the config. Start the array and build parity. If anything goes wrong with 5 or 6 I am thinking I can restore the original config and original drives and have good parity. Wait for parity sync to complete. Preclear the 8 TB drives I coped the data from and are no longer in the arrary. (Technically I may not need to preclear but planning to do it anyway.) Stop the array and add the precleared drives. Start the array. Copy data from remaining 7, 2 TB drives to the now empty 2 TB drives. Verify copied data. Shutdown the array. New config. Replace the new parity drive with the old one. Remove the 7 old 2 TB drives from the array. Start the array and build parity. Again I should have good parity if I have to revert to the config i have at the end of step 15. Wait for parity sync to complete. Shut down the array. Add second 8 TB parity drive. Start array and let it build parity on the second parity drive. Do what ever I want with the 7 old 2 TB drives. Maybe preclear and add some back to the arrary to have more free space. Will probably take a month or so to complete all steps but when done I should be able to replce any of the 11, 2 TB drives still in the array with an 8 TB drive and get an XFS alligned partion after rebuild. Thoughts? Pitfalls? Other ideas? Thanks for taking a look.

Like most I voted for 16b. However I think there should be consideration given to staying with the reiserfs patch, even for 5.0 final. The patch has been very well tested. Changing to the official fix would require rigorous testing and, who knows, might not even work. So for 5.0 I would suggest staying with what has been tested and works.

The Upgrade Instrucitons for release 5.0-rc8a and older do not say anything about copying the syslinux.cfg file to the flash drive. Am I correct to asusme that is only because the instrucitons have not been updated and I really do need to copy it?

Keep in mind that the code is for $15 off an order not a per drive discount.

Using version: 5.0-rc6-r8168-test with C2SEE I was getting inconsistent response times when clicking on things in the web interface. Worked fine for a few minutes then got a 15, 20 second or longer wait before a response. I finally got tired of all the problems with the built in nic and decided to follow the advise so often given in these forums so I purchase this. http://www.ebay.com/itm/Intel-PWLA8391GT-1000Mbps-Desktop-PCI-Network-Card-NIC-/150592466899 Installed it and now my web page response is 100% consistent. After a few days of testing I have not once had any delay in web page displays. I suppose I will need to add one to my two primary systems before converting them to 5. Only mistake I made was not moving the on board jumper to disable the built in nic. Apparently unRAID uses the first nic it sees so it kept using the realtek instead of intel. After cracking open the case and moving the jumper all was good. On the C2SEE it does take moving a mobo jumper, can't disable it from the BIOS settings.

There have been quite a few posts over in the 5 beta threads stating there is a real need for NFS and AFP. Maybe I can understand AFP for Apple users but I am more puzzled why there is such an urgent need for NFS. I have been running 4.7 with 20x2TB drives using SMB for a long time. Never have a problem finding the shares from my Windows machines, get 100m read speads, typically 35-40 write (no cache drive). So why do I need NFS?

I used a Logitech Cordless MediaBoard Pro for PS3 in an HTPC I gave to one of my kids for Christmas. They tell me it is working great, when they need to use a keyboard. Two things. 1. It does not come with a bluetooth receive. You need to get one somewhere else. Extra $5. 2. Can't use it to get into the BIOS and make changes. Need to hook up a wired keyboard to do that. Also gave them a Media Center IR remote that they use most of the time. Media Center is started at boot up, and they rarely leave it. TMT5 for Blu-ray and MyMovies for catalog/menu. I know it says it is for a PS3 but works great with PC. Lot's of feedback at the egg, most seem to be using with a PC. It is a full size KB with track pad. All the keyboards I researched that have a joy stick or track ball got considerable worse feedback.

Do you have any 2 TB Samsung F4 HD204UI drives in your array? If so, has the firmware been updated? Could be completely unrelated but is something to check.

Not sure I would say that it is recommended. From what I have read it is either compatible with your main board and works fine or it's not. There is no inbetween. The evidence seems to suggest that if there is an JMB controller on the main borad you chances of this card working drops dramatically. So, unless you can find a post that confirms it works with your main board you spend your $9 (price went up) and take your chances. I have several of them working just fine in both unRAID and Windows systems.

More goodness. I have a new build with three Hitachi 3TB cool spin drives. One on a mobo port, one on an MV8 and one a JMB card. Newly configured flash drive. First started testing with beta 9 and had some of the problems report in these threads. Just updated to beta 12 and everything I have tried (not that I tried a lot) is working perfectly. Web interface is snappy (wasn't in early tests) and a parity check started running at 117MB per second. Of course that will drop as it gets further into the drive. So, for now, things are looking really good. I will do some more experimenting and post the results. 15 bay box with C2SEE - E3400 - Kingston KVR1333D3N9K2/4G DDR3-1333 SASLP-MV8 and JMB PCI Express Hong Kong special. CORSAIR CMPSU-750TX I really hope that this means it is getting close to the end of the beta cycle. A stable 5.0 official release would be a great thing. I too have to thank Tom for all his hard work and everyone that has been testing these betas.

Looks like Supermicro is updating the AOC-SASLP-MV8. I don't see it listed yet at the sites I normally buy from so I don't know what it is going to cost. Key Features • 8-channel SAS/SATA adapter with 600MB/s per channel • PCI-E x8 interface • JBOD mode only. No RAID support • Dimension: 6.6" (length) x 2.7" (width) More details here: http://www.supermicro.com/products/accessories/addon/AOC-SAS2LP-MV8.cfm

I have been experiencing this behavior for a long time, have read other posts describing similar behavior and finally learned enough to have an idea what might be causing it. First, I am assuming unRAID is using ReiserFS v3. I have not learned enough to know how to check that but have read it is v3.6. If it is not v3 then the rest of what I am going to write is kind of useless. Ok, the problem: When a disk is getting close to full, somewhere above 90%, copying a file to it will often cause an initial pause of 20 seconds or so during which time the light on the data drive flashes continously. Only the data data drive, not the parity drive. Some times Windows will get tired of waiting and time out, resulting in an error. After the initial pause, the copy works fine, unless... There is other activity on the system, for example a preclear. In which case a block of data will be copied after the pause (parity drive light flashes for the actual data copy) followed by another pause, flashing data drive light, of the same duration as the first one. This repeats and repeats until the file is finally copied. A 500m (yes meg) file has taken an hour to copy in this situation. My theory: Based on research and observation I have come to the conclusing that what could very likely be happening is free space bitmap searching. When nothing else is running the bitmap is cached so there is only one pause, however if there is other activity, the cache gets purged resulting in another read of all the bitmaps spread across the partition. My question: Again being a UNIX newb I am wondering if someone can tell me if the patch described by this post is part of the unRAID distribution? It seems to describe exactly what I am experiencing although I never checked the CPU utilization (that newb thing again). Thanks for any feedback. Jerry http://www.mail-archive.com/[email protected]/msg21592.html

Interresting subject. I signed up for a 2G account to checkout SpiderOak and kind of like it. However I would suggest that security on the share funciton is not nearly as good as it could be. I posted the following to the SpiderOak features request forum and am repeating it here, instead of providing a link, because their forums don't seem to allow public access. I think you have to have a SpiderOak account just to view. Here is what I wrote. I setup an experimental share to get experience with how it works. In the case where I want a share to be truly public, giving out the URL is a nice solution. However if I want to keep a share semi private, where only friends a family can see it, there is a risk. I can tell friends what the Share ID and Room Key is along with instructions to go to spideroak.com and use the share login but the result is the same URL as if I had sent them a URL. Now if all my friends and family were computer savvy folks and understood that the URL need to be protected to keep unwanted people out, that might not be a problem. My fear is that after logging in the URL will remain in browser history or be unwittingly published in a public forum thus exposing my data to the whole world. It would be a great security feature if there were some way for me to configure a higher security share that always forced family and friends to use the Share Login process. I would expect that clicking on a saved or historical link to the share would display a Share Login screen. I completely understand why you would not want all shares to work this way but it would be a really nice option. I also realize that my friends might give or post the Share ID and Room Key other people but that would be deliberate vs. accidentally disclosing the URL. And giving out the Share ID and Room Key would not expose the share content to indexing by search engines. The most secure option would be to allow a share to only be accessible to a specific list of other registered SpiderOak customers. Combine that with a feature to let those customers automatically download updates (kind of like a read only one way sync) to their system and SpiderOak would be an even better product. An option to restrict share access only to other customers would, in my mind, also be an acceptable alternative to always forcing a Share Login as I described above and could be a way to get more people to signup.

I had a similar problem. 30+ days, no cards. I finally found them sitting at the post office waiting for us to pick them up. The USPS claimed to have tried to deliver them but did not leave anything telling us that. For four cards a signature was required so they wouldn't just leave them in the mail box. This sort of thing happens all too oftern with our local post office. It is incredibly anoying. The seller did offer to refund before I found them but I told them to wait until I did some more checking.

Hope this helps. If you can find a flash chip, you have better eyes than I. Also scanned at 1600 dpi but the file is 21M. The back has a few more capacitors and resistors but that is it. From the 1600 dpi scan I was able to confirm it is in fact a JMB362 chip. I believe the ROM is built into the JMB362.