First I'd like to apologize for the long read.
I hope you can help me with this one. I have a 2-bay NAS (DS218+). I initially have a single 4TB (WD Red NAS Drive) drive (SHR - without data protection) and multivolume support was flagged as No. I decided to upgrade my storage capacity so I bought a new 8TB WD Red NAS Drive.
I've been reading the knowledgebase but still reluctant to proceed as I'm still quite confused if I'm doing the correct procedure. What I want to achieve is to upgrade my storage without data loss to 8TB (without data protection in mind yet). Lets just say I want to replace my 4TB to 8TB like nothing happened.
The current version of my DSM is 6.2.3. In my 1st bay is the 4TB. I attached the 8TB to the 2nd bay and saw the drive recognized and "Not Initialized" as expected. Now, the videos I've seen always mention a Manage button, but in my case I can't find it. And it didn't ask me to repair anything nor there was a "Degrade" status.
I only see Add Drive when I go to Storage Pool -> Action however. I went with it and clicked Next, then had a pop up warning me that the data in the newly added drive will be erased, I clicked OK and this was displayed:
Now, the Total Capacity: 3.63TB is what got me bummed. I'm new to Raid stuff so I'm still quite confused. I'm hoping to get a new max capacity of 7.2TB from my new 8TB. How do I do this without losing data? And my system as-is?
I hope you can guide me. I'd really appreciate it.
Thank you so much in advance.
To have redundancy you cannot have more than what can be saved on at least 2 disks. Right now you have only ~4TB available on 2 disks. If you have another 8TB you will be able to use 100% of the space.
More information
https://www.synology.com/en-us/knowledgebase/DSM/tutorial/Storage/What_is_Synology_Hybrid_RAID_SHR
Related
Respected Seniors,
I need proper guidance for Addressable, please.
If someone wants to share his or her experiences, I would be very thankful for it. I am not able to understand after watching so many videos; I am so confused about them.
I need to upload the different spritesheets (almost 5 to 10) with different labels (should I make a separate group for each spritesheet or place them in a single group, which will be a better way in terms of performance, etc)?
And I am confused about the addressable cache and data.
When something new is added to the server, I want spritesheets to download from the server only once and update on the user's device only when we update the data at server.
The cache and data for addressable will be available until the user uninstall the application or this will be deleted in 150 days. (Someone told me this will delete automatically after 150 days.)
Please guide me about the settings and code. I have also done some stuff, but Addressable is a very confusing topic, so I am not sure if I am doing it correctly or not.
I am hoping for a positive response. Thank you for your precious time.
I was doing some late night work on a hard disk, blowing away partitions on a drive, I accidentally selected my main drive which had a windows 10 install on it. Blew away the partitions with gparted using live disk.
I managed to recover the most of the partitions using testdisk but not the MSR (the hidden one or secure one) one, so the PC doesn't boot....
At this stage i'd like to copy my recovered partition, but using anything doesn't work, clonezilla is confused because somehow there is an MBR and GPT installed on it.
I do not know what i was actually using(mbr or gtp) i see a whole load of overlapped partitions on it looks like the disk was a mess. However the main partition is in tact and the data is all there, checked with testdisk.
At this stage i've deleted all the partitions except for one i wish to keep but clonezilla/gparted still can't clone my partition.
I have no idea how to move forward from this.
Ideally what i would have done is cloned the last partition, done a fresh install of Windows 10 recreating the correct partition table, partitions ect, and then cloned the original partition, the one with data on it, back onto of the freshly install windows 10 one and this process worked for me during my triple boots.
However at this stage cannot clone the partition and too scared to try any option of delete either the GPT or the MBR, in case of data loss.
Advice from anybody would be greatly appreciated, this is only my gaming pc, so we're not taking mountains of valuable data, but there was some old files i forgot to copy to the NAS. Not to mentioned i realised, i never set the backing up onto the NAS of this computer, i know i stuffed this part up, you've save me re-downloading the 600gb of games i had on there and my set up which i loved!
Thanks in advance and your time in reading this mess.
Anyway so i figured it out and this is how i did it.
Basically it was windows 10 that got install with gpt.
and testdisk recovers any way it can which was by installing a mbr table and finding the data.
So i launched gparted to find the info about my current disk, and the partition was visible under mbr, so that meant that gpt was safe to delete.
So did that, after which i could clonezilla the partition to a spare disk, saving all the data!
Fresh install of windows 10 to re-create the partitions, Recovery, MSR and data.
Then clonezilla the from the spare disk ontop of the new windows 10 install, all working perfect, as i'm typing this from that PC.
Thanks all for reading!
I have one e-commerce website in Magento 2.2.2 and it keeps on going down almost every day. Whenever it goes down, users get site took too long too respond and it never loads. To get web site working again I have to restart the server and then it works.
Total space on the server is 50GB. Out of which the whole website is around 18GB (11GB Media files and then vendor files etc.). Here are things that i cannot figure out why:
a.) The server shows that 33GB has been used although it should show only 18GB has been used. I have checked everywhere and I can't find what is consuming additional 15GB of space. Complete HTML folder is only 18GB.
b.) When I checked log files: it shows the following:
WARNING: Memory size allocated for the temporary table is more than 20% of innodb_buffer_pool_size. Please update innodb_buffer_pool_size or decrease batch size value (which decreases memory usages for the temporary table). Current batch size: 100000; Allocated memory size: 280000000 bytes; InnoDB buffer pool size: 1073741824 bytes.
I have already set innodb_buffer_pool_size to 2GB. But still, this problem keeps coming.
The server is an Amazon EC2 server and Magento is in production mode. Can allocating 100GB instead of 50GB will solve the problem?
Increased innodb buffer pool size to 10GB and logs do not show error anymore but server still goes down every day. Since RAM is only 4GB on our server, can that be the main cause? Because everyone is suggesting at least 8GB RAM?
Try the things below.
Magento2 has big log files and caching system. There may be increase your files in var folder.
But still you have to check whether your site belongs to more than 3000 products with high size images for products and you are storing all these in your server itself.
The suggestions what I can give, If your site have more products which I already mentioned better you have to use CDN for better performance. So the entire image will be process from the third party.
Next is You have to setup cloud flare to avoid the down time errors or customer side effect. You can make your index page to load while the server is down. And obviously you have to write script to restart the site automatically while its down.
In your server side check the memory size for php, you can better to give to 2G.
In Mysql side : Check the whether its making sleep query or not. If its making through your custom extension area ask your developer to optimize the code.
for eg : May be the code passing 'collection' for a single item fetch.
You can use the tool like nurelic
If everything is fine from your developer area please try to optimize the site with making memory limit mysql killing etc.. with your server side.
In the mean while magento is a big platform for e-commerce sector, so it has more area to cover by default. Better to avoid the unwanted modules from your active site, like disable the core modules which you are not using yet.
For an average site Use 16gb RAM,
A restart your mysql to make it effect ?
Also you need to set that buffer up to 20971520000, thats around 20GB.
Magento uses a lot of sessions and cache.
I have a mongodb database with several million users.
I wanted to free space and I created a bot to remove inactive users of more than 6 months.
I have been looking at the disk for several minutes
and I have seen that it varied but it will not release large space, not even 1 mb. That's weird.
I've read that "remove" does not actually delete the disc if it does not simply mark that it can be deleted or overwritten. It is true?
That seemed to make a lot of sense to me. So, I've looked for something that forces space to really free up...
I've applied repairDatabase() and I think I've done wrong.
Everything has been blocked!
I have tried the luck and I have restarted the server.
There is a MongoDB service working but its status is maintained in "Starting" (not Running).
I'm reading from other sites that repairDatabase() requires twice as much space as the original size of the database, it does not have it.
I do not know, what is doing, and this could in several hours, days ...
Is the database lost? I think I will stop all services and delete the database.
repairDatabase is similar to fsck. That is, it attempts to clean up the database of any corrupt documents which may be preventing MongoDB to start up. How it works in detail is different depending on your storage engine, but repairDatabase could potentially remove documents from the database.
The details of what the command does is outlined quite clearly (with all the warnings) in the MongoDB documentation page: https://docs.mongodb.com/manual/reference/command/repairDatabase/
I would suggest that next time it's better to read the official documentation first rather than reading what people said in forums. Second-hand information like these could be outdated, or just plain wrong.
Having said that, you should leave the process running until completion, and perform any troubleshooting if the database cannot be started. It may require 2x the disk space of your data, but it's also possible that the command just needs time to finish.
I have been doing an online course in MongoDB, however I am frequently coming across a term called "Persistent disk". I have googled it out, but did not get a satisfying answer. Could you please help me out ?
When your application runs (or Mongo in this case), it does all its work in RAM. RAM is not persistent because when you turn off your computer you permanently lose all the information stored in RAM.
Hard drives and SSDs on the otherhand are persistent. If you write something to them, it sticks for good.
So when you tell Mongo to insert a document, it first gets written into RAM, and then eventually gets written to the (persistent) disk. From an AppDev perspective is this all hidden from you and you (generally) just assume its written straight to desk
This is a good video from what I guess to be the Mongo course you're taking that talks about the transition from memory to disk.