phone guy
-
Posts
398 -
Joined
-
Last visited
-
Days Won
3
Everything posted by phone guy
-
@pocopico@Orphée@Peter Suh I have a couple quick questions about building DVA3221 in Proxmox I am assuming performing the update now and fullupgrade now will update all needed modules and scripts to build this platform <DVA3221> And adding the v9fs ext should work as drivers for the paravirtualized drivers. like it does in my other build of DS3622xs+ So from a fresh start and using tinycore-redpill.v0.4.6.img here is what I tried, but I can not access or find the running DSM. Not with find.synology.com or synology assistant app for windows either. And I do not see anything the console serial 0 port either? Just starting kernel... message. Power on vm. Boot to TCRP. Get ip from ifconfig Putty -> ssh in to tcrp and then I enter these commands to build loader. ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh serialgen DVA3221 ./rploader.sh identifyusb now ./rploader.sh satamap now ./rploader.sh ext denverton-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/v9fs/rpext-index.json This above ext should add whats needed to access using NIC port, again has worked for me not sure its DVA3221 ready? These below are my usual ext added for DS3622 so I #commented them out as this is only a test. Then finally issue the build command ./rploader.sh build denverton-7.1.0-42661 Loader builds, on restart I open serial >_consoe_0 to watch the booting process, switch to usb boot, but I dont see anything? I wait a few minutes, and can never find or see the vm. Maybe I used wrong nic port drivers? or have I missed a step? I saw some information about adding and changing custom_modules.json, but I thought @pocopico fixed all that? and performing the updates and upgrades fixed anything missing. Advice?
-
Glad to hear that, You should post your method and results with any commands for us all so we can duplicate your success!
-
I think you missed ./rploader.sh fullupgrade now Make sure you clean now, update now, fullupgrade now, add ext for your nic, then build.
-
Since I do not run ESXi I am afraid I can not help, I personally am using Proxmox. I know to get the DVA working you will need a graphics card, I am not sure it boots up without a graphics card?
-
I dont think he created the right jun loader. That picture is not the 918, its a 36xx model. Try the correct 918 loader, or switch to redpill. -
Most everybody wants to migrate to newest DSM7.x platforms now
-
First, always make a backup of your data because you never know! be safe and backup data before starting to be safe. You should be able to make new loader for bare metal (GUIDE) Doesn't matter if you use same serial or not. It should not matter. After you successfully make new loader with TCRP for 42661 (DSM7.1) you should see option to migrate disks when you load your dsm page in browser. Just select your migration option and install dsm from .pat downloaded directly from synology web site of whichever platform you build new 7.1 loader for. (DS918 if you choose that platform) and thats it. Good Luck.
-
Excellent. I can't wait to try it!
-
From SSH while tiny core is loaded. tc@box:~$ ls -la /sys/class/scsi_disk total 0 drwxr-xr-x 2 root root 0 May 19 02:12 ./ drwxr-xr-x 61 root root 0 May 19 02:12 ../ lrwxrwxrwx 1 root root 0 May 19 02:12 6:0:0:0 -> ../../devices/pci0000:00/0000:00:02.0/usb10/10-1/10-1:1.0/host6/target6:0:0/6:0:0:0/scsi_disk/6:0:0:0 tc@box:~$ ls -la /sys/block/s* lrwxrwxrwx 1 root root 0 May 19 02:12 /sys/block/sda -> ../devices/pci0000:00/0000:00:02.0/usb10/10-1/10-1:1.0/host6/target6:0:0/6:0:0:0/block/sda lrwxrwxrwx 1 root root 0 May 19 02:12 /sys/block/sr0 -> ../devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sr0 tc@box:~$
-
I am NOT tired of this, I figured you were I am willing to continue as long as you are! Booting back to tcrp, give me a second.
-
Here you go root@DS3622:~# ls -la /sys/class/scsi_disk total 0 drwxr-xr-x 2 root root 0 May 18 20:55 . drwxr-xr-x 60 root root 0 May 18 20:55 .. lrwxrwxrwx 1 root root 0 May 18 20:55 1:0:0:0 -> ../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:0/end_device-1:0/target1:0:0/1:0:0:0/scsi_disk/1:0:0:0 lrwxrwxrwx 1 root root 0 May 18 20:55 1:0:1:0 -> ../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:1/end_device-1:1/target1:0:1/1:0:1:0/scsi_disk/1:0:1:0 lrwxrwxrwx 1 root root 0 May 18 20:55 1:0:2:0 -> ../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:2/end_device-1:2/target1:0:2/1:0:2:0/scsi_disk/1:0:2:0 lrwxrwxrwx 1 root root 0 May 18 20:55 1:0:3:0 -> ../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:3/end_device-1:3/target1:0:3/1:0:3:0/scsi_disk/1:0:3:0 lrwxrwxrwx 1 root root 0 May 18 20:55 1:0:4:0 -> ../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:4/end_device-1:4/target1:0:4/1:0:4:0/scsi_disk/1:0:4:0 lrwxrwxrwx 1 root root 0 May 18 20:55 2:0:0:0 -> ../../devices/pci0000:00/0000:00:02.0/usb4/4-1/4-1:1.0/host2/target2:0:0/2:0:0:0/scsi_disk/2:0:0:0 root@DS3622:~# ls -la /sys/block/s* lrwxrwxrwx 1 root root 0 May 18 20:55 /sys/block/sdb -> ../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:0/end_device-1:0/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 May 18 20:55 /sys/block/sdc -> ../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:1/end_device-1:1/target1:0:1/1:0:1:0/block/sdc lrwxrwxrwx 1 root root 0 May 18 20:55 /sys/block/sdd -> ../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:2/end_device-1:2/target1:0:2/1:0:2:0/block/sdd lrwxrwxrwx 1 root root 0 May 18 20:55 /sys/block/sde -> ../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:3/end_device-1:3/target1:0:3/1:0:3:0/block/sde lrwxrwxrwx 1 root root 0 May 18 20:55 /sys/block/sdf -> ../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:4/end_device-1:4/target1:0:4/1:0:4:0/block/sdf lrwxrwxrwx 1 root root 0 May 18 20:55 /sys/block/synoboot -> ../devices/pci0000:00/0000:00:02.0/usb4/4-1/4-1:1.0/host2/target2:0:0/2:0:0:0/block/synoboot root@DS3622:~# We really need a terminal or shell prompt loadable from dsm to issue commands without ssh
-
Yes unused slot 1, just like all the other pics
-
Ok, so I just rebuild the loader, using ./rploader.sh satamap now defauts, which were 1 and 5 (1 for first sata controller and 5 for second sata controller) which added this to user_config.json "SataPortMap": "15", "DiskIdxMap": "0001" But still HBA drives start at position #2
-
Ok, rebuilding loader again. Just to be thorough, first I run update now and fullupgrade now Then satamap now I left defaults in place, which were 1 for first controller and 5 for next controller tc@box:~$ ./rploader.sh satamap now Machine is VIRTUAL Hypervisor=KVM Found SCSI HBAs, We need to install the SCSI modules Downloading: scsi-5.10.3-tinycore64.tcz Connecting to repo.tinycorelinux.net (89.22.99.37:80) saving to 'scsi-5.10.3-tinycore64.tcz' scsi-5.10.3-tinycore 100% |*******************************************************************************************| 2632k 0:00:00 ETA 'scsi-5.10.3-tinycore64.tcz' saved scsi-5.10.3-tinycore64.tcz: OK Succesfully installed SCSI modules Found "00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)" (1 drive(s) connected) How many ports should be mapped for this controller? [0-9] <1> Found "01:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 01)" (5 drive(s) connected) How many ports should be mapped for this controller? [0-9] <5> SataPortMap=15 DiskIdxMap=0001 Should i update the user_config.json with these values ? [Yy/Nn] y Done. Then added ext for acpi, v9fs and misc. Then ./rploader.sh build broadwellnk-7.1.0-42661 and reboot, select usb verbose from tcrp menu. and here I am back to dsm with disks on hba starting on slot #2.
-
Thats not the VM I am running as my dsm, that was just one I did for the tutorial with everything default to make it less confusing for others. My personal VM, doesnt have any emu hdd as you see above in that picture. Mine looks like this: I will re-build loader. and let rploader satamap set its defaults (which were 1 on sata connection 1 which is the built in sata ports on the motherboard, and 5 on sata connection 2 which is the hba card. as I only have 5 hdds connected at this time (waiting on the PSU power cable 😛 ) I'll post results in a minute
-
@flyride If you want any other information, I will be happy to provide or test at your discretion. Thank you again for taking the time to try and help! I really appreciate it!
-
Like you said, I guess its a proxmox thing? Maybe when you get bored you can try out proxmox and see? I obviously do not know Here are those results root@DS3622:~# lspci -kvd 1b4b:9235 0001:09:00.0 Class 0106: Device 1b4b:9235 (rev 11) (prog-if 01) Flags: fast devsel 0001:0c:00.0 Class 0106: Device 1b4b:9235 (rev 11) (prog-if 01) Flags: fast devsel root@DS3622:~#
-
The only disk that is connected to the motherboard sata ports is the disk proxmox boots from. Is it not part of the vm, but technically disk 1 is the boot disk for that server, loading the proxmox "OS" I even tried remapping the diskidxmap as 0600 so to me, that would mean disks on the hba (the second controller) would start at 00 (sda) but that doesnt work either. Its not a big deal, but since you guys were already digging into the satamap I thought I would ask. I sincerely appreciate the help and the time you have given this. Maybe in the future this will get sorted out.
-
I don't know how to remove that from the VM, I tried editing the .conf for the vm, and even when I comment the virtio scsi out, it get replaced with the default item I guess thats the problem...? I guess I need to see if its possible to completely remove that...? Like I said removing it from the vm.conf should eliminate that controller, but pops back up with something else.
-
Ok, things have changed since I ran the satamap command last @pocopico suggested not running satamap when using hba, so I never did. I never saw these results before, where it tells you how many controllers and asks how to map them. Here are those results (which did not work by the way) tc@box:~$ ./rploader.sh update now Checking Internet Access -> OK Checking if a newer version exists on the repo -> Version is current tc@box:~$ ./rploader.sh satamap now Machine is VIRTUAL Hypervisor=KVM Found SCSI HBAs, We need to install the SCSI modules Downloading: scsi-5.10.3-tinycore64.tcz Connecting to repo.tinycorelinux.net (89.22.99.37:80) saving to 'scsi-5.10.3-tinycore64.tcz' scsi-5.10.3-tinycore 100% |****************************************************************************************************************************| 2632k 0:00:00 ETA 'scsi-5.10.3-tinycore64.tcz' saved scsi-5.10.3-tinycore64.tcz: OK Succesfully installed SCSI modules Found "00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)" (1 drive(s) connected) How many ports should be mapped for this controller? [0-9] <1> 0 Found "01:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 01)" (5 drive(s) connected) How many ports should be mapped for this controller? [0-9] <5> 8 SataPortMap=08 DiskIdxMap=0000 Should i update the user_config.json with these values ? [Yy/Nn] y Done. tc@box:~$ So I told it 0 drives on the first controller, and 8 drives on the hba lsi card which resulted in this being added to user_config.json "SataPortMap": "08", "DiskIdxMap": "0000" So I completed building the loader, launched my console and the vm, and it died in kernel panic, here is the output from the console [ 2.432607] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 [ 2.432607] [ 2.433591] Kernel Offset: disabled [ 2.433591] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 [ 2.433591] The only thing that changed is the satamap (08/0000)
-
This motherboard is a Supermicro X9-SCM-F and has 6 sata ports, 2 sata 6 and 4 sata 3. (LINK TO MOBO) I never added anything to the vm except the hba card as a pass thru pci device, I am not sure if proxmox adds these controllers by default or what? Rebuilding loader will post results in a minute
-
Ok. Here is lspci root@DS3622:~# lspci 0000:00:00.0 Class 0600: Device 8086:29c0 0000:00:01.0 Class 0300: Device 1234:1111 (rev 02) 0000:00:02.0 Class 0c03: Device 1033:0194 (rev 03) 0000:00:1a.0 Class 0c03: Device 8086:2937 (rev 03) 0000:00:1a.1 Class 0c03: Device 8086:2938 (rev 03) 0000:00:1a.2 Class 0c03: Device 8086:2939 (rev 03) 0000:00:1a.7 Class 0c03: Device 8086:293c (rev 03) 0000:00:1b.0 Class 0403: Device 8086:293e (rev 03) 0000:00:1c.0 Class 0604: Device 1b36:000c 0000:00:1c.1 Class 0604: Device 1b36:000c 0000:00:1c.2 Class 0604: Device 1b36:000c 0000:00:1c.3 Class 0604: Device 1b36:000c 0000:00:1d.0 Class 0c03: Device 8086:2934 (rev 03) 0000:00:1d.1 Class 0c03: Device 8086:2935 (rev 03) 0000:00:1d.2 Class 0c03: Device 8086:2936 (rev 03) 0000:00:1d.7 Class 0c03: Device 8086:293a (rev 03) 0000:00:1e.0 Class 0604: Device 8086:244e (rev 92) 0000:00:1f.0 Class 0601: Device 8086:2918 (rev 02) 0000:00:1f.2 Class 0106: Device 8086:2922 (rev 02) 0000:00:1f.3 Class 0c05: Device 8086:2930 (rev 02) 0000:01:00.0 Class 0107: Device 1000:0087 (rev 01) 0000:05:01.0 Class 0604: Device 1b36:0001 0000:05:02.0 Class 0604: Device 1b36:0001 0000:05:03.0 Class 0604: Device 1b36:0001 0000:05:04.0 Class 0604: Device 1b36:0001 0000:06:03.0 Class 00ff: Device 1af4:1002 0000:06:12.0 Class 0200: Device 1af4:1000 0001:09:00.0 Class 0106: Device 1b4b:9235 (rev 11) 0001:0c:00.0 Class 0106: Device 1b4b:9235 (rev 11) root@DS3622:~# I will post the satamap command next
-
Here you go root@DS3622:~# lspci | grep "Class 01.*" 0000:00:1f.2 Class 0106: Device 8086:2922 (rev 02) 0000:01:00.0 Class 0107: Device 1000:0087 (rev 01) 0001:09:00.0 Class 0106: Device 1b4b:9235 (rev 11) 0001:0c:00.0 Class 0106: Device 1b4b:9235 (rev 11) root@DS3622:~#
-
root@DS3622:~# lspci | grep "Class 01.*" 0000:00:1f.2 Class 0106: Device 8086:2922 (rev 02) 0000:01:00.0 Class 0107: Device 1000:0087 (rev 01) 0001:09:00.0 Class 0106: Device 1b4b:9235 (rev 11) 0001:0c:00.0 Class 0106: Device 1b4b:9235 (rev 11) root@DS3622:~#
-
That didnt work, still starting at disk 2 Here are the results of ls -la /sys/block/s* root@DS3622:~# ls -la /sys/block/s* lrwxrwxrwx 1 root root 0 May 18 18:52 /sys/block/sdb -> ../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:0/end_device-1:0/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 May 18 18:52 /sys/block/sdc -> ../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:1/end_device-1:1/target1:0:1/1:0:1:0/block/sdc lrwxrwxrwx 1 root root 0 May 18 18:52 /sys/block/sdd -> ../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:2/end_device-1:2/target1:0:2/1:0:2:0/block/sdd lrwxrwxrwx 1 root root 0 May 18 18:52 /sys/block/sde -> ../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:3/end_device-1:3/target1:0:3/1:0:3:0/block/sde lrwxrwxrwx 1 root root 0 May 18 18:52 /sys/block/sdf -> ../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/port-1:4/end_device-1:4/target1:0:4/1:0:4:0/block/sdf lrwxrwxrwx 1 root root 0 May 18 18:52 /sys/block/synoboot -> ../devices/pci0000:00/0000:00:02.0/usb4/4-1/4-1:1.0/host2/target2:0:0/2:0:0:0/block/synoboot root@DS3622:~# Question, I am rebuilding the loader for each attempt, manually editing user_config.json and rebuilding the loader to test each option. I think I can press E to edit the grub during boot? but it seems to default to booting sata when I hit ctrl x to exit... am I not using the E to edit grub correctly? or is there a way to force it to default to usb verbose boot instead of sata boot?
