LimeB

Okay cool, that at least got me not to the shell prompt. Different issue now but I think it is because I never selected the OS Install ISO to install when setting up as I had thought it would pull it automatically and being I saw the shell command line, I thought it was Chrome OS but not the GUI. Actually I didn't realize there was a difference until now. I do want to just run Chrome OS to play around with it, see maybe if I wanted to get a cheap Chromebox for a few various reasons.

That I do have setup, the OS just loads to a command line. I would expect to see the GUI for the OS.

I just setup a Chrome OS VM, just the default template, but I don't seem to have a GUI. How do I go about getting a GUI for it? Sorry, I'm a total noob to ChromeOS and just can't seem to find the answer.

I am looking at replacing my Win 10 desktop as I just really don't use it anymore but I still like having it for certain things from time to time. I do also have a Win 10 VM running in unRAID which works great but I use it for other reasons outside of my desktop. Can I simple take my desktop HDD and manually passthrough that disk without having to format and reinstall Windows? Or likewise, in the future, could I simple take the passthrough disk out of unRAID and put it back into a desktop? I know drivers and such would need to reinstall which is fine. My main concern is say unRAID dies and I need to get to that VM I want to be able to at any moment by popping the disk into a normal desktop.

Thanks. Actually just was posting that I say in another thread that is what someone did. Looks like I am good again. Much appreciation!

Thanks. I tried running it with with -nv and this is what came back. Phase 1 - find and verify superblock... - block cache size set to 743528 entries Phase 2 - using internal log - zero log... zero_log: head block 180718 tail block 177815 ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... bad agbno 4294967295 in agfl, agno 3 freeblk count 5 != flcount 4 in ag 3 agi unlinked bucket 62 is 149374206 in ag 3 (inode=3370599678) sb_ifree 194, counted 2085 sb_fdblocks 352884694, counted 377133049 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 5 - agno = 3 - agno = 4 - agno = 2 - agno = 1 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 3370599678, would move to lost+found Phase 7 - verify link counts... would have reset inode 3370599678 nlinks from 0 to 1 No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Mon Mar 12 06:49:59 2018 Phase Start End Duration Phase 1: 03/12 06:49:52 03/12 06:49:52 Phase 2: 03/12 06:49:52 03/12 06:49:52 Phase 3: 03/12 06:49:52 03/12 06:49:57 5 seconds Phase 4: 03/12 06:49:57 03/12 06:49:57 Phase 5: Skipped Phase 6: 03/12 06:49:57 03/12 06:49:59 2 seconds Phase 7: 03/12 06:49:59 03/12 06:49:59 Total run time: 7 seconds I then tried just -v and this came back. Phase 1 - find and verify superblock... - block cache size set to 743528 entries Phase 2 - using internal log - zero log... zero_log: head block 180718 tail block 177815 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. I'm not sure what to do next.

Yesterday all of my user shares were inaccessible and I saw they all went missing. I rebooted and they all came back except the ones on one of my drives which now shows: Unmountable: No file system Attached is the diagnostics file. Not really sure what to do at this point and didn't want to try something that ended up losing the data. diagnostics-20180312-0621.zip

Gotcha. It was what I was looking at as well but wasn't entirely sure. Thanks again John_M and trurl for the help. I have everything running better then it was before and learned a couple of new things.

It looks like it did work but I'm not sure what controller='1' means. Also initially I had two SCSI Controllers without drivers in Device Manager, once took the virtio drivers while the other doesn't. Now I have the Blu-ray drive showing up in Windows but I am not sure why I have this extra SCSI controller showing up.

I am trying to get this to work myself but a little confused. I am trying to pass through [7:0:4:0] cd/dvd PIONEER BD-RW BDR-208M 1.10 /dev/sr0 Would this be correct? <hostdev mode='subsystem' type='scsi'> <source> <adapter name='scsi_host7'/> <address type='scsi' bus='0' target='4' unit='0'/> </source> <readonly/> <address type='drive' controller='1' bus='0' target='4' unit='0'/> </hostdev>

Okay thanks. That seems to have mostly have done what I was hoping for, or maybe I am looking at it incorrectly. After having everything up, including my cache drive, I seem to have a few folders that I am unable to get ride of. I would like to just wipe the cache drive because it seems that inside it has the following folders/files \mnt\cache\system\docker\docker.img \mnt\\cache\system\libvirt\libvirt.img I tried doing an rm -r to them but when I reboot, they come back. Should they be there?

I do have back up the flash from before. So then should I just only copy over super.dat? I don't want to retain any other settings/configurations I had prior except for keeping the data on the drives. I also did copy over the key already but nothing else.

Today I decided to rebuild my unRAID box from scratch but I want to retain all my data drives. I have wiped out my USB drive and set it up as fresh. I have my drives selected how they should be. Would I then use New Config to start the array without the drives being seen as new? I want to retain the data on all the drives. And would I use the preserve option? I just want to make sure I don't do something incorrectly here and lose the data.

Rumor has it that if you purchase the Pixel 2 that you also will receive 5 years if unlimited Google Drive. There may be some limitations if it but nothing is known besides the rumor of 5 years of unlimited storage for Drive. We'll know more shortly.

Which one did you pick up? Reviews seem hit or miss on theirs. Java sucks but it is what it is.

Oh yes, correct, over IP. The cost seems to be the issue.I could see going $300 tops but everything I am finding that should provide good quality/reliability is a bit more than that. Maybe I will have to just wait.

For years I have been running a Super Micro server board with IPMI. I love the ability of being headless with remote power controls. I am running a few generations ago Intel chip and have been early waiting for Super Micro's updated IPMI with HTML5 instead of Java but now that Ryzen is due out in a few days and that I started running some apps in Docker and some VMs, I am really interested in an 8 core Ryzen chip for my server. The issue for me is not running a server motherboard and having headless and power controls. Can anyone recommend a good KVM setup that also gives me power controls and would allow me to use it on any motherboard that I use? It also would be pretty nice if it allowed control for a few boxes but even just a single would be fine. Also hoping not to spend to much, maybe a few hundred bucks is fine with me.

Appreciate the reply. Issue seems to have been resolved. Ended up going back into the settings for VM Manager and there was a check box to delete the image next to Libvirt storage location. I did that and the tab showed up and was able to boot up my VM.

A few weeks ago I added a cache SSD and was trying to move basically just my VM and docker images over to it which initially worked fine. At some point, maybe after a reboot, I noticed my Windows 10 VM was not up and that the VM tab was missing. i have tried disabling and enabling VM Manager and the paths appear to all be correct. I am running 6.2.4 and attached is diagnostics.

Think I am good now. I dd to another drive and on that drive I used -L on xfs_repair. It appeared that all my files where there, at least the most critical being family photos. The new ones were at least there and the older ones I know are backed up. So I went ahead and did xfs_repair -L on the original drive and it had an error but seemed to work. Its back in my unRAID and seems to be okay. Thanks you guys for the help, learned a bit from in which in the end is fun.

Okay thanks, I wasn't entirely sure. Same error in Ubuntu as unRAID with the correct command so I will wait until I get home with a new drive and clone it before preceding. I work IT (network) and probably should know more Linux but don't so I really appreciate the help. Last question I think for now. The Disks utility in Ubuntu. How well does the Create Partition Image and than Restore Partition Image work? Going to assume it does not work the same as dd.

I did try running xfs_repair -v /dev/sdc in Ubuntu and it is going through a bit different that what in unRAID did. Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... ........................................................................... ........................................................................... ........................................................................... (and repeats) Not sure if it is doing something, stuck, or what to do.

Absolutely. That fact is one of the BEST features of unraid, each drive has a completely independent file system that can be manipulated in any compatible OS. While doing a check through Ubuntu, do I need to use /mdx (mdx1 showing in unRAID) or do I go with /sdbx? I don't actually understand what /mdx means, I never saw this until I saw it on the console and read a mention of it in another thread. Also wondering. Does 'Creating partition image' in Disks truly create a disk image which than can be restored?

I do have externally swappable bays. If I were to use dd to clone it; is it possible to than take that clone and try running the file check in lets say Ubuntu?

If you wanted to have another shot at recovery if these attempts fail, you could pull the physical disk and rebuild to a new drive, then do the file system repair on the new drive. I'll give that a try first. When was the last time you had a clean parity check? If all your other drives are physically fine and parity accurately reflects what is on the rest of the drives, rebuilding to a new drive will clone what is on there currently. I ran a check over this past weekend so it should be good. There are several options and permutations with varying levels of safety and repeatability to work with your data. How much trouble do you want to go through to ensure the best possible outcome? I'm willing go through whatever hassle needs to be done as well as it could be. All in all sounds like the next step is to rebuild the drive from the parity and trying the -L flag. I should know then sometime this weekend if that will work.