Jump to content
XPEnology Community

Benoire

Member
  • Posts

    239
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Benoire

  1. So another question, what happens to disk groups etc. if this change happens again on a new boot image release? At the moment, my HBA controller dumps a drive in a drive 1 within DSM and so my disk groups are not laid out like that. What happens to a disk group if the boot image causes the controllers to move them again? Will I lose access to the group and therefore data, or does DSM store the data by UUIDs and therefore knows which HDD is attached to which group? Thanks, Chris
  2. Solved this, appears to be a dodgy system partition on the drive I was trying to add to the group but nothing in the logs showed this. Only caught it on the main screen before it disappeared.
  3. Hi I've currently got DSM 5.2 installed. I can create single volumes per disk but everytime I try to create a SHR array, adding the drives does nothing and no disk group is created. Not sure where to look to find out why but I've re-installed DSM 5.2 multiple times and each time I am not able to create anything. Anyone else suffered this and have some pointers? Cheers, Chris
  4. Ok, so I went back to 5.1 as I had nothing on the drives and they all sorted themselves and booted in the right order. Upon updating the USB drive to Xpenology 5.2, booting in to 5.1 causes the messed up drive settings. It appears that something in the boot system may not be playing fair with my LSI raid card and the X7SPA-HF-D510 SATA ports to get them in the right order! @Trantor and other devs - Is it possible to set the order that SATA drives are hosted? For example, all motherboard based SATA first, followed by HBA's? Cheers, Chris
  5. Hi, I've just come back to Xpenology now that DSM 5.2 supports SMB3, well done to all involved. When I was running 5.1, my baremetal system (SM X7SPA-HF-D510) was numbering my 12 hotswap drive bays as 1-4 onboard SATA and then 5-12 LSI HBA in IT mode; effectively meaning that on the 12 bay display in DSM the left most drive corresponded to drive 1 and hence bay 1.. A perfect match! Now, running DSM 5.2 from scratch (no upgrade), Sata 1-4 is hotswap bays 2-5 and for some reason the HBA has drive 1 as its first drive, even though its connected to hotswap bay 5 and then 6-12. Is there anyway I can return this back to hotswap bay 1 attached to SATA 1 is drive 1 in Synology? Would make it easier to replace drives etc. Cheers, Chris
  6. No, the USB is simply used as a bootloader. The actual DSM software is installed on every HDD installed in the unit, so it does actually need the HDDs connected.
  7. That's a shame, thanks though. I was hoping to use block based LUNs for full speed for certain applications, will just have to use file based instead!
  8. I've got an issue with sharing a iSCSI LUN as the drive. I've I map it to the LUN as a block device, I can create it but I cannot share it and no client can connect. If I create a thin provisioned file, then it all works as normal. Is this an issue with the boot system or just likely to be a problem at my end?
  9. Ok so the group isn't dead. Running MDADM in Ubuntu has allowed me access to those directories that wouldn't show in DSM... Might need to reinstall DSM by the looks of it, unless running mdadm in Linux will recover the system enough for DSM to pick it back up again?
  10. Hi, I've got 3 HDDs in an SHR-1 config that was storing most of my data. Earlier today, the entire system (DSM update 4) became unusable and crashed. Force rebooting the machine started a consistency check on reboot and subsequently the SHR1 group became available, however I've now only got access to a small number of the shared folders that are on that SHR1 group. Trying to open up the folders, I get an 'Operation Failed' in Filebrowser and I cannot access the shares at all, even the ones that work, over the network. The Storage Manager still says I'm using 1.28TB out of 2.9TB which was about right so I don't know what is wrong. Is there anyway I can get access to all the data on the HDDs, or get a parity repair (I've run parity consistency check already once!). Thanks for any help! Chris
  11. Rightio, so mental note to self... Need to ensure that the DNS servers mentioned are actually running! My primary DC with DNS/DHCP on Xenserver had dropped out and while my secondary was working fine and therefore connections working DSM only had the primary in its box... D'oh. Still haven't fixed the issues with iSCSI though.
  12. So, it seems that I can't even add the community packages to the package list... No connection at all can be got outside of the network. Weird as the router is not set to block the ip of the device, and there are no blocks at my AD/DNS/DHCP level either.
  13. Hi CtrlAltDel, Nope, this is a clean install of DSM 5.1 as I was unable to migrate my 5.0 installation when I tried. Not sure what has happened as 5.0 apps where working fine with the same hardware. Its not SCSI I'm referring to but the iSCSI sharing protocol. It seems that creating a new volume and then a regular file lun with thin provisioning works fine, but as soon as I try and create a block level LUN, DSM screws up and windows cannot connect to the new target. Can only delete the target and LUN after resetting DSM via a full hardware reset (or IPMI in my case).
  14. Hi, Installed the fixed DSM 5.1 yesterday and all went well and so far not lost the drives, I do have a number of issues though. Firstly, I get connection errors when trying to access the app storage areas and so cannot install any apps, this connectivity also applies to checking for updates as it comes up with connection errors. The second issue relates to iSCSI and that trying to configure block level across a single LUN (1TB drive) creates problems in that Windows cannot see the newly created volume (but can when doing regular file iSCSI across the SHR pool with thin provisioning enabled) and when I try to delete the target or the LUN, DSM simply sits there waiting and then only way to kill it is to hard reset the machine. The system is running on a Supermicro X7SPA-HF D510 with 4GB Ram. The USB drive is installed to the internal Type A USB 2 slot and the main install exists on a 60GB SSD that is connected to SATA 0. I have 4 other drives connected to MB sata ports, with the LSI card currently connected but nothing attached. Has anyone else got similar issues to this, especially iSCSI? Thanks, Chris
×
×
  • Create New...