Really slow on SSD in HP z820 - openSuSE issue?
Posted: Fri Aug 23, 2024 8:35 pm
Here do be an oddity and I must confess to being befuddled. Part of this is a brain dump because writing these things down helps me thing.
I have an HP z820. 20-core with 128GB of RAM. There are 2 CPU having 10-core each. I have a 1TB SSD boot drive; 6TB WD Black spinning disk; 2TB WD Blue spinning disk. There are two different built in disk controllers. One is an LSI SAS 2308 RAID controller that loads its firmware from some burnt EPROM thing for security purposes. All 8 connectors for it are 6Gb/s. Second controller is Intel C600 PCH and is "just there." Provides four 3 Gb/s ports and 2 6Gb/s ports.
I have a really nice 4TB drive in external enclosure connected via USB 3.x cable on USB 3.x port out back. This is my backup target.
The OS on there is currently openSuSE Leap 15.6 but that should be irrelevant. Boot is very fast once the BIOS gets done loading its LSI firmware.
Right now the two spinning drives have just over half the data the SSD has. Backing up the SSD is over 40 minutes. Both the spinning disks are under 5 minutes. I swapped out the Samsung EVO 840 today for some brand new latest and greatest SSD thinking the 840 is older tech (which it is) and might be the problem. I'm over an hour into the restore and it says I still have over an hour to go.
Just for grins, before I got this far I stuck in a 1TB WD Blue spinning disk and the restore to it was going at the same pace. I was willing to believe there was an issue with the drivers being loaded for "vintage" controllers.
While typing this I looked over at the display and noticed the total restore is 801.something GB. There is no where near that on the drive.
Does Drive Image have a no-likey situation going on with whatever the disk/partition format is that openSuSE uses by default?
I can understand now, if that is the case. I've had success with Drive Image for so long I never considered it was backing up every block on the drive because it couldn't handle the partition format. Really need to use Leap on that machine though. Would seriously hate to have to wipe and re-install trying to force SuSE to use a different partition type.
Oh, Image for Linux 4.01.
I have an HP z820. 20-core with 128GB of RAM. There are 2 CPU having 10-core each. I have a 1TB SSD boot drive; 6TB WD Black spinning disk; 2TB WD Blue spinning disk. There are two different built in disk controllers. One is an LSI SAS 2308 RAID controller that loads its firmware from some burnt EPROM thing for security purposes. All 8 connectors for it are 6Gb/s. Second controller is Intel C600 PCH and is "just there." Provides four 3 Gb/s ports and 2 6Gb/s ports.
I have a really nice 4TB drive in external enclosure connected via USB 3.x cable on USB 3.x port out back. This is my backup target.
The OS on there is currently openSuSE Leap 15.6 but that should be irrelevant. Boot is very fast once the BIOS gets done loading its LSI firmware.
Right now the two spinning drives have just over half the data the SSD has. Backing up the SSD is over 40 minutes. Both the spinning disks are under 5 minutes. I swapped out the Samsung EVO 840 today for some brand new latest and greatest SSD thinking the 840 is older tech (which it is) and might be the problem. I'm over an hour into the restore and it says I still have over an hour to go.
Just for grins, before I got this far I stuck in a 1TB WD Blue spinning disk and the restore to it was going at the same pace. I was willing to believe there was an issue with the drivers being loaded for "vintage" controllers.
While typing this I looked over at the display and noticed the total restore is 801.something GB. There is no where near that on the drive.
Does Drive Image have a no-likey situation going on with whatever the disk/partition format is that openSuSE uses by default?
I can understand now, if that is the case. I've had success with Drive Image for so long I never considered it was backing up every block on the drive because it couldn't handle the partition format. Really need to use Leap on that machine though. Would seriously hate to have to wipe and re-install trying to force SuSE to use a different partition type.
Oh, Image for Linux 4.01.