<div dir="ltr"><div dir="ltr">The HDD died. Luckily, I was smart enough to leave the second unused storage drive in that computing node.<div><br></div><div>root@gpu11$ lsblk<br>NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT<br>sda 8:0 0 1.8T 0 disk <br>└─sda1 8:1 0 1.8T 0 part <br>sdb 8:16 0 1.8T 0 disk <br>└─sdb1 8:17 0 1.8T 0 part /home/scratch2<br>nvme0n1 259:0 0 238.5G 0 disk <br>├─nvme0n1p1 259:1 0 1G 0 part /boot<br>└─nvme0n1p2 259:2 0 237.5G 0 part <br> ├─sl_gpu11-root 253:0 0 50G 0 lvm /<br> ├─sl_gpu11-swap 253:1 0 4G 0 lvm [SWAP]<br> └─sl_gpu11-home 253:2 0 183.5G 0 lvm /home<br></div><div><br></div><div><br></div><div>I just created <div><br></div><div>/home/scratch2</div></div><div><br></div><div>on /dev/sdb1</div><div><br></div><div>After the scheduled power outage, you should pull the dead drive out. I don't recall the drive bay label (not a file server so not very important), but since the server is going to be off, make sure you leave the NVMe drive and a 3.5" HDD with the following serial number.<br></div><div><br></div><div><br></div><div><br></div><div>=== GOOD DRIVE INFORMATION SECTION ===<br>Model Family: Seagate Enterprise Capacity 3.5 HDD<br>Device Model: ST2000NM0055-1V4104<br>Serial Number: ZC22SY3F<br></div><div><br></div><div>Cheers,</div><div>Predrag</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 4, 2023 at 1:48 PM Piotr Bartosiewicz <<a href="mailto:pbartosi@andrew.cmu.edu">pbartosi@andrew.cmu.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Problem with the scratch directory.<br></div>
</blockquote></div></div>