January 10, 20251 yr I'm in the middle of changing my homeserver from a DELL R230 to a HPE DL20 Gen9 due to the facts that the HP has redundant power supplies and has way less depth for my rack. The Dell barely fits and is snug against my rack door which prohibits efficient airflow and gets the temps up to 70° sometimes even with an exhaust fan from the rack to the outside (with filters of course) I've configured the new to me HPE DL20 with the H240 to HBA Mode an can see 4 975GB SAS SSDs within SSA which I have sourced from other hardware (cleared beforehand, were used as boot drives). Also within unraid the drives seem to be mounted. SCSI Devices [0:0:0:0] disk JetFlash Transcend 16GB 1100 /dev/sda 15.7GB [1:0:1:0] disk SAMSUNG MZILT960HAHQ/0FU V302 /dev/sdb - [1:0:2:0] disk SAMSUNG MZILT960HAHQ/0FU V302 /dev/sdc - [1:0:3:0] disk SAMSUNG MZILT960HAHQ/0FU V302 /dev/sdd - [1:0:4:0] disk SAMSUNG MZILT960HAHQ/0FU V302 /dev/sde - From the system log i can see that it's reporting with 0B size Jan 10 01:49:33 btxSRV01 emhttpd: device /dev/sdb has size zero Jan 10 01:49:33 btxSRV01 emhttpd: device /dev/sdc has size zero Jan 10 01:49:34 btxSRV01 emhttpd: device /dev/sdd has size zero Jan 10 01:49:34 btxSRV01 emhttpd: device /dev/sde has size zero Jan 10 03:30:06 btxSRV01 kernel: hpsa 0000:06:00.0: scsi 1:0:0:0: added RAID HP H240 controller SSDSmartPathCap- En- Exp=1 Jan 10 03:30:06 btxSRV01 kernel: hpsa 0000:06:00.0: scsi 1:0:1:0: added Direct-Access SAMSUNG MZILT960HAHQ/0FU PHYS DRV SSDSmartPathCap- En- Exp=1 Jan 10 03:30:06 btxSRV01 kernel: hpsa 0000:06:00.0: scsi 1:0:2:0: added Direct-Access SAMSUNG MZILT960HAHQ/0FU PHYS DRV SSDSmartPathCap- En- Exp=1 Jan 10 03:30:06 btxSRV01 kernel: hpsa 0000:06:00.0: scsi 1:0:3:0: added Direct-Access SAMSUNG MZILT960HAHQ/0FU PHYS DRV SSDSmartPathCap- En- Exp=1 Jan 10 03:30:06 btxSRV01 kernel: hpsa 0000:06:00.0: scsi 1:0:4:0: added Direct-Access SAMSUNG MZILT960HAHQ/0FU PHYS DRV SSDSmartPathCap- En- Exp=1 Jan 10 03:30:06 btxSRV01 kernel: hpsa 0000:06:00.0: scsi 1:0:5:0: added Enclosure HP H240 enclosure SSDSmartPathCap- En- Exp=1 For me, everthing looks fine but the core system is unable to either access these ssd's or they are not getting mounted correctly via cli i can get the following regarding disks - also reporting size 0B root@btxSRV01:/dev# lsblk -o tran,name,type,size,vendor,model,label,rota,log-sec,phy-sec TRAN NAME TYPE SIZE VENDOR MODEL LABEL ROTA LOG-SEC PHY-SEC sas sdb disk 0B SAMSUNG MZILT960HAHQ/0FU 0 512 4160 sas sdc disk 0B SAMSUNG MZILT960HAHQ/0FU 0 512 4160 sas sdd disk 0B SAMSUNG MZILT960HAHQ/0FU 0 512 4160 sas sde disk 0B SAMSUNG MZILT960HAHQ/0FU 0 512 4160 smartctl on the ssds gives me normal output and capacity on all drives... endurance percentage is between 1 to 3% an all drives. root@btxSRV01:/dev# smartctl -a /dev/sdb smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.1.118-Unraid] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: SAMSUNG Product: MZILT960HAHQ/0FU Revision: V302 Compliance: SPC-5 User Capacity: 975,200,204,160 bytes [975 GB] Logical block size: 520 bytes Physical block size: 4160 bytes LU is resource provisioned, LBPRZ=1 Rotation Rate: Solid State Device Form Factor: 2.5 inches Logical Unit id: 0x5002538b49257690 Serial number: FM200086 Device type: disk Transport protocol: SAS (SPL-4) Local Time is: Fri Jan 10 03:45:35 2025 PST SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Disabled or Not Supported When I boot into a Server 2022 ISO I'm able to see all disks just fine and can create partitions/install on it as last troubleshooting measure I inserted a normal HPE SAS Drive (1,2TB HDD) into the drive bay... same outcome Server and components are updated via SPP 2022.08 (i think thats the latest for Gen9 servers) some components could get a newer fw version from a newer spp but i couldn't be bothered right now since latest SPPs wont start inventory so i would need to install linux or windows to do an online update. Also attached - the diagnostics of the unraid install. diagnostics-20250110-1232.zip
January 10, 20251 yr Author Solution ok guys... I've figured it out... googled everything I saw but not the line "emhttpd: device /dev/sdb has size zero" Solution was also within unraid forums so I'm just dumb enough to not search thoroughly enough about halfway down this thread i found the solution SAS Drive 520 sector size - General Support - Unraid Reformat a SAS HDD to different block sizes mainly 512 to use in UNRAID This took me a few hours to find and work out but was so much needed OK so I have just now done this for myself by installing sg3_utils onto my UNRAID OS using installpkg all using terminal 1. download the package into a tmp dir # wget http://slackware.cs.utah.edu/pub/slackware/slackware64-14.1/slackware64/l/sg3_utils-1.36-x86_64-1.txz 2. run this from that tmp dir after the download to install sg3_utils # upgradepkg --install-new sg3_utils-1.36-x86_64-1.txz 3. use this command to show SAS HDD's # sg_scan -i 4. this command to format 'obviously /dev/XXX should be the HDD u wish to format MAKE SURE ITS THE RIGHT ONE! # sg_format --format --size=512 -v /dev/XXX this has been allowing me to reformat the block size and use previously non usable drives saving buttonnes of money WARNING this format will destroy a HDD if interrupted during this process if you can a UPS is recommended have a great day I love UNRAID! only needed 3 and 4 ... after some time and rebooting the first disk is showing up SundarNET is the MVP here Edited January 10, 20251 yr by blacktronix
January 10, 20251 yr Community Expert Yep, didn't have a chance to look at the diags before: Jan 10 03:30:06 btxSRV01 kernel: sd 1:0:1:0: [sdb] Unsupported sector size 520.
January 10, 20251 yr Author yeah should have looked deeper into syslog but also it should have come upon me when I looked at the smartctl output... never to late to learn!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.