Suse User

Just a quick question… in this case does more pins = better performance? I have two controllers lying around, but I only need 1 of them.

I've decided to abandon this motherboard/memory & use another from a different donor system. I successfully booted from that PC, so will switch the motherbaord & memory into my Server case. Thanks anyway guys.

Good to know, it's an old server so memory might be difficult to source for it, but I'll investigate adding more. I did have 4gb in there, but 1 one the memory sticks turned out to be faulty on memtest.

I'll take a look at Rufus, but the boot sequence does start, it just hangs at the exact same point each time. I only have a Mac, but I know someone with a PC if Rufus is a PC program. I'm using UEFI mode currently as that's what the installer defaulted to.

For years I couldn't even upgrade to v5release due to a hardware incompatibility, a certain beta version worked, but beyond that it wouldn't boot. Having abandoned my 6 port SAS controller I am now able to run v5.x, but when I trying to upgrade to v6 I don't even get to the screen to choose which boot option I want. I've followed the upgrade instructions meticulously, I've tried the Unraid USB creator and tried the manual method using 3 different Sony & Verbatim USB sticks (I have 4 licences) but all stop at the same point, just before I'd expect the boot menu to appear if it was v5. v5 boots just fine. I ran the test and my CPU is 64bit & I have 3gb Ram in the server. USB sticks ranged from 1gb to 64gb (I didn't have a 32 to try, and the 64 gb stick got just as far as the smaller ones). Could there be a BIOS setting I should be turning off perhaps? ALL my drives are connected via SAS controller in my 24 bay server case. I'm in the middle of another Parity rebuild currently as I'm replacing disks with larger ones, so I can't give it another try until tomorrow anyway, but any suggestions are welcome. Thanks.

I've found the updated link and will try it once Parity has been completed

My Unraid server has been offline for years due to a hardware compatibility issue with my SAS controller resulted in a failure to boot. I've removed the offending hardware, reduced the number of disks accordingly and it's booted successfully, I'm currently rebuilding Parity based on 6 Disks + Cache + Parity. I've been looking for the links to update from v5.x but they are all dead. Same for the WIKI, the links no longer work. Where can I find info on how to upgrade? Thanks, Mark.

Thank you, I've followed it carefully. It appears my UnRaid is a Core2Duo CPU with 3GB Ram, I may well need to do a hardware upgrade too. It'll do for now, but my UnRaid Boot USB is also 1gb, and is very old, probably since v2 or 3. Is it complicated to swap to a new stick? the GUID mentioned in the setup instructions is unique to that specific stick isn't it? Is much stored on the stick in v6? Thanks, Mark.

I've been using UnRaid since v2, but I've never jumped into all the wonderful extra features. I'm on 5.0rc11, I never upgraded beyond that after a hardware compatibility scare that at the time I just didn't want to get my head around. I'm happy to lose all my settings/disk allocations, but I want to ensure my data is safe. 2 questions: 1/ Is there a command line way to see what processor & memory my unbraid has? It was pretty powerful at the time, but that was a few years ago. 2/ Is there a quick & easy way to upgrade directly to the latest version so I can start seeing what I've been missing? Thanks.

using Grep (something I don't really understand how to work correctly) with:- lsof | grep disk cache_dir 1404 root cwd DIR 9,1 336 2 /mnt/disk1 cache_dir 1405 root cwd DIR 9,10 224 2 /mnt/disk10 cache_dir 1406 root cwd DIR 9,2 152 2 /mnt/disk2 cache_dir 1407 root cwd DIR 9,3 128 2 /mnt/disk3 cache_dir 1408 root cwd DIR 9,4 368 2 /mnt/disk4 cache_dir 1409 root cwd DIR 9,5 160 2 /mnt/disk5 cache_dir 1410 root cwd DIR 9,6 152 2 /mnt/disk6 cache_dir 1411 root cwd DIR 9,7 288 2 /mnt/disk7 cache_dir 1412 root cwd DIR 9,8 104 2 /mnt/disk8 cache_dir 1413 root cwd DIR 9,9 232 2 /mnt/disk9 find 2431 root cwd DIR 9,1 285168 56315 /mnt/disk1/backup/2009-06-22 Old TimeMachine/Xxxxxxxx’s iMac_001ec21b47a8.sparsebundle/bands sleep 3153 root cwd DIR 9,9 232 2 /mnt/disk9 sleep 3155 root cwd DIR 9,8 104 2 /mnt/disk8 sleep 3157 root cwd DIR 9,2 152 2 /mnt/disk2 sleep 3159 root cwd DIR 9,5 160 2 /mnt/disk5 sleep 3161 root cwd DIR 9,6 152 2 /mnt/disk6 sleep 3163 root cwd DIR 9,3 128 2 /mnt/disk3 sleep 3165 root cwd DIR 9,7 288 2 /mnt/disk7 sleep 3167 root cwd DIR 9,1 336 2 /mnt/disk1 sleep 3169 root cwd DIR 9,10 224 2 /mnt/disk10 sleep 3171 root cwd DIR 9,4 368 2 /mnt/disk4 smbd 30698 nobody cwd DIR 9,1 336 2 /mnt/disk1 smbd 30698 nobody 33r DIR 9,1 336 2 /mnt/disk1 smbd 30698 nobody 38r DIR 9,1 136 18 /mnt/disk1/backup/Xxxxxx's Macbook Those last 3 lines are SMB connections to disk1? That is the disk that is current constantly reading.

That looks like it will be just the thing. I do have a lot of open files, but I've discovered that on both machines the disks being accessed contain backups of Macs and it is a Mac that appears to be the only machine connected using netstat -an | grep ESTABLISHED Which is the command I discovered on a Linux forums. Thanks

I'm having an issue with both my main UnRaid and my backup test box where a single disk seems to be experiencing constant read access. I've recently populated each of the affected disks with backup data including a large number of photos. My assumption is that some kind of spotlight index or other index caching is going on by 1 or more machines on my network. Is there a command line way to quickly see what current connections are active on my server and reading (or writing) data? Thanks, Mark.

Having just recovered from some issues caused by my own stupidity I currently have my server out of the rack and and decided to take another look at trying to upgrade to the latest stable version 5.0.5, something I hadn't previously been able to do successfully. When I upgrade I get "Fixing recursive fault but reboot is needed!" on boot and progress stops there. I've read plenty on the forums that memory can be a cause, but mine passes Memtest (multiple pass) no problem. Through trial & error I've discovered that if I disconnect my RES2SV240 16-Port expander then my server will reboot no problem, although without the majority of my disks. Under 5.0-RC11 my server boots and works just fine. Can anyone suggest a fix? Thanks, Mark.

Could you tell the precise command line to move data (hopefully whole folders) from 1 UnRaid server to another please? I have managed to manually mount the required disks of my failed Server and would like to copy certain folders to my backup/test server. Thanks.

I've actually recovered all critical data to the cache disk by manually mounting the device volumes. I used:- mkdir /mnt/cache mount /dev/sdb1 /mnt/cache mkdir /mnt/disk1 mount /dev/sdd1 /mnt/disk1 cd /mnt/disk1 cp myfolder /mnt/cache -R And it appears to have copied correctly. In order to recover more (not critical) data from the two damaged disks I'd need more space than I have available. Is there a command line I can use to copy entire folders to another UnRaid server on my network? Thanks, Mark.

Does anyone have a good suggestion how to fix a damaged MBR when I can't rebuild the disk? I'm ready to try to copy the MBR from an identical make/model disk purchased at the same time, but is there information held within the MBR that is specific to that physical disk? I've read the the volume label may he held in there. IF so is that something I get get around? Thanks, Mark.

It looks like I have a damaged MBR on one of my disks related to a faulty PSU. I have 3 other identical disks in my array. Is it possible to use 'DD' to backup the MBR from a healthy Disk and restore it to replace my damaged one? Would the MBRs be identical for identical model disks bought at the same time? I've been reading on ubuntu forums how to do this, but if there's a better way to replace a corrupt MBR on an unraid disk I'd love to know the solution. Before anyone suggests I just replace the disk I'm still hoping it'll allow me to parity rebuild recover some data from a different disk that also had problems. I have 2 failed disks, this one seems like just the MBR. Thanks, Mark.

Thank again for all your help. It turns out that the external backup I thought I had of my Up to 2004 photos still exist, just on a different disk to the one in the box marked "Photos" . I said I had my recent (past few years) photos still on my computer, it turns out I have everything since 2004 for there. I'd have guessed I did the archive/clearout 2 or 3 years ago. Turns out it was 10 years ago! No photos lost. I have the actual licence numbers in a database program, but the licence files required by the odd app are still currently lost. I will still try the recovery methods you have suggested Thank, Mark.

Hi there, There's no excuse for it. I'm amazed I don't have a backup of the photos, I thought I did on an external USB HDD but looking at that now it appears it got used for emergency repairing a family members computer a year or so ago. I don't remember using that disk for backup, but that's what's on it. All the current photos (past few years) are also on main computer too, but I felt safe thinking I had 2 backups of the old ones. It appears I have problems with my UPS, I'm getting intermittent power fluctuations. I followed those 'mdcmd' instructions and it allowed me to configure my array again correctly, but on restarting another disk that was previously fine (Disk18 with green dot) appeared to be trying to do a data recovery but failing with contest errors and disk1 wasn't being written to at all. I stopped the array again and Disk18 was not present. I'm getting in a right mess here. I'm going to buy another 3TB disk (same size as my old parity) to swap out for Disk1 & use the backup of my USB key (I took before starting this) to try the mdcmd approach again. I did manage to do a reiserfsck (readonly) on my disks after a reboot and disk2 and disk18 won't run that test because of "Bad Block 2" Disk18 is (currently) non-critical backups of other computers, I'm not overly concerned about that. I do recall there is a method to recover data on a disk that has a corrupted file system. I'm not sure if that is the reiserfsck --rebuild-tree, even if --rebuild-sb may work. Maybe it's a different command entirely.... but I'm beginning to think this will be a better chance of getting my pics back. Once my new Disk arrives I'll attempt the 'mdcmd' approach again as well. Thanks for your help Mark.

That looks like it's going to be very helpful, Thanks... From that thread:- Just so I'm Crystal Clear.. In my case I'd set:- mdcmd set invalidslot 1 As my "Disk1" is the one that needs rebuilding from the rest?

Thanks for your reply, as you suggest I think I'll wait for confirmation to be sure... I did find a bit in the Wiki about swap-disable But as my previous Parity disk is not recognised as valid in the array I don't think that will work for me. Thanks, Mark.

It's serves me right for trying to install a new parity disk whilst working on the phone. I wasn't paying attention and didn't notice that my Disk1 had a red dot by it after I stopped the array. I clicked Format new disk(s) thinking I would just be preparing my new parity disk. I stopped the formatting and now I have "too many wrong/missing disks" I have my original parity disk that I'd just swapped out plus all the other disks from the array so I *should* be able to rebuild disk1, but the interface tells me "Wrong Disk" for the Parity volume. Can I manually edit a file on the flash to tell Unraid to use my Previous parity volume? The disk 1 contains all the licences for all the software I've ever bought, together with out Photos going back 20 years. Thanks, Mark. PS Using 5.0-RC11

That did the trick, thanks Thanks, I'll take a look at that as well.

THAT'S THE PAGE I was looking for, where I previously found the info Thanks! Searching for the word screen understandably came up with MANY results. I'm using Terminal on the Mac

I did try typing "screen" and got the response "Cannot find terminfo entry for 'xterm-256color'." I assumed I needed more arguments. Thanks, Mark.