Moogs

Members
  • Content count

    45
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Moogs

  • Rank
    Junior Member
  1. Hello, Ive been running on xpenology for quite some time now, maybe 4 years or so. I own 8 legitimate camera licenses that Ive acquired over the years as my setup has grown. I recently added some more cameras and now I can't add the license. I get: Connection failed. Please check your network settings This is a new error for me. I've never had problems before. Any ideas what's changed or if there is a solution? 8.1.4.5498 version of Surveillance Station Running on bare metal DSM 6.1.6-15266 on DS3615xs model name HP Microserver Gen 8 with an external 8-bay array.
  2. Moogs

    DSM 6 - Missing 2 Disks

    bump, to get ahead of the spam and some help
  3. Moogs

    DSM 6 - Missing 2 Disks

    I have a Gen 8 HP server with 4 internal disks, these are fine. I have 8 external disks hooked up to a box over external HBA connections. Each connection runs 4 drives in a single 8 bay enclosure with two links in the back. 6 disks are seen, 2 are not and it shows 2 available slots. BIOS Post shows the drives fdisk -l shows the drives I have 5 USB devices, 12 drives, no eSata so: internalportcfg="0xfff" usbportcfg="0x1f000" esataportcfg="0x00000" maxdisks="12" Disk /dev/sda: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors 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: 61DA5485-7C44-4EB1-86D7-10941D7AE6F3 Device Start End Sectors Size Type /dev/sda1 2048 4982527 4980480 2.4G Linux RAID /dev/sda2 4982528 9176831 4194304 2G Linux RAID /dev/sda3 9437184 15627848351 15618411168 7.3T Linux RAID Disk /dev/sdb: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors 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: 1EB8E28F-1CD8-4363-A100-1235C7A6020C Device Start End Sectors Size Type /dev/sdb1 2048 4982527 4980480 2.4G Linux RAID /dev/sdb2 4982528 9176831 4194304 2G Linux RAID /dev/sdb3 9437184 15627848351 15618411168 7.3T Linux RAID Disk /dev/sdc: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors 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: BBF4EBA4-6606-42DD-B6AC-2B1F98A6E4BF Device Start End Sectors Size Type /dev/sdc1 2048 4982527 4980480 2.4G Linux RAID /dev/sdc2 4982528 9176831 4194304 2G Linux RAID /dev/sdc3 9437184 15627848351 15618411168 7.3T Linux RAID Disk /dev/sdd: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors 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: 6E04EA6E-2019-422B-B82A-58DF89374D6D Device Start End Sectors Size Type /dev/sdd1 2048 4982527 4980480 2.4G Linux RAID /dev/sdd2 4982528 9176831 4194304 2G Linux RAID /dev/sdd3 9437184 15627848351 15618411168 7.3T Linux RAID Disk /dev/sdg: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors 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: EB9DF917-6BDE-41E3-8E3E-920B18881A71 Disk /dev/sdh: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors 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: A49D3C16-6582-49EB-A37F-7A60231B8684 Disk /dev/sdi: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors 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: 4E97C4FD-83C7-4CAD-A962-B3E081E49E33 Disk /dev/sdj: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors 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: 460CB000-3C7F-49C1-9FAB-4ED3BF112348 Disk /dev/sdk: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors 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: 58E81A81-308C-4074-9357-80E2603C183E Disk /dev/sdl: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors 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: 79D981A7-CF22-431B-9249-AF5BF77B6E0C Disk /dev/sdm: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors 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: F028EE0A-3BB8-41AA-8B00-36085A6B708F Disk /dev/sdn: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors 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: C3D68369-2F4A-490B-9BE7-F97BEE965DEA I created a RAID group with the 6 drives that are available so it seems the last 2 drives are the ones that I can't use: Disk /dev/sdm: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors 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: F028EE0A-3BB8-41AA-8B00-36085A6B708F Disk /dev/sdn: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors 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: C3D68369-2F4A-490B-9BE7-F97BEE965DEA
  4. Moogs

    Jun's DSM 6 Loader - Driver List

    Worked out of the box with the 9205-8e. Good stuff.
  5. Moogs

    Jun's DSM 6 Loader - Driver List

    You're the man Polanskiman! Should cover the 2 cards I have.
  6. Moogs

    What's the point of DSM6?

    transmission works great on DSM 6. I was a long time 5.x even 4.x user back in the day. 6 has been great to me. Sickbeard is available, Couch Potato is available Mosquitto is available Looks like you need to add the community sources.
  7. Where can I find a list of drivers supported in jun's bootloader? Seems the threads have mixed the old loader with the newer jun's loader and I don't feel the drivers are supported on both.
  8. I would guesstimate being that it's based on a 12 disk NAS 12 disks @60TB
  9. Not sure if this has even really been documented here before but to create a USB on OS X do the following. I've had to create these for Ubuntu and other XPE* bootloaders. 1. Download the fat img of the bootloader of choice, I believe ext2 fs is also ok, for say Nanoboot. Make a note of its path. In this example we'll say it's saved to the Desktop and we'll use NanoBoot-5.0.2.4-fat.img 2. Plug your USB drive in. It may behoove you to use disk utility to create a FAT formatted partition to ensure there aren't any funky old parition schemes on there. Make it MBR: Choose the following options: Open terminal 1. Run diskutil list 2. Locate your USB drive: On the command line run: pwd should = /Users/ Unmount nanoboot parition: diskutil unmount /dev/disk2s1 (changed disk2s1 to whatever is listed as the DOS_FAT_32 NANOBOOT disk, not partition.). sudo dd if=~/Desktop/NanoBoot-5.0.2.4-fat.img of=/dev/disk2 bs=1m 15+1 records in 15+1 records out 16384000 bytes transferred in 21.031898 secs (779007 bytes/sec)
  10. Moogs

    LSI 9211-8i kernel issues

    I think I saw the same behavior in GnoBoot. I never looked at the logs but the first drive is not the first one in the order. This happens on two identical machines with the exact same disk load pattern. Not sure why but never sweated it. This is with a flashed 9211 LSI 8i card.
  11. The release notes claim to have the mpt2sas driver/module loaded so I am going to try it tonight.
  12. Moogs

    Gnoboot, Trantor, and now Nanoboot. Security?

    So it seems referencing some of the latest discussion in the nanoboot thread that bootloaders can manipulate the pat files regardless of their source. The case in point is where nanoboot slipstreams old 4458 files into the 4482 to "make it work" where it's really copying files from an older build. This to me means that anything can be moved over to the system from the bootloader software. Now that there's a release that supports LSI 9211 and Intel l210 NICs I'll give it a go and see if I can audit the communication outbound.
  13. Intel I210 NICs are likely not supported as they were in other bootloaders. I have the same boards.
  14. Any news on LSI 9211 HBA support?
  15. Moogs

    Push Service not working

    huh?