F5F Stay Refreshed Hardware Desktop Upgrading to a different interface won't allow the system to start.

Upgrading to a different interface won't allow the system to start.

Upgrading to a different interface won't allow the system to start.

Q
QuasarOne
Junior Member
Find
9
10-04-2016, 06:15 PM
#1
Long time observer, first-time contributor. I have a peculiar setup I suspect might be overlooked. I own an Amazon firewall appliance purchased recently, and I want to upgrade it with a bigger NVMe storage as the existing one only offers 128GB. I bought a new 512GB drive last week, but when I try to install it, the system fails to power on. I also used a 256GB drive I found, hoping it matched the size, but it didn’t work either. If I revert to the old NVMe, it boots up fine—no issues there. Both faulty NVMe units I installed function correctly on other platforms, which made me doubt their reliability. I checked the BIOS for any relevant settings, but they seem standard and didn’t help. I reset the CMOS and tried it again, but nothing changed. The motherboard lists as N5105. The working drive is identified by SM2263XT_BGA132X4_M2_V01_6L_T1216, but the model number on it is incomplete. It seems my concern might be missing something obvious. Anyone have ideas I might have overlooked? Appreciate your input!
Reply
Reply
Q
QuasarOne
10-04-2016, 06:15 PM #1

Long time observer, first-time contributor. I have a peculiar setup I suspect might be overlooked. I own an Amazon firewall appliance purchased recently, and I want to upgrade it with a bigger NVMe storage as the existing one only offers 128GB. I bought a new 512GB drive last week, but when I try to install it, the system fails to power on. I also used a 256GB drive I found, hoping it matched the size, but it didn’t work either. If I revert to the old NVMe, it boots up fine—no issues there. Both faulty NVMe units I installed function correctly on other platforms, which made me doubt their reliability. I checked the BIOS for any relevant settings, but they seem standard and didn’t help. I reset the CMOS and tried it again, but nothing changed. The motherboard lists as N5105. The working drive is identified by SM2263XT_BGA132X4_M2_V01_6L_T1216, but the model number on it is incomplete. It seems my concern might be missing something obvious. Anyone have ideas I might have overlooked? Appreciate your input!

Reply
Reply
K
KYUUBl
Member
Find
106
10-05-2016, 02:38 AM
#2
The system's hang or failure to start usually stems from BIOS or firmware issues. Does this firewall support updating its firmware?
Reply
Reply
K
KYUUBl
10-05-2016, 02:38 AM #2

The system's hang or failure to start usually stems from BIOS or firmware issues. Does this firewall support updating its firmware?

Reply
Reply
K
kroko_53
Junior Member
Find
34
10-05-2016, 06:55 AM
#3
You're looking for a solution to reduce the size of a firewall device while maintaining its performance. Most systems require only 128Gb for adequate functionality.
Reply
Reply
K
kroko_53
10-05-2016, 06:55 AM #3

You're looking for a solution to reduce the size of a firewall device while maintaining its performance. Most systems require only 128Gb for adequate functionality.

Reply
Reply
M
magiccheese7
Junior Member
Find
16
10-16-2016, 07:19 PM
#4
Consulting the manufacturer regarding the BIOS is a smart move for an update. This setup is part of a ProxMox cluster, and I’m currently running just the PFSense VM. I’m considering adding a bigger NVMe drive to store prebuilt VMs for the rest of the cluster. My aim is to install a 512GB NVMe for storage, though the system will only boot with the 128GB drive installed at the moment.
Reply
Reply
M
magiccheese7
10-16-2016, 07:19 PM #4

Consulting the manufacturer regarding the BIOS is a smart move for an update. This setup is part of a ProxMox cluster, and I’m currently running just the PFSense VM. I’m considering adding a bigger NVMe drive to store prebuilt VMs for the rest of the cluster. My aim is to install a 512GB NVMe for storage, though the system will only boot with the 128GB drive installed at the moment.

Reply
Reply