merve04
Member-
Posts
322 -
Joined
-
Last visited
-
Days Won
4
Everything posted by merve04
-
I assembled a shr-2 with 6x 12TB drives to start as the temp mobo only had 6 satas. Transferred all my data which left me with about the 500GB space free, hence the earlier questions. Now I've moved my drives to the permanent server with the addition of 2 more 12TB drives. Shockingly, when i initiated the expand, it prompt the 2 additional drives, and final calculation of array size was 65.46TB up from 43.64TB. I thought expansions only happened 1 drive at a time, bonus if it does this all in one shot though. When i look at resource monitor, under disk, i can see disk 1-6 are reading and writing at a decent speed, and disk 7-8 are only writing. This leads me to believe both drives will be added. When i looked up mdstat, it was going at over 60000kbps in the begining, its down to around 50000~55000kbps as I'm letting people stream away from my plex and sonarr\radarr still rolling and downloading as need be. Its been 33 hours and its at 51.5% done.
-
Whats the fastest kbps speed you've seen xpenology expand a volume at?
-
I mean i estimate i will have between 300~400GB available once transfer is done and can begin expanding. Hopefully thats enough for btrfs?
-
Thanks for the info, as you mentioned I also looked on synologys site but couldn't find anything that said i cant. It just would seem unusual why someone would wait till they have merely a few gigs left before doing an expansion and didn't want to be in a position where it wouldn't work.
-
Is there a fill limit the volume can be at before expanding doesn’t work. Example, if volume is 99% full can I expand?
-
The best you might be able to accomplish is run xpenology in virtualbox within macos
-
Quick question, maybe someone who uses this card knows or can confirm; I’m planning a rebuild of my array with exos x16 drives and since they’re 4Kn, is this card capable of reading 4K sectors? Or will I be limited to 512e? thanks
-
Alor hier j’avais décidé de commencer un smart test sur le dernier disque dur que j’ai ajouté au system. Plus de 30 heures plus tard, le test était geler at 60%, mon system était virtuellement non accessible, incapable de redémarrer dsm du menu, il y a fallu que je manuellement redémarre la machine. DSM fonctionne normal maintenant mais un scrub est en processus. J’ai aussi remarqué que un de mais disque dur que la lumière d’activité étai allumé solide. Tant que le scrub n’est pas terminé, je ne peux pas vérifie quel disque dur est-ce t’il. J’ai pris quelque screenshot du disque que je faisais un smart test, aucune idée ce que c’est valeur veule dire. Si quelqu’un ici peut me fournir un peu plus de renseignent, j’apprécierait beaucoup cela.
-
J’imagine que je doit fournir le rapport smart de tous les disque dur?
-
Ou se trouve t’il ce rapport?
-
Merci pour votre réponse, j’ai présentement 13 disque dur puis tous indique normale pour le « health » et le « SMART » faudrait tu que je fait un test prolongé pour chacun des disques dures? Car le test rapide detect aucun erreur.
-
Bonsoir, Alors jai un probleme avec DSM et des erreus checksum. Mon materiel est un gigabyte b365m ds3h, i5 8400 et deux carte pice 4x jmb585 (5port sata par carte) Depuis le debut de decembre je recoit des erreur, jai fait un memtest86 pendant 80min recament avec aucun erreur. Je ne c'est plus quoi faire. Voice quelque log. dmesg.html syslog_2021-2-17-20 9 58.html
-
Well nearly 90min of testing, I’m going to assume it’s prettt safe that it’s not the memory causing issues. Anything else I could check/test?
-
“message” does not work for me. All drives in my pool are Seagate 4 and 8 TB drives. I have one hitachi running standalone for VM and surveillance recordings. I could flash a USB key with memtest I suppose. I replaced a dozen files that reported checksum errors, just tv shows though. Nearly all other errors are plex metadata issues which I don’t think is critical and dockers can be rebuilt if need be.
-
So I ssh with my admin account, did "cd /var/log" then i typed "dmesg" got a bunch of info and attached a copy here. When i try "message" i get command not found. I do "ls" and see there is indeed a "messages" file, not sure how much it pertains into finding clues to my issue. dmesg log.html
-
What should I be looking for in var/log are there are several files?
-
Gigabyte B365M DS3H, i5 8400, 2x JMB585 Ive never implemented any read/write caches ever. How do I go about access the /var/log?
-
I understand the part if there was some sort of file corruption prior to migrating to btrfs, it wouldn’t fix it. But the ******* ton of metadata errors with plex, and I wiped it all and it still comes back?? Has me confused. I mentioned memory because it’s what I read as a potential issue, HDDs were also a possibility but they don’t report any abnormalities. Another reason I perhaps thought memory, was because the issues started about a month after adding more modules. Maybe it was a coincidence, as removing them the problem persists.
-
I'm truly at a loss on what to do about this. I've attached a log file, just did a date range from Nov 1, 2020 to present. The only thing I can think of then was I had installed 2 memory modules around Nov 4 or 5th. I removed them in mid January but the problem still happens. I've also done a expansion to my pool, but after I was already getting checksum errors, I believe I did the expansion around the 10th-12th of December. I've tried with the Plex folder as its the worst, I unistalled plex, deleted the folder, and reinstalled plex and let it rebuilt the database\metadata, takes so long,, and the problem came back. Any suggestions on where to go next? Thanks syslog_2021-2-8-16 50 55.html
-
Tutorial - Modifying 1.04b Loader to Default to 24 Drives
merve04 replied to autohintbot's topic in Tutorials and Guides
possibly, -
Not sure if this has been asked around here, but I know many folks have been using NVME drives for r or r\w cache, but could I use a pair of SSD's in lieu? I would need to modify the drive count from 16 to 18 which i dont think thats too difficult.
-
I'm using a 16 bay hot swap rackmount case i ordered from alibaba, theres so many styles, it all came down to who could ship it at a reasonable price. It's nearly identical to a NORCO RPC-3216
-
Ok I’m kinda getting worried with no sight in finding the issue. This all started back in beginning of December, I was nearly a daily occurence, sometimes 2-5 events a day, 98% of the time related to something in the plex directory. I think it got so bad that recently dozens of items didn’t work in plex anymore yet the file if played say through VLC was fine. Things I’ve tried over the course of time, check parity, twice, defrag a few times as well. All HDDs show no signs of issues. I did double up the ram back in December, decided to rip it out just in case it was bad. I erased every trace of plex I could find and start fresh, still seeing checksum errors. Sometimes I’ve seen checksum errors on @docker folder, @appstore, @database twice of seen just a regular mp4/mkv file trigger checksum. Any ideas? thanks
-
Can I or has anyone ran this with xpenology?
-
- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 2 - Loader version and model: Jun's Loader v1.04b - DS918+ - Using custom extra.lzma: YES, IG-88's v0.13.3 - Installation type: BAREMETAL - Gigabyte B365M DS3H - Additional comments: Updated directly from DSM Control Panel. Reboot required.