Intel NUC
Yet another move in order to save some energy costs and gain some sanity when the main server is shut down in order to stop generating noise happened the other day – most of the nodes are now on an Intel NUC i3, 10th gen.
The new toy is equipped with 64G of SO-DIMM DDR4 RAM, and seems to be pretty good and capable running all of the hosts transferred from the big brother.
While waiting for more Noctua silent fans for the big beast, a hefty part of Simulakrum will run on this tiny one.
One of the immediate issues I had was when trying to use SEDNA hard-disk enclosure (now equipped with Seagate Barracudas) via the USB gen 3 cable; adding the quirks for the device was not fruitful:
echo options usb-storage quirks=174c:55aa:u | tee /etc/modprobe.d/blacklist_uas.conf
dracut -f /boot/initramfs-5….something here
would not help the NUC recognize the disks:
[ 58.173980] usb 2-2: reset SuperSpeedPlus Gen 2 USB device number 6 using xhci_hcd
[ 58.186569] usb 2-2: can't restore configuration #1 (error=-71)
[ 58.193781] usb 2-2: USB disconnect, device number 6
[ 58.388800] usb 2-2: new SuperSpeedPlus Gen 2 USB device number 7 using xhci_hcd
[ 58.401522] usb 2-2: string descriptor 0 read error: -71
[ 58.401527] usb 2-2: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00
[ 58.401530] usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 58.403034] usb 2-2: Set SEL for device-initiated U1 failed.
[ 58.403191] usb 2-2: Enable of device-initiated U2 failed.
[ 58.403288] usb 2-2: UAS is ignored for this device, using usb-storage instead
[ 58.403290] usb-storage 2-2:1.0: USB Mass Storage device detected
[ 58.407801] usb-storage 2-2:1.0: Quirks match for vid 174c pid 55aa: c00000
[ 58.409761] scsi host3: usb-storage 2-2:1.0
[ 58.672746] br0: port 5(vnet3) entered learning state
[ 59.696730] br0: port 6(vnet4) entered learning state
[ 60.720718] br0: port 7(vnet5) entered learning state
[ 61.745707] br0: port 8(vnet6) entered learning state
[ 62.257696] br0: port 9(vnet7) entered learning state
[ 62.768696] br0: port 10(vnet8) entered learning state
[ 63.513717] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
[ 63.792683] br0: port 11(vnet9) entered learning state
[ 64.137675] hrtimer: interrupt took 6090 ns
[ 64.502678] usb 2-2: USB disconnect, device number 7
[ 64.816683] br0: port 12(vnet10) entered learning state
[ 65.622725] usb 2-2: new SuperSpeedPlus Gen 2 USB device number 8 using xhci_hcd
[ 65.635363] usb 2-2: string descriptor 0 read error: -71
[ 65.635369] usb 2-2: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00
[ 65.635372] usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 65.637122] usb 2-2: can't set config #1, error -71
…
[ 5197.834765] usb 2-4.1: UAS is ignored for this device, using usb-storage instead
[ 5197.834773] usb-storage 2-4.1:1.0: USB Mass Storage device detected
[ 5197.835030] usb-storage 2-4.1:1.0: Quirks match for vid 174c pid 55aa: c00000
[ 5197.835137] scsi host4: usb-storage 2-4.1:1.0
[ 5198.882506] scsi 4:0:0:0: Direct-Access SEDNA ASM1352R-Fast 0 PQ: 0 ANSI: 6
[ 5198.883473] sd 4:0:0:0: Attached scsi generic sg0 type 0
[ 5198.885683] sd 4:0:0:0: [sdb] 15628042241 512-byte logical blocks: (8.00 TB/7.28 TiB)
[ 5198.885695] sd 4:0:0:0: [sdb] 4096-byte physical blocks
[ 5198.885953] sd 4:0:0:0: [sdb] Write Protect is off
[ 5198.885961] sd 4:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 5198.886198] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5198.938155] sd 4:0:0:0: [sdb] Attached SCSI disk
Yet, using the front USB-C port as “slow” allowed the kernel to use the SEDNA hard disk enclosure, here in RAID0:
[ 5197.819649] usb 2-4.1: new SuperSpeed Gen 1 USB device number 116 using xhci_hcd
[ 5197.832859] usb 2-4.1: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00
[ 5197.832874] usb 2-4.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 5197.832880] usb 2-4.1: Product: ASM1352R-Fast
[ 5197.832884] usb 2-4.1: Manufacturer: SEDNA
[ 5197.832888] usb 2-4.1: SerialNumber: 2018092100BE
[ 5197.834765] usb 2-4.1: UAS is ignored for this device, using usb-storage instead
[ 5197.834773] usb-storage 2-4.1:1.0: USB Mass Storage device detected
[ 5197.835030] usb-storage 2-4.1:1.0: Quirks match for vid 174c pid 55aa: c00000
[ 5197.835137] scsi host4: usb-storage 2-4.1:1.0
[ 5198.882506] scsi 4:0:0:0: Direct-Access SEDNA ASM1352R-Fast 0 PQ: 0 ANSI: 6
[ 5198.883473] sd 4:0:0:0: Attached scsi generic sg0 type 0
[ 5198.885683] sd 4:0:0:0: [sdb] 15628042241 512-byte logical blocks: (8.00 TB/7.28 TiB)
[ 5198.885695] sd 4:0:0:0: [sdb] 4096-byte physical blocks
[ 5198.885953] sd 4:0:0:0: [sdb] Write Protect is off
[ 5198.885961] sd 4:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 5198.886198] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5198.938155] sd 4:0:0:0: [sdb] Attached SCSI disk
[root@dionysus ~]# parted /dev/sdb
GNU Parted 3.4
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Error: /dev/sdb: unrecognised disk label
Model: SEDNA ASM1352R-Fast (scsi)
Disk /dev/sdb: 8002GB
Sector size (logical/physical): 512B/4096B
Partition Table: unknown
Disk Flags:
(parted) mklabel gtp
parted: invalid token: gtp
New disk label type? mklabel gpt
parted: invalid token: mklabel
New disk label type? gpt
(parted) print
Model: SEDNA ASM1352R-Fast (scsi)
Disk /dev/sdb: 8002GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
(parted) quit
Information: You may need to update /etc/fstab.
[root@dionysus ~]# fdisk -l /dev/sdb
Disk /dev/sdb: 7.28 TiB, 8001557627392 bytes, 15628042241 sectors
Disk model: ASM1352R-Fast
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 64436EEE-8937-476A-BEEF-2861F7D426B5
[root@dionysus ~]# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.36.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdb: 7.28 TiB, 8001557627392 bytes, 15628042241 sectors
Disk model: ASM1352R-Fast
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 64436EEE-8937-476A-BEEF-2861F7D426B5
Command (m for help): n
Partition number (1-128, default 1):
First sector (34-15628042207, default 2048):
Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-15628042207, default 15628042207):
Created a new partition 1 of type 'Linux filesystem' and of size 7.3 TiB.
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
[root@dionysus ~]# mkfs.ext4 /dev/sdb1
mke2fs 1.45.6 (20-Mar-2020)
Creating filesystem with 1953505020 4k blocks and 244191232 inodes
Filesystem UUID: 0a845adf-dfed-4386-b991-e7f389acf309
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544, 1934917632
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
[root@dionysus ~]# mount /dev/sdb1 /mnt/
[root@dionysus ~]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 32G 0 32G 0% /dev
tmpfs 32G 0 32G 0% /dev/shm
tmpfs 13G 2.3M 13G 1% /run
/dev/nvme0n1p3 930G 525G 405G 57% /
/dev/nvme0n1p3 930G 525G 405G 57% /home
/dev/nvme0n1p2 976M 234M 676M 26% /boot
tmpfs 32G 472K 32G 1% /tmp
/dev/nvme0n1p1 599M 31M 569M 6% /boot/efi
tmpfs 6.3G 44K 6.3G 1% /run/user/0
tmpfs 6.3G 60K 6.3G 1% /run/user/42
tmpfs 6.3G 128K 6.3G 1% /run/user/1000
/dev/sdb1 7.3T 93M 6.9T 1% /mnt
[root@dionysus ~]# umount /mnt
[root@dionysus ~]#
mount /dev/disk/by-uuid/0a845adf-dfed-4386-b991-e7f389acf309 /mnt/
Interestingly enough, my MacBooks were able to use SEDNA enclosure as-is immediately.
I’ll be mostly interested in the cost savings here, and I can already see the average consumption is some 30W less.
A good start.