Jump to content

jbrubaker

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jbrubaker

  • Rank
    Newbie
  1. Thanks for your help. I stopped array, and mounted one of the array disks in Unassigned Devices. All the data I checked was intact. I unmounted it from Unassigned Devices, and with it unassigned from the array, I started the array. The emulated disk mounted and as far as I can tell the data still looks good, so I think I can proceed to rebuilding the disk. Running the first disk rebuild now.
  2. Thank you both for your replies. I attempted the disk move tonight, and as predicted, Unraid said the disks were missing when I booted and "Wrong" when I selected the appropriate disk. I created a new config as recommended by @trurl, checked "Parity already valid", and started the array, then got the "Unmountable: Unsupported partition layout" on each of the disks (except parity) that had been connected to the previous RAID controller (now on the Dell H310). When the system was booting, I believe I saw something flash by about the GPT layout sector something not being at the end of disk or something. I did some Googling and couldn't find many useful hints at what to try. Any thoughts? Edit: Found this in the log: "Alternate GPT header not at the end of the disk" Dec 1 23:42:30 Hyperion kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 1 23:42:30 Hyperion kernel: ata4.00: ATA-9: ST3000DM001-1ER166, Z501REW5, CC25, max UDMA/133 Dec 1 23:42:30 Hyperion kernel: ata4.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 32), AA Dec 1 23:42:30 Hyperion kernel: ata4.00: configured for UDMA/133 Dec 1 23:42:30 Hyperion kernel: scsi 4:0:0:0: Direct-Access ATA ST3000DM001-1ER1 CC25 PQ: 0 ANSI: 5 Dec 1 23:42:30 Hyperion kernel: sd 4:0:0:0: Attached scsi generic sg3 type 0 Dec 1 23:42:30 Hyperion kernel: sd 4:0:0:0: [sdd] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) Dec 1 23:42:30 Hyperion kernel: sd 4:0:0:0: [sdd] 4096-byte physical blocks Dec 1 23:42:30 Hyperion kernel: sd 4:0:0:0: [sdd] Write Protect is off Dec 1 23:42:30 Hyperion kernel: sd 4:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Dec 1 23:42:30 Hyperion kernel: sd 4:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 1 23:42:30 Hyperion kernel: mpt2sas_cm0: host_add: handle(0x0001), sas_addr(0x5000000080000000), phys(8) Dec 1 23:42:30 Hyperion kernel: GPT:Primary header thinks Alt. header is not at the end of the disk. Dec 1 23:42:30 Hyperion kernel: GPT:5859352575 != 5860533167 Dec 1 23:42:30 Hyperion kernel: GPT:Alternate GPT header not at the end of the disk. Dec 1 23:42:30 Hyperion kernel: GPT:5859352575 != 5860533167 Dec 1 23:42:30 Hyperion kernel: GPT: Use GNU Parted to correct GPT errors. Dec 1 23:42:30 Hyperion kernel: sdd: sdd1
  3. An update was just pushed to the spaceinvaderone/Macinabox repo on github. The (foxlet fetch-macos.py) script which fetches the disk image from Apple was grabbing the wrong ID. The new push changes the parameters passed to that, which in turn fetches the correct Catalina image. Mine was fetching Mojave instead of Catalina. I deleted the old VM and the Macinthebox container. Re-installed the docker from CA, and now it is correctly pulling Catalina.
  4. First post. Be kind? I've been running Unraid (currently 6.7.2) for about 4 months now. My SuperMicro dual Xeon server has developed some issues, possibly related to a power outage or insufficient cooling. At any rate, I'm putting together a new-from-used-parts machine (Ryzen 7 2700X, X370) and want to move the drives (and the Unraid USB) to the new machine. Google (and this forum) tell me that Unraid should have no problem identifying the drives and placing them in the correct slot in the array when I first boot the new build. However, I'm a little worried that it will work correctly with my setup. My SuperMicro is using a 9650SE-12ML RAID card which does not support IT mode. The drives are setup in "single" mode in the card config, but the controller still sits in front of the disks and prevents "direct" access (e.g. blocks SMART, etc.) and changes the drive identifier string. Here's one of my disks on the RAID controller with the id string: Oct 29 20:56:25 Hyperion kernel: md: import disk0: (sdf) 9650SE-12M_DISK_D88RER0842FC52006B26_3600050e042fc52006b26000021e80000 size: 5859363788 I am putting an IT-mode RAID card in the new box (Dell H310, LSI 2008) to get SMART support. I am pretty sure that after I swap the drives to the new system/controller and boot Unraid, the disk identifier for each disk is going to be different on the new controller. Do I simply need to make a note of each drive's actual identifier and then manually match them up with the appropriate slots in Array Devices when I boot the new hardware with the old drives (see attachment)? Am I making this too complicated? Am I missing something else important. Thanks for any guidance.