kazuni
Member-
Posts
64 -
Joined
-
Last visited
-
Days Won
1
Everything posted by kazuni
-
- Outcome of the installation: SUCCESSFUL - DSM version prior update: None. This is a fresh install on 6.2.1 (23824) - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - QNAP TS-853A, 16GB RAM - Additional comments: All 4 NIC works OOTB - I used a proper set of SN/MAC, don't know if this affects the installation or not.
-
- Outcome of the installation: SUCCESSFUL - DSM version prior update: None.. This is a fresh install on 6.2.1 (23824) - Loader version and model: JUN'S LOADER v1.03a - DS918+ - Using custom extra.lzma: NO - Installation type: VM - VMware ESXi 6.7u1 Oct 16 release on Optiplex 7020 (8 Core/8GB RAM) - Additional comments: Must use E1000E as NIC, VMXNET3 no longer works. Must use 50mb vmdk lead disk as SATA 0:0 Second and above vmdk must sit in SATA0:1~11 (12 disk config) I used a proper set of SN/MAC, don't know if this affects the installation or not.
-
Thank you so much Pigr, this is the only image that works on my ESXi 6.7, much appreciated!
-
Do you see the list of disk before pondering if the disk can be passed through or not? # ls -l /vmfs/devices/disks if they are visisble, all you need to do is make a virtual vmdk linked to the disks using vmkfstools -z
-
- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 - Loader version and model: Jun's loader v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - QNAP TS-853A /w 16GB LPDDR3 - Additional comments: REBOOT REQUIRED, no extra config needed.
-
- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.6-15266 Update 1 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: No - Installation type: QNAP TS-853A 8 Disk /w Internal Apacer Boot Drive (no usb needed) - Additional comments: Updated through Control Panel, reboot required.
-
probably a late reply but nonetheless, yes you can ssh into the server and modify them. I own a TS-853A and it runs with the internal flash (apacer USB emulation disk is built in on the TS-853A, with 512MB space, perfect to be used as Jun's DSM loader) msg me if you need any further info
-
I'm running mine on a TS-853A with DSM 6.1, works flawlessly
-
lspci -k 0000:00:00.0 Class 0600: Device 8086:2280 (rev 35) Subsystem: Device 8086:7270 0000:00:02.0 Class 0300: Device 8086:22b1 (rev 35) Subsystem: Device 8086:7270 0000:00:10.0 Class 0805: Device 8086:2294 (rev 35) Subsystem: Device 8086:7270 0000:00:13.0 Class 0106: Device 8086:22a3 (rev 35) Subsystem: Device 8086:7270 Kernel driver in use: ahci 0000:00:14.0 Class 0c03: Device 8086:22b5 (rev 35) Subsystem: Device 8086:7270 Kernel driver in use: xhci_hcd 0000:00:1a.0 Class 1080: Device 8086:2298 (rev 35) Subsystem: Device 8086:7270 0000:00:1b.0 Class 0403: Device 8086:2284 (rev 35) Subsystem: Device 8086:7270 0000:00:1c.0 Class 0604: Device 8086:22c8 (rev 35) Kernel driver in use: pcieport 0000:00:1c.1 Class 0604: Device 8086:22ca (rev 35) Kernel driver in use: pcieport 0000:00:1c.2 Class 0604: Device 8086:22cc (rev 35) Kernel driver in use: pcieport 0000:00:1c.3 Class 0604: Device 8086:22ce (rev 35) Kernel driver in use: pcieport 0000:00:1f.0 Class 0601: Device 8086:229c (rev 35) Subsystem: Device 8086:7270 0000:00:1f.3 Class 0c05: Device 8086:2292 (rev 35) Subsystem: Device 8086:7270 0000:01:00.0 Class 0106: Device 1b4b:9215 (rev 11) Subsystem: Device 1b4b:9215 Kernel driver in use: ahci 0000:02:00.0 Class 0106: Device 1b4b:9215 (rev 11) Subsystem: Device 1b4b:9215 Kernel driver in use: ahci 0000:03:00.0 Class 0604: Device 1b21:1184 Kernel driver in use: pcieport 0000:04:01.0 Class 0604: Device 1b21:1184 Kernel driver in use: pcieport 0000:04:03.0 Class 0604: Device 1b21:1184 Kernel driver in use: pcieport 0000:04:05.0 Class 0604: Device 1b21:1184 Kernel driver in use: pcieport 0000:04:07.0 Class 0604: Device 1b21:1184 Kernel driver in use: pcieport 0000:05:00.0 Class 0200: Device 8086:1533 (rev 03) Kernel driver in use: igb 0000:06:00.0 Class 0200: Device 8086:1533 (rev 03) Kernel driver in use: igb 0000:07:00.0 Class 0106: Device 1b4b:9215 (rev 11) Subsystem: Device 1b4b:9215 Kernel driver in use: ahci 0000:09:00.0 Class 0604: Device 1b21:1184 Kernel driver in use: pcieport 0000:0a:01.0 Class 0604: Device 1b21:1184 Kernel driver in use: pcieport 0000:0a:03.0 Class 0604: Device 1b21:1184 Kernel driver in use: pcieport 0000:0a:05.0 Class 0604: Device 1b21:1184 Kernel driver in use: pcieport 0000:0a:07.0 Class 0604: Device 1b21:1184 Kernel driver in use: pcieport 0000:0b:00.0 Class 0200: Device 8086:1533 (rev 03) Kernel driver in use: igb 0000:0c:00.0 Class 0200: Device 8086:1533 (rev 03) Kernel driver in use: igb 0000:0d:00.0 Class 0106: Device 1b4b:9215 (rev 11) Subsystem: Device 1b4b:9215 Kernel driver in use: ahci 0001:00:02.0 Class 0000: Device 8086:6f04 (rev ff) 0001:00:02.2 Class 0000: Device 8086:6f06 (rev ff) 0001:00:03.0 Class 0000: Device 8086:6f08 (rev ff) 0001:00:03.2 Class 0000: Device 8086:6f0a (rev ff) 0001:00:1f.0 Class 0000: Device 8086:8c54 (rev ff) 0001:00:1f.3 Class 0000: Device 8086:8c22 (rev ff) 0001:06:00.0 Class 0000: Device 1b4b:1475 (rev ff) 0001:08:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:09:00.0 Class 0000: Device 8086:1533 (rev ff) 0001:0c:00.0 Class 0000: Device 8086:1533 (rev ff) 0001:0d:00.0 Class 0000: Device 8086:1533 (rev ff) Hide Here's the lspci -k; no idea how to interpret this list... In my motherboard it has a very limited set of parameters that can control the I/O ports (in fact there are none), so I don't think there are anything that I can do with fiddling the BIOS at the moment...
- 3 replies
-
- sata
- juns loader
-
(and 2 more)
Tagged with:
-
I got the Qnap TS-853A running with Jun's loader, everything runs flawlessly, including all 4 LAN ports, USB, except HDMI (no framebuffer just like all other machines with jun's loader) and karaoke board. I have a weird configuration issue - as you can see in my attached image, all my Disks are accounted for (8) but they are slotted in a weird spacing manner (although they are in sequence). Before editing /etc.defaults/synoinfo.conf, the last disk (disk #8 physically, in the diagram it's the last disk) was not shown up in Storage Manager. I managed to edit the file and edited three lines: internalportcfg="0xfff" usbportcfg="0x300000" esataportcfg="0xff000" and now all my disk are recognized, just in a weird manner as below. Any idea what caused the spacing of disks?
- 3 replies
-
- sata
- juns loader
-
(and 2 more)
Tagged with: