hbr245b
-
Posts
9 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by hbr245b
-
-
Fixed my error!
VM -> Edit Settings -> Options -> Guest Operating System
I had this originally set to "CentOS 4/5/6/7 (64 bit)" [force of habit - we have many vms of this type at work]
Shutdown vm, modified to "Ubuntu Linux (64 bit)", booted and the errors disappeared.
This is booting via plop, first USB device attached is the unraid USB flash drive, second USB device is blank (& unmounted).
-
I boot from plop and was seeing the errors until I attached a second (blank) USB stick to my unraid VM. Note: I am not passing through a USB controller, only assigning USB devices to the VM. After getting a UPS and configuring a VM for it (with USB cable connected) I was able to remove the second USB from my unraid VM and the errors have not returned.
Poor choice of words on my part; a USB controller was added to the vm and then the 2 USB flash drives were attached.
have you tried to mount this stick with unassigned devices? when i tested this with USB UPS, UPS daemon was loaded first to stop error messages..
I've tried with the extra USB device both mounted & umounted. The errors continue in the log file.
I currently have it attached and mounted in a separate vm (to test the scenario above with a UPS attached vaia USB to a separate vm). Errors continue in the log file.
-
I boot from plop and was seeing the errors until I attached a second (blank) USB stick to my unraid VM. Note: I am not passing through a USB controller, only assigning USB devices to the VM. After getting a UPS and configuring a VM for it (with USB cable connected) I was able to remove the second USB from my unraid VM and the errors have not returned.
Poor choice of words on my part; a USB controller was added to the vm and then the 2 USB flash drives were attached.
-
I can confirm also that just simply formatting a spare usb flash drive I had laying around and adding that USB device to my unRAID VM stopped the error messages for me. I will also note that I have the unassigned devices plugin installed and the 2nd flash drives shows up under there (though I don't have it mounted).
I must be missing something as I have two USB devices passed through to my unraid 6.1.3 (booted via plop) running on ESXi 5.5.0.3116895.
The log file is full of errors from both usb drives :-(
Nov 2 18:04:25 unraid kernel: usb 1-2: reset high-speed USB device number 3 using ehci-pci
Nov 2 18:04:26 unraid kernel: sd 4:0:0:0: [sdj] 7975296 512-byte logical blocks: (4.08 GB/3.80 GiB)
Nov 2 18:05:01 unraid kernel: usb 1-1: reset high-speed USB device number 2 using ehci-pci
Nov 2 18:05:01 unraid kernel: sd 3:0:0:0: [sdi] 30529536 512-byte logical blocks: (15.6 GB/14.5 GiB)
-
For 6.1.0, it is identical, except the IRQ is fine and no crashes, controller and drives are fine and stay fine, just as you said. The hpet message is identical in the working and non-working syslogs, so must be harmless, unrelated. I can see no clues at all as to what is different, so that's the limit of my ability to help. I have no explanation.
I have a Dell H310 ready to be converted to IT mode to replace this card. Thanks for looking into the problem nonetheless!
-
unraid as a guest on esxi:
root@unraid-backup:~# lspci -vv -d 1b4b:*
03:00.0 RAID bus controller: Marvell Technology Group Ltd. 88SE9485 SAS/SATA 6Gb/s controller (rev 03)
Subsystem: Marvell Technology Group Ltd. Device 9480
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at fd5c0000 (64-bit, non-prefetchable)
Region 2: Memory at fd580000 (64-bit, non-prefetchable)
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 5GT/s, Width x32, ASPM L0s, Latency L0 <64ns, L1 <1us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 5GT/s, Width x32, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [140 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status: NegoPending- InProgress-
Kernel driver in use: mvsas
Kernel modules: mvsas
I don't have a problem with the speed of parity check; what happens on my system is that one or more disks red-balls during a check.
-
I've removed the docker (I didn't have anything running in the docker) from the config.
I've attached 2 diagnostic files - the filename contains the unraid version 6.1 versus 6.1.1
Both diagnostics contain a hpet1: lost X rtc interrupts
I reconfigured how the pci devices are passed though into the vm (this is an esxi server with unraid as a guest) and the errors related to irq seem to have now disappeared.
6.1.1 boots with no disks present. Same hardware config and 6.1 boots fine.
Any thoughts?
-
Upgraded via the web gui from 6.1 to 6.1.1
All drives missing from the array. Rebooted a few times to see if any change. None.
Downgraded to 6.1 and the drives are present & the array started.
Note: this is a virtualised server (esxi 5.5); drives are connected via SAS2LP controller ( I'm following the thread on this SAS controller & parity check speed ).
[Support] Linuxserver.io - TVHeadend
in Docker Containers
Posted
I'm getting an error with this docker: mpegts: too much queued table input data (over 2MB) - tvheadend becomes unresponsive & I need to stop & start the docker to get it going again.
A google search throws up a number of references on the tvheadend.org website but it's been down for the last 36 hours or so.
Anyone know how to get in touch with tvheadend to let them know there's an issue with their website?