Recent content by GazdaJezda

Of course (maybe I was not clear enough), my goal is latest full patched version.

Ok, thank you. System (boot) partition is ext4 and I would like to keep it that way. First I need upgrade to final version of 7 - I hope that issue would not be the case here already! Because I'm more affraid about NIC name changes (all NIC's are onboard / Supermicro board). I'm expecting this...

Thank you guys. I need to find some time and then I will fire upgrade (6 to 7). I think I use it although I don't understand completely to what you refer? I have a Proxmox on separate SSD drive (ext4) and VM's are on raidz ZFS volume (4 x 2TB SSD's). Also, i think (i will need to check it) I'm...

Unfortunatelly guys, I need to ask again: can I still upgrade my current 6.4 PVE to 7.x or I will break something because it is too old and something vital is missing on the net / repositories? I know it is old, but is constantly have other things active and this one just works :) I need to...

Thank you all. I will first read upgrade guide and then see. Currently I'm on last 6.4 version. I have daily backup's of /etc/ , VM's... for 14 day back. Buying new disc and install latest proxmox on it is no brainer, but configuring it back to old settings can be (for me). I have system on one...

Hi! I know, I'm terrible, but so far there has been no need to upgrade, everything still works without problems. However, time flies and it will be necessary to upgrade my ProxMox box from the current version 6.4 to the current one. The most problematic (i believe) will be the first part, from...

Ok, but then I cannot believe that Samsung is such a s**t. Because go down after less than 1 Tb written is not normal for me. But ok, this disk is only bootable. Now I can see how can I cope with it, so backups of config files are made every day to external drive so this is it. And yes, going...

;)

I do not know. I bought discs, put in server and install PVE. After configuration I pur server in rack and forget about it. Didn't bother with disc's firmware. But yes, Samsung page said so: So then there was possible failed write operation or similar. Eh, forget it... :)

As I thought, same on all 860 drives: Last one (sdd) is a new disc (870).

Disc on a picture is old one, picture was send to me by HW reseller. That disc (original EVO 970) is now officialy dead and will get new one. Magician is Windows app yes, it was used just to confirm that BIOS and other S.M.A.R.T. readings are valid - that disc is @EOL. After 3 years and a...

Yes. So I still have 3 discs in machine with I believe same firmware, since they were all bought at same time from same seller (Amazon) :)

UPDATE - Disc is definitely broken and since it is still in warranty will be replaced for free... But still, it happened after not even 1 Tb written...

UPDATE - Just to let you know: I return both failed discs (NVME EVO 970 and SSD EVO 860) to my HW provider. First disc (970 - boot disc) is definitely bad, but still in 5 year warranty so will be changed for free. Second one (860 - this thread's main actor) was examined and after some...

Scrub finished without errors. It seems fine. Thank you all again! Cheers! Now I can freely go to Tuscany :) P.S. - about p1,p9 partitions: since new device have been put to same 'slot', is that maybe reason why partitions were there? I dont know other reasons, definitely i wasn't copy...