Joe L.

Upgrading from 5.0.6 to 6.0-rc4. Many small issues... First, "failed to load COM32 file menu.c32 when I first attempted to boot my flash drive. To get it to boot I had to copy menu.c32 from the syslinux folder on the flash drive to the root of the flash drive. Then, once that was resolved, it booted and allowed me to see the disk assignment page by invoking //tower after assigning each of the data drives, I get: URL: tower/undefined 404 File Not Found hitting the back button and then refreshing the browser, I see the assigned disk, but at the bottom of the main disk assignment page is: Fatal error: Call-time pass-by-reference has been removed in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(278) : eval()'d code on line 56 After assigning all the disks as they were previously, I'm stuck... I cannot start the array now that I've assigned my drives because of this error, as there are no buttons present to start the array. Help is requested. This is my first attempt to boot on 6.X and I'm not impressed so far with the experience. I can click around on the various tabs in the interface and can get to all the pages... Apparently, it is just the main disk assignment page with the error so far. It appears to me as if going straight from 5.0.6 to 6-rc4 is going to be an issue for some. (I should add I did not completely re-format the flash drive.. I did disable all the packages/add-ons, etc in the config/go script, re-named the packages folder to packages_v5, etc. There was a older menu.c32 in the root directory of the flash drive... perhaps it was confusing syslinux. I did run the make_bootable.bat script from within Windows Vista using "run as administrator" on it before my first attempt to boot 6-rc4.) Joe L.

Ok, understood. Anyway it doesn't "pretend" it so badly at the end... If you install the unMENU "image_server.sh" package, it will serve the images instead of using emhttp. That way they will still be visible when emhttp crashes. yes, it does a pretty decent job of pretending to be a web-server. (had you fooled for a while )

Actually, I run 4.7 on my older original unRID server, and 5.0.6 on the newer unRAID server. unfortunately, the 5.0.6 version crashes on occasion, and the older server is getting quite old... and I'm so busy these days I barely have time to myself to post here. Joe L.

I guess lime-tech removed that file. You might try replacing it with http://lime-technology.com/forum-logo.png (at least that exists) not sure what the original size was, but you can experiment.

it might be because the correct way to supply the "recursive" argument (or any argument for that matter) is cp -r source destination options to the copy command must come before the source and destination directories/file-names

yes, you can do exactly as you stated.

You are wrong. If stopped as described in that link to the wiki instructions, the array will not need to perform a parity check upon restart. The key command is /root/mdcmd stop which you'll only be able to perform successfully after un-mounting all the disks. (those are the first steps in the wiki link) Joe L

I would try running the short smart test before doing anything that would power cycle the disk. type smartctl -t short /dev/sdi then wait for the time it indicates and get a new smart report smartctl -A /dev/sdi followed by the same steps for the long test, waiting several hours or more as indicated when invoked before getting a subsequent smartctl -A report. (Don't forget to disable any spin-down timers, as spinning down the disk will terminate the long test.) smartctl -t long /dev/sdi waiting hours as needed, then smartctl -A /dev/sdi It might have currently stopped responding to read requests, but might start again if power cycled. The actual issue could be with the disk controller OR the disk itself. (That is not a good behavior, as if you cease being able to read a disk it is a very bad thing in any network-storage-device)

I would not use either drive. The first has over 900 sectors already re-allocated (it will not get better with use), and the second is already FAILING the smart test. 184 End-to-End_Error 0x0032 099 099 099 Old_age Always FAILING_NOW 1 Joe L.

Actually, it said "0 bytes copied" so it could not read the disk when it was trying to. Might be fine in operation, but I expect you might want to keep an eye on it. Can you get a smart report on the drive right now? (does it respond at all to read requests?) What do you see when you run this command that attempts to read the disk's first 195 sectors: (it will print, at most, 30 lines of text) dd if=/dev/sdi count=195 | od -c -A d | sed 30q

To mount ANY file system you must have an appropriate driver for that file-system type. It has nothing to do with the version of unRAID. What file-system is your ISO file? It will NOT work with DVD ISO files, as they use a file-system type not supported in unRAID. It will probably work with ISO images of install disks. Basically, you need to create a mount-point (an empty directory) and then use the "mount" command with the appropriate arguments for your file-system type. (and have a driver in unRAID for that file-system type) I have no idea about 6.X unRAID, my server is still on 4.7.

based on the smart report, it is highly likely to be bad cabling to the drive, or cabling picking up noise from adjacent cables. (if you neatly tie-wrapped all the drive cables, you've caused the problem. Do NOT run the cables all parallel to each other or to power cables.) It might also possibly indicate a power supply at its limits, with the power supplied to the drive being noisy causing the checksum errors in communicating with the drive that are showing in the SMART report:

Exactly. That library was accidentally left out of several old 4.4 releases of unRAID. It has properly been included since. unMENU sees it is present even though you did not download it.

Then it indicates your disk is dropping off-line in some way and can no longer be accessed. (either a bad disk, or a power supply that cannot supply proper power to the disk, or a disk controller that is stopping to respond, or a loose cable or connector, or loose drive tray, or back-plane. ) Sorry to say, difficiult to isolate which it might be) Thanks Joe. I think that I am just going to RMA the drive even thought it passes all of the Seagate SeaTools tests. I am using a Norco 4224 case and I have tried preclearing the drive in multiple slots to eliminate the possibility of a bad cable, or PCI-E card with no luck. I was able to preclear an old 2 TB drive just fine so I am suspecting the drive. Better to RMA the drive now, then to have it stop responding when attempting to load it with your data (or fail when using it to recover another failed disk). Joe L.

Then it indicates your disk is dropping off-line in some way and can no longer be accessed. (either a bad disk, or a power supply that cannot supply proper power to the disk, or a disk controller that is stopping to respond, or a loose cable or connector, or loose drive tray, or back-plane. ) Sorry to say, difficiult to isolate which it might be)

exactly. Thee signature is partly based on the drive size. When seen as its full size on your main system, it would have the wrong preclear-signature, and the wrong partition-type.

PRetty sure it says the same thing regardless if it is pre-cleared, or not.... but skips the lengthy clearing step it would normally perform if once it starts on the process of adding the drive to the array. I did not see in your syslog any evidence of you actually adding the disk to the array. Did you press the button to actually add the disk, or just stop because it says it will clear the disk? Joe L. I stopped it because it just clears it again. I tried removing the Dynamix plugins and preclearing and then adding the drive, but have the same problem of it wanting to clear the drive again. No matter what I seem to do, it keeps saying wanting to clear the drive and never lets me get to the format drive. Are you sure you are using the latest version of preclear? Are you using unRAID v6? There was an issue with the preclear signature on v6 which has been fixed in the latest version of preclear I am 100% sure I am using the latest version. 1.15. If I do a preclear_disk.sh -v it outputs 1.15. I am on unRaid 5.0.6 SO I upgraded to unRaid 6 Beta 12 and tried preclear and then tried adding and getting the same exact problem. I am almost at capacity, what can I do? It is pretty obvious... Does the disk still test as "precleared" when you invoke: preclear_disk.sh -t /dev/sdX (where X = your drive letter) If that test says it is pre-cleared, it is... and you can add the disk to your array and let unRAID do as it wants, regardless of what the screen seems to say. If I'm right, it will skip the step of writing zeros to the entire drive and add it to your array. If I'm wrong, it will write zeros to the drive and then add it to your array. Either way, it ends up added to your array. Joe L.

PRetty sure it says the same thing regardless if it is pre-cleared, or not.... but skips the lengthy clearing step it would normally perform if once it starts on the process of adding the drive to the array. I did not see in your syslog any evidence of you actually adding the disk to the array. Did you press the button to actually add the disk, or just stop because it says it will clear the disk? Joe L.

It looks great. Joe L.

PM me a link. Your changes sound interesting and useful. I'll review and incorporate the improvements. Joe L.

Hey There! OK, so this is normal behaviour for the display and the second entry disappear once the live partition moves off to the 1st - It just appeared and so got concerned, but thanks for the clarification, so I am good to go then and build this array up? No, there will always be multiple entries in the linux /dev directory once a disk has been partitioned. It is expected and normal. unRAID uses /dev/mdX devices. These are a layer on top of the /dev/sdX1 partitions. Basically, once you assign a disk to a unRAID slot, you'll never interact with the /dev/sdX1 partition, but you'll access it through the /dev/mdX partition. If the array is started, the home page of unMENU will periodically refresh itself. It will not refresh if the array is stopped. You are welcome. Please refrain from asking the same question in multiple forums/threads. It is considered to be bad style. (You asked about the partitions in several I've seen, and probably others I've not, and it makes it difficult to respond.) Joe L.

Well... maybe... but maybe not. The preclear report said: == Disk /dev/sdi has NOT been successfully precleared == Postread detected un-expected non-zero bytes on disk== Basically, it wrote all zeros to the disk, but when it went to read them back to verify the write was successful, there were some bytes that were not zero. That is a very bad thing, since you cannot rely on the disk to store your data accurately. Nor can you rebuild any other failed disk accurately if one were to fail. I would try a parity check at this point. It might have an error or two as it expected all zeros... Joe L.

they are not duplicated. What you are seeing is an entry for the entire drive, and a second entry for the first (and only) partition on the disk. Those second entries have the trailing "1" in their names. The file system will eventually live on the first partition.

NO... completely wrong. You'll cause damage to the file-system with that command. you need to use /dev/md2 for disk2.

My first gut instinct response is that it is a memory related problem. I know you said you tested it, but not with the disks also drawing power. What make/model power supply are you using? Many have reported issues with over 6 or 7 drives on a multi-rail power supply... perhaps it is the interaction of both drawing from the power supply. If a single-rail power supply is being used, I would try a different version of unRAID (with a different version of "bash" as it seems to be the one with the segfault) from your syslog: segfault at 2 ip 0807e3a0 sp bfd912a0 error 4 in bash[8048000+be000]