anthropoidape

Just installed the plex docker yesterday. Seamless installation, everything works. Thanks!

I just had more or less the same experience - I got "connection refused" with Needo's plex, but binhex worked. I'm not complaining or anything, just thought I'd mention it.

Thanks. Yep, I have since done a correcting parity check.

Thanks! Well, I feel a bit dumb now but I am used to that

I see. And it seems like xfs_repair does pick up md-devices correctly. So perhaps the answer is simply that I should have run /dev/md1 instead?

I connected to my unraid box with SSH, then ran: xfs_repair /dev/sdi1 ... or some similar designation of the device (it might have been sdn1 or some such). I subsequently ran xfs_repair -L /dev/sdi1 I realise this was not the right thing to do on a mounted filesystem and it may have caused some filesystem corruption (I ended up with some stuff in LOST+FOUND), but I was really just experimenting. I seem to recall that other filesystem repair tools - for reiserfs and btrfs - decline to run on a mounted filesystem, or am I misremembering?

Is it correct that xfs_repair runs on an unraid-mounted drive without warning that it should be unmounted? I lost some data recently, possibly (but possibly not) because of doing this. It was not critical and I am not complaining, but it does seem like a potential data destroyer if someone runs xfs_repair and forgets to stop the array first. I may be wrong about all this, but I thought I should mention it just in case it's a problem and you guys aren't aware of it. Jason

Of course you mean after you have paid for the Windows OS for each and every copy you're running. Otherwise you're simply stealing from Microsoft. I'd hate to get into the debate about what really constitutes stealing, but I don't need to on this occasion anyway... I am just running one XP Pro VM. I paid for XP long ago, and today XP is probably not much use for anything except a VM. I am now setting up a second VM running Ubuntu and that will probably be it. I was talking about the idea of having unlimited amounts of (virtual) hardware to play around with.

Thanks for this. I added a second vdisk via the command line, this prompted XP to want driver installation, and now I am back to one vdisk that runs on the virtio drivers. In case it is not yet known, the kvm gui reverts the the vdisk to bus=virtio with each change to the VM (even, for example, when you change the VM to automatically start). So (a) this probably needs fixing and (b) it was a good reason for me to go to the effort of getting the virtio SATA drivers into the XP VM. It is nice to be prodded into doing some command line work anyway I like this little XP VM. It's on a 10GB vdisk and even that is more than it really needs, and it covers off a few little things that I use a 24/7 windows box for. I don't know what it says about me but even though I have been using VMs on unraid for a while now, I still find them amazing. It's like, "I can have as many computers as I want! For free!"

Thanks Jon. Is there any particular problem with leaving the disk running on the IDE bus for the time being?

See my edit. I edited the xml and it seems to be installing now. I am not sure whether I'll be able to edit it back later after installing virtio drivers. I will let you know how that goes.

I think I have the same problem, but I am not sure I understand the solution. I am attempting to install Windows XP on a VM but there is no opportunity to install drivers; the system looks for a floppy disk. I have tried changing the virtio drivers iso to a floppy drive but it doesn't although the xml appears to validate. I also tried adding the virtio drivers to the XP install using n-lite without any success. Have you managed to install XP or just windows 10? Edit: XP seems to be installing now. I had to amend the XML so that the hard disk was on bus='ide' rather than bus='virtio' and delete the reference to PCI below that item.

Well, I stopped the array, restarted without any Disk 10, then restarted with a Disk 10. It's rebuilding now.

I don't know whether there are other methods, but there is a SNAP plug-in for v6 that works. https://lime-technology.com/forum/index.php?topic=31594.0

Well, in unraid 5, no problem with parity or that disk's data was showing up at all. I am not sure whether that actually means anything though. I ran chkdsk on the unraid 6 stick and it found no errors. I re-copied the v6beta15 files over (other than config) as well. It made no difference. Am I looking in the right place for the parity check or rebuild option? The XFS disk just showed up as "unformatted" btw, in case anyone is interested in what happens when you revert to unraid 5.

Thanks. I can't see anything untoward in the disk attributes. Disk 10 attached to port: sdj ID# ATTRIBUTE NAME FLAG VALUE WORST THRESH TYPE UPDATED FAILED RAW VALUE 1 Raw Read Error Rate 0x002f 200 200 051 Pre-fail Always Never 0 3 Spin Up Time 0x0027 249 160 021 Pre-fail Always Never 2541 4 Start Stop Count 0x0032 100 100 000 Old age Always Never 779 5 Reallocated Sector Ct 0x0033 200 200 140 Pre-fail Always Never 0 7 Seek Error Rate 0x002e 100 253 000 Old age Always Never 0 9 Power On Hours 0x0032 093 093 000 Old age Always Never 5503 10 Spin Retry Count 0x0032 100 100 000 Old age Always Never 0 11 Calibration Retry Count 0x0032 100 100 000 Old age Always Never 0 12 Power Cycle Count 0x0032 100 100 000 Old age Always Never 638 192 Power-Off Retract Count 0x0032 200 200 000 Old age Always Never 585 193 Load Cycle Count 0x0032 200 200 000 Old age Always Never 780 194 Temperature Celsius 0x0022 126 112 000 Old age Always Never 24 196 Reallocated Event Count 0x0032 200 200 000 Old age Always Never 0 197 Current Pending Sector 0x0032 200 200 000 Old age Always Never 0 198 Offline Uncorrectable 0x0030 200 200 000 Old age Offline Never 0 199 UDMA CRC Error Count 0x0032 200 200 000 Old age Always Never 1 200 Multi Zone Error Rate 0x0008 200 200 000 Old age Offline Never 0 I am about to try rebooting in unraid v5 (as I have two sticks deal) and see what happens. I am not sure how it will handle the one XFS drive.

Of course, sorry. syslog.zip

Hi all, I'm a very long-time user of unraid v4 and v5, but only just this weekend got around to switching to v6. All is well. I am in the process of moving files around to convert to XFS - one 2TB drive down, 9 to go. Got a Windows 7 VM running in Xen... very cool. I just need to get plex going next, then swap in the much gruntier mobo and cpu from my current desktop PC, and I will be done for a while. I hit a snag though. At a couple of points this afternoon, my unraid box completely froze. Totally frozen, ssh disconnected, VNC dead as well. No action at the physical keyboard either. I saw no option but to hard reboot. This actually happened 2 or 3 times in close succession, but has not happened since. The cause is currently a mystery. Anyway, it may or may not be related but I now have a triangle next to Disk 10 which indicates "invalid data content". What I can't see anywhere is an option to run a parity check or rebuild Disk 10. I just have invalid data and that's all I've got. Am I blind? Shouldn't it just be there on the "main" page? Or is this a data failure of a kind that I haven't seen before? I am running 6.0-beta15 with a Pro licence. This problem aside, I am very excited with the new emphasis on virtualisation. My unraid 5 setup suddenly came into its own when I figured out vbox, and Xen is easier and better.

Thanks very much. Soon (probably) I will take the plunge!

Hi all, I have been running this plugin for a while, and it's been great. I have hit some hardware issues and so I am giving my unraid box a bit of a spring clean. I am considering jumping to v6, as I have been sitting at v5.05 for a long time. Question... what options are there for a webserver with v6? I am asking in this thread because the only reason I have ever bothered installing a webserver plugin was so as to run php virtualbox. It is ages since I did this, but I seem to recall that it was basically essential for setting up a vbox machine. What are those of you running v6 + virtualbox using for the webserver component? Or, if you are not using a webserver, what is the webless process for the initial setup of a virtual machine? Jason

I thought I'd just pop in and say that all is well now. Nothing failed while I was waiting for the RMA drives, and one of the 2TB drives was replaced with a 3TB... no comment from WD so I don't know if it's a policy or an error. Obviously that is now my parity drive so I am "3TB drive ready" from here on. I ended up with more drives than I really needed, so now my array has 2TB more capacity than it had before.

I will leave the Parity Disk for now and replace it with one of the RMAs that's coming back. The one I had that had 65535 sectors - which was Disk 4 in the OP - kept passing in WD Diagnostics. I had to stress it (fill with zeros etc) a few times before it finally gave clear cut errors. Now it is in my RMA box. Jason

The syslog appears clean as far as I can tell. I am somewhat inclined just to leave it for now, replace that drive when I get my RMAs back, and then do the preclear etc then. I can leave it in the box as a warm spare if it cleans up okay.

Thanks bonienl. I thought about it, and decided that apostrophes are not particularly good practice anyway. They are always going to be a risk for some form of breakage. Thanks for looking at it!

Good morning, D4 replaced/rebuilt, and parity removed, re-added, resynced. The parity disk still has one pending sector - it's unchanged. I guess that most probably means that the relevant sector wasn't written to in the resync..? Should I have precleared it or something?