maxhartung
-
Posts
39 -
Joined
-
Last visited
Posts posted by maxhartung
-
-
12 minutes ago, blindspot said:
apollolake-DS918
bromolow-DS3615
broadwell-DS3617
broadwellnk-DS3622Tried with broadwellnk-DS3622 same issue. Another ideea ? I will try with broadwell.
-
3 minutes ago, Dvalin21 said:
What version of the img do you have? It's on 45 and above
Sent from my HD1925 using Tapatalk
Then I should have it. I will try a build. I have the latest from git. I just build bromolow but with serialgen 3622xs, right ?
-
2 minutes ago, Dvalin21 said:
I can't remember, have you tried 3622? My build wouldn't work until I switched to it. And even then it was the default that worked first
Sent from my HD1925 using Tapatalk
Nope, how can I add support for it ?
-
7 hours ago, blackmix said:
My bad, it was STI is 1442 - i3 2nd geration
DS3615xs build.
Install with 1 hard drive and after Install change satamap to 6 drivers in grupo.cfg.
Still not working on my side with one SSD installed.
On 3/19/2022 at 6:54 PM, Dvalin21 said:Have you tried the default, 58 0A00
Yes, tried. Nothing is working. Everything was working with Juno's bootloader
-
2 hours ago, blackmix said:
Finally got some work success;.
I managed to install dsm7 on an hp notebook with 2 hds, when installing it gives an error because there are 6 sata ports on the motherboard controller of this notebook.. but physical there are only 1 and another is a cdrom to sata adapter.. The solution was to install only with SataPortMap=1 and DiskIdxMap=0 after installing everything i changed grub.cfg SataPortMap=6 and DiskIdxMap=00 and now all 2 hds appear successfully and maybe more if I add more adapters.
thanks.
What HP notebook do you have ? I also tried with your options but no go
-
2 minutes ago, xennix said:
have you ever try with hdd. sometimes you have to set bios for ssd.
The only option that I have is RAID or AHCI
-
I have the problem with:
It's an HP Elitebook 840 G2 with 2 SSDs.
We've detected errors on the hard drives (1, 3), and the SATA ports have also been disabled. Please shut down your DS918+ to replace or remove the hard drives and try again. I tried the suggested DiskIdxMap=0000 and SataMap=0004 or something like that but didn't work.
I tried many configs but nothing works
Tried: DiskIdxMap=00 SataPortMap=4 -> We have detected errors on the hard drives 1,3,4
Tried: DiskIdxMap=00 SataPortMap=3 -> We have detected errors on the hard drives 1,3
Tried: DiskIdxMap=00 SataPortMap=2 -> We have detected errors on the hard drives 1
Tried: DiskIdxMap=00 SataPortMap=1 -> No drives detected
Tried: DiskIdxMap=00 SataPortMap=0 -> not loading/no network
Tried: DiskIdxMap=00 SataPortMap=1 SasIdxMap=0 -> No drives detected
Tried: DiskIdxMap=00 SataPortMap=2 SasIdxMap=0 -> We have detected errors on the hard drives 1
Tried: DiskIdxMap=01 SataPortMap=1 -> No drives detected
Tried: DiskIdxMap=01 SataPortMap=2 -> We have detected errors on the hard drives 2
DiskStation> fdisk -l
Disk /dev/sdb: 466 GB, 500107862016 bytes, 976773168 sectors
60801 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytesDevice Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/sdb1 0,0,1 1023,254,63 1 976773167 976773167 465G ee EFI GPTDisk /dev/sdd: 224 GB, 240057409536 bytes, 468862128 sectors
29185 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytesDevice Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/sdd1 0,0,2 1023,254,63 1 468862094 468862094 223G ee EFI GPTDisk /dev/synoboot: 14 GB, 15518924800 bytes, 30310400 sectors
14800 cylinders, 64 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytesDevice Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/synoboot1 * 0,32,33 6,62,56 2048 100351 98304 48.0M 83 Linux
/dev/synoboot2 6,62,57 15,205,62 100352 253951 153600 75.0M 83 Linux
/dev/synoboot3 15,205,63 130,138,8 253952 2097151 1843200 900M 83 Linux -
There is any fix for "We have detected issues on hard drives 1,3"? I tried every combination of SataPortMap and DiskIdxMap
-
-
1 minute ago, haydibe said:
Hmm, that's odd. Can share the output of `docker image ls`?
Let me check my history, not that I skipped testing it again.. everything is possible before the first coffe 😊
After another restart is working correctly.
-
1 minute ago, shibby said:
build containter first
I did it already but error with the above
./redpill_tool_chain.sh auto apollolake-7.0-41890
-
6 minutes ago, haydibe said:
you didn't do this, did you?
So I tried reinstalling Docker, removing all references from the system, reinstalling, restart the Mac.
docker builder prune --all --filter label=redpill-tool-chain
WARNING! This will remove all build cache. Are you sure you want to continue? [y/N] y
Total reclaimed space: 0B
docker image ls --filter label=redpill-tool-chain --quiet | xargs docker image rm
MacBook-Pro redpill %
-
9 minutes ago, haydibe said:
Seems I missed to test the bromolow-7.0.1 image... So this is the one that caused this mystery behavior.
I disabled the build cache now by default - it can be turned on again in global_settings.json.
Now "clean all" deletes all images, including the last build one.
changes in v0.7.3 :
- fixed usage of label that determins the redpill-tool-chain images for clean up
- add `"docker.use_build_cache": "false"` to global_settings.json
- add `"docker.clean_images": "all"` to global_settings.json (set to orphaned to cleanup everything except the latest build)
See README.md for usage.
When I introduced labels, I must have made a last adjustment to the Dockerfile, which actual resulted in all images beeing created using the correct key, but with the wrong value (=all identical) .
Please clean up your build cache and images to benefit from the fix:
docker builder prune --all --filter label=redpill-tool-chain docker image ls --filter label=redpill-tool-chain --quiet | xargs docker image rmSame issue with this build too. Should I try to reinstall Docker ? I am running on Mac
./redpill_tool_chain.sh auto apollolake-7.0-41890
Unable to find image 'redpill-tool-chain:apollolake-7.0-41890' locally
docker: Error response from daemon: pull access denied for redpill-tool-chain, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
-
39 minutes ago, haydibe said:
Is docker.local_rp_load_use set to true in your global_settings.json?
If so:
No, I don't have it enabled. I tried a clean build with everything deleted but the same issue.
-
Anyone has this error ?
./redpill_tool_chain.sh auto apollolake-7.0-41890
Unable to find image 'redpill-tool-chain:apollolake-7.0-41890' locally
docker: Error response from daemon: pull access denied for redpill-tool-chain, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'
I really can't figure out what's wrong with it.
-
22 minutes ago, Franks4fingers said:
I am looking to given Proxmox a run out and jump from baremetal to virtual. This will be my first foray into running Xpenology on virtual.
Does anyone have any links to good tutorials that can be followed on the best options to use for configuring things from the outset?
For the most part you need to set the VID and PID to these values and make the loader (don’t forget about the MAC Address too):
VID: 0x46f4PID: 0x0001
Then you need to create a new VM with SATA based hdd and machine type set to Q35You also need to edit the config of the virtual machine and add this line with also replacing the path to the file:
args: -device 'qemu-xhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/XXX/redpill-DS918+_7.0-41890.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot,bootindex=5'
or you can just use sata boot
-
1
-
-
38 minutes ago, coint_cho said:
Tried booting with a VID/PID/MAC from my baremetal machine, using a R8169 built in gigabit NIC, doesn't grab a new IP from DHCP and currently is not working, running 6.1.7 with 1.02b Jun's loader modded with support for MBR storage. VMWare doesn't work as well unfortunately, it just doesn't want to go pass 56% of installing PAT file.
Di you tried with SATA boot ?
-
Yes, I have network access that’s why I can see the error: We have detected errors on hdd 1,3
-
Quote
Do you have a serial console by any chance? If so can you post the full dmesg output?
No, the laptop doesn't have serial console (HP Elitebook 840 G2). I will try to find a way to attach a serial console in some way. Thank you.
-
24 minutes ago, haydibe said:
Mine looks like this:
I crossed out some details with X, but that's the config that works for me without any issues.
So I tried to compare the config via diff tool but nothing syntax related seen, I copied your config, replaced the lines, changed the information and now works.
For mapping there is something to be done ? My drive starts at 7
-
6 minutes ago, haydibe said:
I am not sure if it's because of the path you choose or because of the absence of the usb0 device. Appart of having my bootloader image in /var/lib/vz/images/${MACHINEID}/${IMAGENAME} the args line looks identicaly.
Works like a charme on pve 7.0.1
I tried mkdir folder called 100 (machine id), put the img there and see if it works but same error.
-
My Proxmox install seem broken for some reason:
I uploaded the img file to via web browser (local home -> ISO Images)
/var/lib/vz/template/iso/image.img
But when I try to start the VM:
kvm:  -device qemu-xhci,addr=0x18 -drive id=synoboot,file=/var/lib/vz/template/iso/image.img,if=none,format=raw -device usb-storage,id=synoboot,drive=synoboot,bootindex=5:
Could not open ' -device qemu-xhci,addr=0x18 -drive id=synoboot,file=/var/lib/vz/template/iso/image.img,if=none,format=raw -device usb-storage,id=synoboot,drive=synoboot,bootindex=5': No such file or directory
I checked the file via shell and it's there.
This is the args in the conf:
args: -device 'qemu-xhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/template/iso/image.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot,bootindex=5'
root@home:~# ls /var/lib/vz/template/iso/
image.img
root@home:~#Config:
args: -device 'qemu-xhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/template/iso/image.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot,bootindex=5'
balloon: 0
boot: order=sata0;net0
cores: 2
machine: q35
memory: 4096
name: DSM
net0: virtio=F2:9D:7D:2E:7E:61,bridge=vmbr0
numa: 0
ostype: l26
sata0: local-lvm:vm-100-disk-0,size=120G
scsihw: virtio-scsi-pci
smbios1: uuid=27d90b08-fa4c-4b43-85fc-f40200747f72
sockets: 1
vmgenid: 6e85c112-295e-4432-b661-7f91af624a80 -
Further findings in my case of "We have detected errors on HDD" with HP EliteBook 840 G2:
On Juno's bootloader 6.2.1 in DSM the disks are listed as Disk 2 and Disk 4. Both of them are detected without an issue and everything works except in redpill.
-
In order to work on ESXI what changes are required ?
TinyCore RedPill Loader (TCRP)
in Loaders
Posted · Edited by maxhartung
"SataPortMap": "1",
"DiskIdxMap": "02"
SynologyNAS> fdisk -l
Disk /dev/synoboot: 14 GB, 15518924800 bytes, 30310400 sectors
14800 cylinders, 64 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/synoboot1 * 0,32,33 6,62,56 2048 100351 98304 48.0M 83 Linux
/dev/synoboot2 6,62,57 15,205,62 100352 253951 153600 75.0M 83 Linux
/dev/synoboot3 15,205,63 130,138,8 253952 2097151 1843200 900M 83 Linux
DiskIdxMap 00
SataPortMap 2
With the default values detected, it detects like sdb and sdd. I plugged in only one drive:
SynologyNAS> fdisk -l
Disk /dev/sdb: 466 GB, 500107862016 bytes, 976773168 sectors
60563 cylinders, 256 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/sdb1 0,0,2 1023,255,63 1 976773167 976773167 465G ee EFI GPT
Disk /dev/synoboot: 14 GB, 15518924800 bytes, 30310400 sectors
14800 cylinders, 64 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/synoboot1 * 0,32,33 6,62,56 2048 100351 98304 48.0M 83 Linux
/dev/synoboot2 6,62,57 15,205,62 100352 253951 153600 75.0M 83 Linux
/dev/synoboot3 15,205,63 130,138,8 253952 2097151 1843200 900M 83 Linux