December 27, 20169 yr I was poking around my flash drive on another issue and found this file. It appears to be a file created (daily?) containing all of your disk assignments. I've been religiously recording these data points separately because of the importance of being able to connect disk assignments. If this file is being created everyday, then is there a reason we couldn't use this? i.e. back it up daily to a local drive. The only data points missing are the linux device name (i.e. sda, sdb, sdc, etc). So a couple of questions... 1. What creates this file? 2. Is it created daily? 3. Could it be enhanced to also include the device name? Is there another app out there that automatically backs up the drive mappings/info needed to rebuild?
December 27, 20169 yr The Linux device name can change across reboots for a given drive so why do you think it is needed?
December 27, 20169 yr It's created whenever CA backs up the flash Sent from my SM-T560NU using Tapatalk
December 29, 20169 yr Author The Linux device name can change across reboots for a given drive so why do you think it is needed? Did not know that the device name changes across reboots. So "SDF on Disk4" isn't always "SDF on Disk4"? I've never noticed those changing, except when a new device has been added. Aren't these device name/drive numbers required when recovering a system? I've never had to recover an unraid system yet (sound of wood being knocked), but I've been there many times before on other OS's, but my understanding is that the device name and disk name pairs are critical to recovery? Am I misinformed?
December 29, 20169 yr The Linux device name can change across reboots for a given drive so why do you think it is needed? Did not know that the device name changes across reboots. So "SDF on Disk4" isn't always "SDF on Disk4"? I've never noticed those changing, except when a new device has been added. Aren't these device name/drive numbers required when recovering a system? I've never had to recover an unraid system yet (sound of wood being knocked), but I've been there many times before on other OS's, but my understanding is that the device name and disk name pairs are critical to recovery? Am I misinformed? Device names aren't important. The disk serial number and position are what's important.
December 29, 20169 yr The Linux device name can change across reboots for a given drive so why do you think it is needed? Did not know that the device name changes across reboots. So "SDF on Disk4" isn't always "SDF on Disk4"? I've never noticed those changing, except when a new device has been added. Aren't these device name/drive numbers required when recovering a system? I've never had to recover an unraid system yet (sound of wood being knocked), but I've been there many times before on other OS's, but my understanding is that the device name and disk name pairs are critical to recovery? Am I misinformed? Device names aren't important. The disk serial number and position are what's important. Where position means assigned slot number.
January 6, 20179 yr Author Device names aren't important. The disk serial number and position are what's important. Where position means assigned slot number. Ergo this data is critical...SN and Disk # must match... http://my.jetscreenshot.com/12412/20170106-hj24-93kb.jpg[/img]
January 6, 20179 yr ... Ergo this data is critical...SN and Disk # must match... Actually, the positions do NOT matter with single parity (as shown in your screenshot) -- except of course the parity drive must be correctly assigned. They DO matter with dual parity. They also mattered even with single parity on early v6.2 releases, but Tom indicated this would be corrected ... I assume (but do not know for certain) that this has been fixed in the latest release.
January 6, 20179 yr And of course they also matter if you use specific disks in specific ways. For example, if you have a user share set to include only disk1 and disk2, and you move those disks to another slot, you would have to adjust the user share settings if you wanted to continue to keep those files with those disks.
January 6, 20179 yr But the net result either way is that the contents of DISK_ASSIGNMENTS.txt is correct as is
January 6, 20179 yr FWIW, those disks look to be a tad on the warm side. Is it summer where you are, JWH?
January 6, 20179 yr Author FWIW, those disks look to be a tad on the warm side. Is it summer where you are, JWH? Its always sunny in Wisconsin! Except when its not. 6F today. The server is in a cabinet, so it gets warm when a parity check happens. I usually open the door and all is well. But yes, often get warnings about a hot drive. I think my next server will move to the basement and be in a rack. http://my.jetscreenshot.com/12412/20170106-92nz-202kb.jpg[/img]
January 6, 20179 yr I have mine in a cabinet too, but I installed temperature-controlled fans in the cabinet.
January 7, 20179 yr Author I have mine in a cabinet too, but I installed temperature-controlled fans in the cabinet. Yeah, I had a fan too, but way too noisy. Just need to find a quiet one...
January 7, 20179 yr I have mine in a cabinet too, but I installed temperature-controlled fans in the cabinet. Yeah, I had a fan too, but way too noisy. Just need to find a quiet one... I got mine at CoolerGuys.
January 7, 20179 yr I've used several of the fans from Coolerguys => they work very nicely and aren't at all noisy.
January 11, 20179 yr Author I've used several of the fans from Coolerguys => they work very nicely and aren't at all noisy. Thanks! They have some very nice units, some with temp sensors. Definitely going to check this out further...
Archived
This topic is now archived and is closed to further replies.