Posts made by AdamF

@DustinB3403 Meaning rebuild the RAID array itself? Yes, twice now. Destroyed the array, recreated a RAID 10 array, initialized the array, and then installed XS. During the install, it asks where to store the VMs (the wording might be off here) and I am able to select the array itself. So XS is seeing the array, but not actually making it available as a SR.

@Danp

Was just about to post this. I tried to do a fsck on the drive. See below screenshot.

@momurda No, I didn't format the lv. Is that something done during the installation?

@momurda said in XenServer installation SR issue:

what is the output of vgs, lvs, pvs from the console?
Seems like either your lvm layer is bad, or the actual raid array is bad.
Have you tried to unmount this and then runs fsck?

Really weird that the local sr wasn't auto created for after install. It is like the first thing that happens when you connect to XS with XC.
Since it is not working you could just reinstall and try again, there shouldn't be an thing on it at this point.

[root@xenserver ~]# vgs
  VG                                              #PV #LV #SN Attr   VSize VFree
  XSLocalEXT-0bff8e3b-dd7c-c3c4-3125-22569f5bbd77   1   1   0 wz--n- 5.42t    0

[root@xenserver ~]# lvs
  LV                                   VG                                              Attr       LSize Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  0bff8e3b-dd7c-c3c4-3125-22569f5bbd77 XSLocalEXT-0bff8e3b-dd7c-c3c4-3125-22569f5bbd77 -wi-a----- 5.42t

[root@xenserver ~]# pvs
  PV         VG                                              Fmt  Attr PSize PFree
  /dev/sda3  XSLocalEXT-0bff8e3b-dd7c-c3c4-3125-22569f5bbd77 lvm2 a--  5.42t    0

And yes, I've reinstalled twice. The second time, I completely destroyed the RAID array, and created a new one. Then ran a Fast Init on it and install XS. That's all I've done to get to the point of error.

@Danp said in XenServer installation SR issue:

@fuznutz04 That was for the xe pbd-create? Did you try performing the xe pbd-plug?

[root@xenserver ~]# xe pbd-plug uuid=484dbd7d-08b0-0305-eae8-c59ebea39a36
Error code: SR_BACKEND_FAILURE_52
Error parameters: , Logical Volume mount/activate error [opterr=FSCK failed on /dev/XSLocalEXT-0bff8e3b-dd7c-c3c4-3125-22569f5bbd77/0bff8e3b-dd7c-c3c4-3125-22569f5bbd77. Errno is 8],

@Danp I did that.. Twice already. Brand new installations

@Danp yes, also an error. I just stepped away from my desk so don't remember what it was at the moment

@Danp Following that guide.... " A PBD already exists connecting the SR to the host"

@Danp I dont even see my disks in XC...

Never mind on that last question... I see it in the pic now.

@JaredBusch

I'm using one of those at another location with a similar paging system. But it's a more Basic system that just accepts an audio feed. The thing that is throwing me off with this paging system is the fact that it delivers dial tone . It's a Raulands Telecenter V. If I can't get this working via an ATA, I'll have to see if it will accept just an audio feed from a Snom. In your setup, where are you connecting the snom to the pagin system? via the red/black audio jacks on the back of the snom?

Does it matter that I installed XS on the actual RAID 10 array that I want to use for storage?

No, thats when I get the error in the original post. "Logical Volume mount/activate error."

Some more relevant errors in XC:

When attempting to create a new SR: "Creating hardware HBA-SR 'Hardware HBA virtual disk storage on 'xenserver': The SR operation cannot be performed because a device underlying the SR is in use by the server"

Also: "The SR has no attached PBDs"

@Danp 7.0

So in my home lab, I've decided to give XenServer a run. I have a Dell R710 with an H700 RAID card in it. I created a RAID 10 volume of 6 TB in the RAID config. I booted from USB and installed XenServer, choosing my new RAID10 volume as storage and selected thin provisioning. It installed successfully.

Upon booting up, at the console (blue screen), there was no management interface listed, even though I statically set one during the install. I rebooted and now I have a management interface and can connect to it via XenCenter.

However, my local SR is boned. Under local storage, I have a red X, and the status is "Broken", and Unplugged. Clicking on it and trying a repair fails and tells me "Logical Volume mount/activate error". Did I miss a step during install or RAID setup?

I'm in! July is perfect.

@JaredBusch said in Grandstream HT503 Gateway:

@fuznutz04 So are you correctly using the FXS port on the unit or the FXO port?

Normally, with other ATA devices, we use the FXS port, as most devices we plug in are expecting to hear a dial tone. (Fax machines, analog phones, etc) However, we are connecting this device (HT503) to a paging system that delivers dial tone. On their old phone system, they would dial a number that would open a connection from their phone system to the Paging system. After a pause, they would hear dial tone which was being delivered from the Paging adapter. I was assuming that I'd need to use the FXO port to get that type of functionality. But again, I could be way off, as this is the first time dealing with this sort of system.

Does anyone have any experience with the Grandstream HT503 "FXO Gateway" devices and interfacing them to an analog paging system? We have a client who has a cloud hosted FreePBX system. Until they get a new paging system, we need to interface with their existing analog paging system. The existing paging system provides dial tone to any device plugged into it. (If I plug in an analog phone, I hear dial tone. Then I can dial some codes to route audio to different zones.) However, when plugging in the HT503 using the FXO/line port, and dialing the extension assigned to that port(80), I receive busy signal. Via the Asterisk console, I can prove that the call is being routed to the HT503. However, no dial tone is heard, and I hear a busy signal. Asterisk says:

Connected line update to SIP/249-00001d15 prevented.
-- Got SIP response 486 "Busy Here" back from xxx.xxx.xxx.xxx:xxxxx
-- SIP/80-00001d17 is busy
== Everyone is busy/congested at this time (1:1/0/0)

I've been using this guide using step 1.

Anyone have any experience with this sort of thing?

Sounds good. I'm going to give this a shot tonight on my ERX at home so I don't bring down the existing tunnel here in the office.