dn7172

Appreciates the info on default shares, I have further understanding of what files would be in here. I checked the /system folder on disk1, and discovered it's no longer there so I guess I'm ok 😕 The /isos folder is empty and that would make sense since I never used VM. I think I've covered all my bases, so pretty much ready to convert the filesystem. But first I am running parity check now as I noticed error counts. While the parity check is running, I was thought I should verify the MC copy was ok. I have double checked total size of directories and count of files - I'm 99% satisfied. For those also learning like me, I'm sharing the resources I used https://linuxhandbook.com/find-directory-size-du-command/ and https://linuxize.com/post/count-files-in-directory-on-linux/ re: 99% satisfied is because there's a discrepancy for one of my folders which the original displayed 92GB vs copied 91GB. However the file count is the same. I'm not sure why the size difference.

There might be a reason to use either in the future. As of now, I haven't done more with it because my system specs are quite outdated and I plan to upgrade it.

Thanks for letting me know. I don't have any docker apps or VMs, i.e. my system is pretty bare and strictly used as a file repository but I have disabled them in settings as instructed. I just checked and saw there is a /system folder on my cache disk too. For some background, my unraid system originally started without a cache disk. I think it was this way for many years, but last year I added a cache disk. Should I really copy disk1/system/ to cache disk or is it better to save it elsewhere and copy back?

I have copied over my files to disk2. For next step, do I need to do something with the /isos and /system on disk1 OR will it be safe to leave it and go ahead to convert the disk to NFS? Best, D

Sorry I missed mentioned the one cache drive (updated my previous post). What should I do? I have a follow up question to approach 2, please forgive my limited knowledge and terminology. I believe my files under folders are distributed across the array (e.g. Documents folder resides on disk1, disk2 and disk3 with various files across those disks). After I copy the files to "backup" to disk2 and convert disk1 to XFS, do I simply just use the MC copy command to copy back those files? Will unraid know and need to recreate the reference points on disk1 to the files?

I found out I need to perform the conversion for one of my disks in RFS format. This disk has documents/files I don't want to loose, so it's important that I do this accurately. So I like to check here and confirm if my approach is sound before starting the process. Current array: Parity 4TB Disk1 1TB RFS (99% utilized) Disk2 4TB XFS (25% utilized) Disk3 1TB XFS Disk4 230GB XFS Cache 250GB Future array: Parity 4TB Disk1 1TB XFS Disk2 4TB XFS Disk3 1TB XFS Disk4 230GB XFS My plan is to use MC to move/copy files, which seems the the most straightforward and understandable to me of some of the methods I've read. Should I be OK? I have two ideas to keep all my files and convert the disk1. Which one is the best/safest approach? Approach 1 Move all my files from disk1 to disk2 Stop the array Convert the FS Optional Move files back to disk1 Done Approach 2 Create a folder "temp" on disk2 Copy all my files from disk1 to disk2/temp Stop the array Convert the FS Copy all files from disk2/temp to disk1 Done Question: I noticed there is folders called /isos and /system on disk1. Should I move or copy them along with my files? /system has /docker/docker.img and /libvirt/libvirt.img Question 2: As I'm a little nervous about doing this, I want to copy just the contents from disk1 to a Windows enabled external USB harddrive to create a secondary backup in case something goes terribly wrong. I don't think I can do this on a Windows PC via network shares without having to identify each file that resides on disk1. Is what I want to do even possible and how would I go about doing this?

I appreciate the follow up. I sent my usb guid id in the last hour and now wait for the reply with the key file. Thanks

I emailed this morning. Thank you for your attention on this forum. Thank you @ChatNoir

Just tried doing this, copied and pasted the license key URL into my browser and getting a 404 page not found. I think something is wrong and maybe I won't be able to download my key.

Figured out my problem now. My BIOS lost all its configurations including date/time, once I updated my server is running again. Interesting you asked about what license. I am currently running a trial version, but have a purchase license key which my server isn't taking. I'm getting a downloading error, so I'm not sure what is going on as I expected that it would be a simple thing to do.

Hello all, Tonight I added a new NIC card to my unraid server because my onboard one was only 100mb. The new NIC is rated gigabit speeds. Now that I have installed it and turned on my server, it's unable to connect to the internet. I can still connect to the the server's portal via local IP. I'm unsure what to do. Also, I don't think this is related but at the bottom the portal page, I see the message "Array Stopped too many devices". I did some troubleshooting, one change I made was disabiling the onboard NIC through the BIOS. I thought that would have helped. I assigned a new IP address for the new NIC in case there was some conflict my router was seeing, but no luck here. I'm unsure what else I can do now. If anyone is interested to help look into my issue and help me get this figured out, I am appreciative. Thanks unraid-diagnostics-20201103-2104.zip

Thanks appreciate your help and tip about SMR which I'm learning about now.

Up to now, my experience with unraid has been with one parity drive, but I'm looking to increase that to two. I just have a couple questions that I like to answer before I decide on the type of drive to purchase. I'm undecided on what type of drive to use for parity. I just read somewhere that it's a waste to use a Red drive for parity, is this true? That is, is it better to use green drives over red (and even blue)? To run two parity drives, do each one have to be as large as the largest data drive like it is when running with one or can they be split? For example, if my largest data drive is 4TB, can each of the parity drives be 2TB? I have a feeling the answer is they both need to be 4TB but looking for confirmation. Thanks

Probably a valid point. I now know my setup is limited and will consider in the future what is needed if I need to upgrade. I'm aware my motherboard is limited to 4 SATA connections and therefore may need to look into a new system or find a decent PCIe controller to add additional ports (preferred approach for now). But the main thing is that my OS is running with the new version!

Wow thanks! I added a 512mb stick and now it is running! If anyone has any clue why this happened, please let the rest of us know especially for people who have a surface/general understanding of unraid (me)

I was able to take a picture of the screen to show where the OS boot stops at

Yes. My motherboard is Asus M2V-MX, cpu is an AMD Athlon 64 X2, with 1GB RAM Parity drive is WD 1TB, and two data disk WD 640GB and 1TB When I run unraid ver 5.0.6, the flash drive is a Kingston datatraveller 512MB. I have tried using this and other flash drives with minimum 512MB to 2GB.

I am attempting to start a new Unraid server on a new usb drive. The installation went ok, but it is stalling somewhere in the boot every time I start it. While the usb drive has been installed with ver 6.8.3, the harddrives have existing data from the previous unraid v5.0.6 - which was very basic, no special configurations other than the data and folders. I was expecting the server to boot ok and bring me into the gui where I would configure the harddrives carefully i.e. parity and two data drives. I have spent about 3 hours trying different usb sticks that I own, scanning for IP addresses to see if that was the problem of not being able to login - but it shouldn't because I have setup a static ip (same as the old configuration). So back to where the boot stalls. The boot doesn't seem to make it through all the way as I was expecting to be able to login to the web portal. Instead the below text is the lines several lines I see on the screen. mount_block_root+0x280/0x2a4 prepare_namespace+0x131/0x167 kernel_init_freeable+0x1d9/0x1e2 Is someone able to tell me what I'm missing?