<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>
<div>Do you have a drive dock or rescue kit? You might test your drives singly in it. You can also get UUID's from the filesystem(s) on the working drives while they're in the dock.</div><div><br></div><div>I hope the server's data and config are backed up.</div><div><br></div><div>Switching to UUID-based mounting as soon as reasonably possible is a great idea. Make sure to save fstab often and maybe check it into git so you have revisions.</div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757">Sent from my Verizon Wireless 4G LTE smartphone</div></div><br><br>-------- Original message --------<br>From: foo7775@comcast.net <br>Date: 6/12/2016 1:48 PM (GMT-07:00) <br>To: "list, CLUE" <clue@cluedenver.org> <br>Subject: [clue] HDD "shell game" issue <br><br><div style="font-family: Arial; font-size: 12pt; color: #000000"><div aria-label="Compose body">Hi All,<br></div><div aria-label="Compose body"><br></div><div aria-label="Compose body"> I've run into a situation that has me puzzled (& a little bit humbled, actually). I have a server that started out with five drives, sda - sde (no RAID, no LVM). The sde drive has been throwing alerts for a few days, so I went in to the DC to replace it. The drives are hot-swappable, so I didn't expect much problem - but when I inserted the new drive, the server appeared to not detect it - and started to generate alerts for the sdB drive as well. (I'm sure that at least a couple of you can probably see where this is going...)<br></div><div aria-label="Compose body"><br></div><div aria-label="Compose body"> After puzzling over the problem for a little while, I found that the new drive had (appropriated|been assigned to) the sdB slot, rather than sdE like I had expected. At that point, I started trying to collect info so that I could recreate the fstab file using 'mount-by-uuid' - but regardless of what configuration I try, I can't seem to get the original sdB drive to reappear:<br></div><div aria-label="Compose body"><br></div><div aria-label="Compose body"> If I boot with the drive slot open, I get sda, sdc & sdd.<br></div><div aria-label="Compose body"><br></div><div aria-label="Compose body"> If I boot with the drive slot holding the bad/original drive, the server shows sda through sdd.<br></div><div aria-label="Compose body"><br></div><div aria-label="Compose body"> If I boot with the drive slot holding the new/unformatted drive, the boot process fails when it's unable to complete checking the drives (server's been up for >450 days), & I had to boot from a rescue drive & comment out the sdb entry in fstab to get the server to complete booting.<br></div><div aria-label="Compose body"><br></div><div aria-label="Compose body"> The worst part of dealing with this is that I *know* that it's not a really complex issue - but I am just not seeing how to restore the server to proper function (which has me feeling distinctly inept). I'm sure that there's data that I've forgotten to provide here, so if anyone has any questions, I'll do my best to answer them.<br></div><div aria-label="Compose body"><br></div><div aria-label="Compose body">I would really appreciate any thoughts/suggestions that anyone can provide.<br></div><div aria-label="Compose body"><br></div><div aria-label="Compose body">Thanks in advance.<br></div></div></body></html>