nextadmin

Dead dead, like dead... unreadable in win or debian ... 2 out of 5... win complain about error, not fix by scan... unmountable on debian... I am definitely cursed

USB KEY died in less than 1 hours ! GUI warning usb key corrupted or offline. System dead !

Thank you. I did check with the US vendor, and i did choose this one excatly: LSI SAS9340-8i ServeRAID M1215 12Gbps SAS HBA P16 IT mode for ZFS FreeNAS unRAID Actually, i bought a BAD USB KEY from amazon, who failed me after less than one hours using unraid ( warning message the key is corrupted or going offline )... I start to beleive i am curse ! The bad usb 3.0 is a 32GO GIGASTONE ... Hopefully, the config folder is safe... and i was using the beta unraid to save it ... I just hope i wont go to bad usb keys too much...

Done: Definitely upgrading controller. Going for a more simple HBA 9340-8i as i realized: - I will never upgrade to SAS ... - I will surely not upgrade my array to mvne disks ... - SSD are not completely out of scope if ever i have dying disk ... - but i want to take advantage of a real PCI3.0 LSI HBA ... Find the card with theartofserver

OK, here that i am doing, thank to JorgeB who was nicely helping: Using some "old" components ( ryzen 3400G, B450M Motherboard, Exos X18 16To )... 32 GO DDR4RAM ( new, tested ok ) 32 GO USB 3.1 key ( just ordered some as i have no more spare ) HBA BEYIMEI 10 X sata3.0 6GB/s based on ASM1166 + JMicron JMB5xx ( tested ok but slow and bottlenecking the system ) 1 parity disk Exos X18 16TO ( have one sitting on a shelve for more than 4 month, time to waste it ) ARRAY of 5 HDD x 4TO ZFS ( ParityST4000NE0025, bought between 2016-2020 ). Will use them until they die, hopefully not all at once. CACHE of 2 X 1TO SSD ( redundancy ) ( just ordered ) Might be a good start. Planning to updated the HBA to a AS9300-16I 12GB/s if the pci 4.0 bios gets available... or i will also change the motherboard... ( getting expensive ) When the HDD from the data array will die, i might simply change them for larger HDD, or for fewer SSD ( 2 TO price are nice , and i will have around 8 free sata slots if i update the HBA ) I will run a Debian12/NEXTCLOUD VM from the cache, store the user's data to the ARRAY ... and backinp up the data in two ways : ZFS Snapshots on the server and a schedule rsynch to an intel nuc and HDD 10G box

Issue is fix. I bough 2 16GO kits... Now, memory size and quality is no more an issue... Also, i went to a double 1TO ssd in order to have redundancy for the cache array...

Well, i am discovering the possibilities around UNRAID ... i maybe i am thinking totally wrong. My goal is to have: - the capacity to host test VM with différents OS. Perfect UNRAID fit. - But, the main purpose is to have a Debian 12 VM ( apache/redis/mariadb/php/nextcloud/letsencrypt ). I want a VM for the flexibility, as i am a complete noob regarding docker/portainer/snaps ... but i am able to manage Debian so far, i have created, tested the VM, and it works exactly as i wish. The storage capacity of my old Synology DS209 ( yes, 2009 model ) is max out and around 9.5TB for a max of 12 TB ( family/pro usage ). It is getting old and can no longer be updated even If I have no real use of the DSM capability. I think it is time for a new machine. Here come UNRAID as i am sitting on a few hardware pieces ... and also for budget limits. The Debian VM will be used as a Nextcloud host. With the capacity of taking advantage of the SSD-CACHE in terms of performance, the array for the parity capacity, and using a CIFS/FSTAB to a ZFS Share for the Nextcloud user data and having Snapshots. My array is so far build with one 4TB parity, and 4x4TD HDD for 16TB capacity. I have a 16 TB HDD who might be used like either a simple device, or as a new parity disk. And I have a 480GB SSD ( can be upgrade to a 1TO SSD ) So far, i am only doing labs stuff to understand how UNRAID works. The big question is how to create all this in the best way with UNRAID ! Even regarding the partition type for the array, i am unsure if i must use BTRFS or ZFS... Btrfs for flexibility, or ZFS for large-scale data storage, i am right in the middle. I am unsure of HOW i should make my built. The VM is around 300 GO. Where should i installed it and how to manage the storage ? The Nextcloud user data will be mounted via CIFS to the array... But how to take advantage of the SSD-CACHE to boost the data transfert ( I have a local 10G network, and my internet provider is FREE with a 10Gb/s 700Mbs bandwith ). Some of my users are not in the same city ! Thank a lot for your time !

Hello, i am actually building a new server ... Using a ssd from LDLC as a cache : CacheLDLC_F7+480GB_03022220B0016 - 480 GB (sdg) Around 74% of the disk space is now fill-up. GB354 GB / 125 GB I have a daily schedule MOVER at 03:00 Notice it did not work for the past 2 days... Tried a manual mover, did not work either. nextlab-diagnostics-20230812-1118.zip

Hello, nice explantation for qemu resizing, but bad syntax. qemu-img resize vdisk1.img 500G like in the video will not work, triggering a warning like: WARNING: Image format was not specified for 'vdisk1.img' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. better use qemu-img resize -f raw vdisk1.img 500G

Hello, I am testing this docker. So far so good, but it is absolutely not friendly users. Absolutely no logs, no verbose output... It is doing the jod, but the VM must be stopped ...

Hello JorgeB I did not realize my mistake. Went back to orignal 8/8, but crash did continue... Anyway, those crash were not good. I did a mem86 and find out one of my ram was bad... Just ordered new ram to definitely fix the problem ( hope )... Thank you for pointing this out !

Hi, My lab is using UNRAID_VERSION: 6.12.3, is based on a Ryzen 5 3400G with 16 GiB DDR4 on a asus Motherboard DS3H-CF based on a B450M chipset. ( joined the diags files ) I have unraid managing ( so far ) an array of one disk parity + 5 hdd, one ssd as a cache ( 450 GO so far, planning more if needed ), one hdd as a device for backup. Classique shares, with cache to array for most of my setup. one docker ( stopped ) for managing VM backup manualy. one Debian 12 VM running nextcloud so far ! Planning to have other VM for dev purpose. It took my several try ( dockers, vm, apps tested ) to finally have what i want. MY PROBLEM 1: - with 16GO DDR4 ram, if parity check is running, i have 85% of the ram consumes. MY PROBLEM 2: - If i upload some files to my debian/nextcloud machines, the system hang/crashe after a few minutes ( my upload was 107 GO and it takes like 10 minutes to build up the ram to more than 100% and crashes... MY QUESTION: - do i need more ram ? - how much ram is needed per VM ? - Do i need to plan for a larger SSD for cache use ? - do you have any comments on my setup MY GOAL: Apps and Dockers are NOT what i want to use with unraid. Only a few if absolutly needed. My main goal is to have a production debian/nextcloud VM running as production. And Somes others VM on a start/stop scheme when needed... still have 25 days to decide to buy a licence or find another solution. thanks. nextlab-diagnostics-20230809-2240.zip