Jump to content
XPEnology Community

g4sho

Member
 View Profile  See their activity

  • Posts

    60

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Posts posted by g4sho

    Develop and refine the FS6400 loader

    in Developer Discussion Room

    Posted

    On 11/25/2022 at 10:39 AM, -iliya- said:

    Hi, have a any news about FS6400?

    I'm thinking of making this model

    Supermicro X11DPL-I

    2x Xeon Silver 4110

    128Gb

    2x LSI 9300-16i

     

    I am in the same boat was hoping to see this loader, but the real programmers explained to me the difficulties of this endeavor. I am using the RS4021xs with my Supermicro server system.

    DVA3221 loader development thread

    in Developer Discussion Room

    Posted

    9 hours ago, Orphée said:

    You will never have any display from DVA3221, this is not meant for it.

    If you think the Synology is a direct surveillance display you are wrong.

    Look at original DVA3221, there is no any port available on it to plug a monitor.

     

    On my proxmox, once the GPU is passed through the Synology VM, the screen goes black.

     

    You can forget any kind of "TV" or anything like this with DVA3221.

     

    You will need something like an Android tv with DS CAM installed on it to access Surveillance station from LAN.

    I don't know if this is normal. but on my barebone dva3221 setup, I do get video out of my hdmi jack on my gtx1650. Its just the boot screen for automated redpill

    DVA3221 loader development thread

    in Developer Discussion Room

    Posted

    4 hours ago, Orphée said:

    You should have a look in /var/log/ folder to read some logs like messages or synoscgi.log to see if any error occurs (license check or anything else)
     

    After looking at logs again, I decided to uninstall surveillance station, and advanced codecs. I then only reinstalled surveillance station, added one camera and one task, and it now works.

    • Like 1

    DVA3221 loader development thread

    in Developer Discussion Room

    Posted · Edited by g4sho

    1 hour ago, Orphée said:

    You should have a look in /var/log/ folder to read some logs like messages or synoscgi.log to see if any error occurs (license check or anything else)
     

    Hi @Orphée I did actually, and there were several errors some pertaining to decoders, and so I cleared them out and will reboot and look at them again. Nothing jumped out at me tho.

     

    DVA3221 loader development thread

    in Developer Discussion Room

    Posted · Edited by g4sho

    Hello all, I have successfully installed DVA3221 on a asrock c2750di4 motherboard with avoton 8 core embedded processor(barebone). I have 32 gigs of memory, and 4 hard drives. Including 2 4tb hard drives, a single 8tb Seagate Skyhawk AI, and a 1tb ssd. I also have installed a Zotac GTX 1650 GPU. My problem is that when I set up a task like counting cars, it does not trigger in the DVA software when a car etc. passes thru. I have tried several task and none working. But my GPU does show up in the info page, and drivers are loaded during boot. @pocopicoor anyone else, a push in the right direction would be appreciated. I am using the automatic redpill loader-beta2

    Nvidia.png

    Issue installing DSM 6.2.3

    in General Installation Questions/Discussions (non-hardware specific)

    Posted

    1 hour ago, rojoone2 said:

    Its the same error as with DSM 7 when installing the pat file for DS3617xs and you are still connected to the internet.

    Synology has been  pushing the latest updates while you are installing the original pat file. Try disconnecting from the internet when you install on a 3617.

    @rojoone2Theres nothing really on the forum topics that i could find about this, except this was one of the symptoms of a failed upgrade to newer DSM pat files. The pat file I used was one that I already had 6.2.3.25379. This error happened on a migration as well as a fresh install. And I have never had to disconnect from the internet before to install. I will try it tho.

    Develop and refine the FS6400 loader

    in Developer Discussion Room

    Posted

    17 hours ago, pocopico said:

     

    @g4sho @yanjun FS6400 is from what dts suggests, all SAS. And it makes absolutely sense. It depends on two internal SAS HBAs which are defined in the DTS file. It splits the local enclosure in two parts. The first one connected to 12 disks and the second to another 12 disks. All disks are defined by its port number on the specific HBA.

     

    You have to understand that FS6400 is an enterprise model and it will of course have tighter hardware restrictions in order to operate properly. As you can see from the DTS file, it even depends on specific HBA firmware. There might have also harder to brake interdependencies and even more counter measures as already @yanjun have found. 

     

     

     

     

     

    @yanjun@pocopicoNow that makes sense to me. Thanks you guys for replying, I did not realize the technical difficulties involved. So basically the sas controllers are hardcoded into DSM. And probably specific firmware, ouch! Yanjun, if this has stumped you guys, I don't have a chance at deciphering this, as I am nowhere close to you guys skill levels. But I will look at it anyway just to see what it is, thanks for the post. Again, thank you guys for all you do for the community.

    • Like 2

    Develop and refine the FS6400 loader

    in Developer Discussion Room

    Posted

    @yanjun@jumkey@pocopico@flyride I guess that is a NO since i have not received any reply from you guys. Is there some kind of unwritten rule on what can be developed for and what can't. Since I started using xpenology,(2015), there has never been a loader made for any of the higher end model numbers. That s a shame, because some of us have the hardware and do other things than just video conversion,plex, etc, with our boxes. Oh well, good work done by all regardless. So thanks anyway.

    Develop and refine the FS6400 loader

    in Developer Discussion Room

    Posted · Edited by g4sho
    clarrification

    @flyrideI have three servers to choose from. My newest is a self built Norco 24 case, supermicro x12spa-tf motherboard,Xeon 3rd gen silver processor, is has 240 gb ram, 4 nvme in vroc config on motherboard, with 12ssds, and 12 spinning disk, and 1 optane 905p, using with primo cache, as cache drive. I also have a HP Dl380 gen 9, dual processor e5-2670v3, 64 gig ram, 12-6tb sas 3 spinning drives, with 9305 16i LSI hba card.(This currently runs DSM 6.2.3) in a raid 10 configuration). Has been rock solid. And I also have a 24 bay supermicro server with dual processor x9 motherboard, with 192gb ram, 24-3tb Sas drives, currently running proxmox 7.2 with 2 tinycore redpill 3622xs vms instances, and a couple of server 2022 vms also. The first server mentioned uses some of the same hardware as the FS6400. I believe that with the hardware I have, I can achieve better performance with the software for the higher end synology boxes. Things like RDMA(SMB3+), which synology provides in their higher end hardware, that they dont provide in the lower end stuff like the 3622xs,etc. I have both 40Gbe and 10Gbe connectivity to these boxes. And yes all this is part of my home lab.

     

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    1 hour ago, Peter Suh said:

     

    Here's the log.

     

      dmesg |grep -i smart (Hide contents)

    admin2@r8152_test:/$ dmesg |grep -i smart
    [    4.365145] <redpill/smart_shim.c:1032> Registering SMART emulator shim
    [    4.365146] <redpill/smart_shim.c:1042> SCSI driver exists - installing canary
    [    4.367584] <redpill/smart_shim.c:1054> Successfully registered SMART emulator shim
    [   12.451076] scsi 4:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
    [   12.588402] scsi 4:0:1:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
    [   21.756675] <redpill/smart_shim.c:934> sd_ioctl_canary triggered for first ioctl()
    [   21.764255] <redpill/smart_shim.c:862> Rerouting sd_fops->ioctl<ffffffff81661b98>=sd_ioctl+0x0/0x230<ffffffff8140dad0> to sd_ioctl_smart_shim+0x0/0x90 [redpill]<ffffffffa000a4d0>
    [   21.873361] <redpill/smart_shim.c:971> Canary finished - routing to sd_fops->ioctl = sd_ioctl_smart_shim+0x0/0x90 [redpill]<ffffffffa000a4d0>
    [   34.540822] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.540823] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.562929] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.562931] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.594586] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.594587] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.594903] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.594904] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.599583] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.599584] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.602196] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.602197] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.602456] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.602456] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.603580] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.603581] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.609885] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.609886] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.613092] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.613093] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.620171] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.620172] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.620508] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.620509] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.626380] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   34.666906] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.666907] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.677084] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   34.677330] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   34.678738] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   34.685789] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   34.691587] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   34.715505] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   34.715506] <redpill/smart_shim.c:390> Generating fake SMART values
    [   34.715512] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd1
    [   34.715512] <redpill/smart_shim.c:457> Generating fake SMART thresholds
    [   34.716658] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.716659] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.716664] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   34.716664] <redpill/smart_shim.c:390> Generating fake SMART values
    [   34.717026] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   34.717538] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd5
    [   34.717539] <redpill/smart_shim.c:516> Generating fake WIN_SMART log=0 entries
    [   34.717607] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   34.717608] <redpill/smart_shim.c:390> Generating fake SMART values
    [   34.719204] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.719205] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.720550] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.720551] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.721315] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.721316] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.727112] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.727113] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.728103] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.728104] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.768695] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.768696] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.933975] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.933975] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.950733] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.950734] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.964781] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   34.964782] <redpill/smart_shim.c:390> Generating fake SMART values
    [   34.964785] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd1
    [   34.964786] <redpill/smart_shim.c:457> Generating fake SMART thresholds
    [   34.964865] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.964866] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.964869] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   34.964870] <redpill/smart_shim.c:390> Generating fake SMART values
    [   34.965417] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd5
    [   34.965418] <redpill/smart_shim.c:516> Generating fake WIN_SMART log=0 entries
    [   34.965493] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   34.965493] <redpill/smart_shim.c:390> Generating fake SMART values
    [   34.966146] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.966147] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.966815] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.966815] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.967244] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.967245] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   34.969436] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   34.969437] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   35.944932] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   35.944933] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   35.944937] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   35.944937] <redpill/smart_shim.c:390> Generating fake SMART values
    [   35.949234] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   35.949235] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   35.949580] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   35.959817] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   35.960974] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   35.961736] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   35.964513] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   35.965738] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   35.972218] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   36.004322] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   36.024034] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   36.024035] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   36.029552] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   36.032350] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   36.055586] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   36.055588] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   36.077485] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   36.077485] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   36.077488] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   36.077489] <redpill/smart_shim.c:390> Generating fake SMART values
    [   36.078101] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   36.078102] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   38.529577] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   39.945803] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   39.951035] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   39.965727] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   39.975223] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   39.987417] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.038566] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   40.050731] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.051445] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   40.095687] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   40.098456] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   40.098458] <redpill/smart_shim.c:390> Generating fake SMART values
    [   40.098463] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd1
    [   40.098464] <redpill/smart_shim.c:457> Generating fake SMART thresholds
    [   40.098697] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   40.098698] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.098701] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   40.098702] <redpill/smart_shim.c:390> Generating fake SMART values
    [   40.099456] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd5
    [   40.099457] <redpill/smart_shim.c:516> Generating fake WIN_SMART log=0 entries
    [   40.099523] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   40.099523] <redpill/smart_shim.c:390> Generating fake SMART values
    [   40.100082] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   40.100083] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.100873] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   40.100874] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.101397] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   40.101398] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.116373] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   40.116375] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.123760] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   40.123760] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.141402] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   40.141404] <redpill/smart_shim.c:390> Generating fake SMART values
    [   40.141409] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd1
    [   40.141410] <redpill/smart_shim.c:457> Generating fake SMART thresholds
    [   40.141667] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   40.141667] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.141671] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   40.141672] <redpill/smart_shim.c:390> Generating fake SMART values
    [   40.141856] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   40.141857] <redpill/smart_shim.c:390> Generating fake SMART values
    [   40.141862] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd1
    [   40.141863] <redpill/smart_shim.c:457> Generating fake SMART thresholds
    [   40.142510] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   40.142511] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.142514] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   40.142514] <redpill/smart_shim.c:390> Generating fake SMART values
    [   40.142569] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd5
    [   40.142570] <redpill/smart_shim.c:516> Generating fake WIN_SMART log=0 entries
    [   40.142654] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   40.142654] <redpill/smart_shim.c:390> Generating fake SMART values
    [   40.143297] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   40.143298] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.143338] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   40.143339] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.144111] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   40.144112] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.144679] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   40.144680] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.168706] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   40.168707] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.187572] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   40.187573] <redpill/smart_shim.c:390> Generating fake SMART values
    [   40.187578] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd1
    [   40.187578] <redpill/smart_shim.c:457> Generating fake SMART thresholds
    [   40.187665] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   40.187666] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.187669] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd0
    [   40.187669] <redpill/smart_shim.c:390> Generating fake SMART values
    [   40.189500] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   40.189501] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   40.629066] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   40.637794] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   40.646533] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   41.652537] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   41.652988] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   41.652989] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   41.654219] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   41.654220] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   41.654845] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd8
    [   41.654846] <redpill/smart_shim.c:656> Attempted ATA_SMART_ENABLE modification!
    [   41.655810] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   41.655811] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   41.682033] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   41.682033] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   41.682149] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   41.682149] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   41.695720] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   41.695721] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   41.697007] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   41.697007] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   41.698173] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   41.698173] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   41.698365] <redpill/smart_shim.c:646> Got SMART *command* - looking for feature=0xd8
    [   41.698365] <redpill/smart_shim.c:656> Attempted ATA_SMART_ENABLE modification!
    [   41.699104] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   41.699105] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   41.757124] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   41.757125] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   41.757231] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   41.757232] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   41.772230] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   41.774577] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   41.775507] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   41.780484] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   41.791522] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   41.967378] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   44.987830] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   45.000009] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   45.051672] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   45.062228] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   45.062461] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   45.062462] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   45.090988] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   45.098446] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   45.110617] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   45.173774] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   45.182409] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   45.194615] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   45.256009] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   45.268189] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   45.277395] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   45.525752] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   45.533751] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   45.545927] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   45.559446] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   45.571615] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   46.522590] <redpill/smart_shim.c:354> ATA_CMD_ID_ATA confirmed SMART support - noop
    [   46.532089] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   46.544265] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY
    [   46.551688] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something
    [   46.563872] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY

     

    I was wondering if this was normal or just a bug, as my virtual machine instance of Redpill does the same thing. If I am monitoring the console, these messages are continuiously spit out on screen. Is there a fix?

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    3 hours ago, Peter Suh said:

     

    Set user_config.json as below

     

    maxdisks = 36
    internalportcfg = 0xfffffffff

    Hi just wanted to say that I have always had problems with xpenology with the max disk settings over 24-26 disk. I have never been able to figure out why? There would be random crashes of the disk array, some times would loose connection, and a list of other weird things. This goes all the way back to DSM 6.0, your mileage may vary tho. Just wanted others to be aware of my experiences with high drive count.

     

    • Like 1

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    20 minutes ago, Peter Suh said:

     

    If the redpill-load directory is still in the TC,
    Under ./redpill-load/c*/e*, you will see three or more directories as follows:
    pocopico.e1000e
    pocopico.igb
    pocopico.ixgbe

    If you don't have a redpill-load in advance,
    ./rploader.sh build broadwellnk-7.0.1-42218

    build first to obtain the redpill-load directory.

    Among them, the pocopico.ixgbe is deleted by force with the sudo rm -rf command

    Perform the

    ./rploader.sh build broadwellnk-7.0.1-42218 manual

    to rebuild the loader without pocopico.ixgbe.

    DS3622xxs+ already contains vanilla ixgbe ext, so I understand that it should not be added again.
    Since I don't actually have the above NIC, I haven't tested it myself and only know it in theory.

    Thanks alot Peter!

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted · Edited by g4sho

    18 minutes ago, Peter Suh said:

     

    Shouldn't you avoid duplication of dca.ko on the two NICs?
    I think a few weeks ago, in a post, we saw that to avoid this, we should use vanilla, which is included by default in DS3622xs+
    Shouldn't we build a manual so that igbxe is not automatically included when the DS3622xs+ loader is built?

    Can you explain what I need to do? For clarification. I am using two(indentical) redpill vm's on one proxmox server. I am passing thru one port each of a two port(10Gbe) nic to each vm. I am checking the 1st vm now that does not exhibit this problem, to see if the custom.config.json, is some how different.

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted · Edited by g4sho
    Clarification

    4 hours ago, pocopico said:

     

    The overlapping dependencies issue has been fixed on my redpill-load repo. Are you using the develop branch of the pocopico repo in your custom_config.json ? 

     

    4 hours ago, pocopico said:

     

    The overlapping dependencies issue has been fixed on my redpill-load repo. Are you using the develop branch of the pocopico repo in your custom_config.json ? 

    I will look but I have changed nothing in the boot loader., I am using the defaults that come with the latest tinycore build download. It looks like it is the developement branch if what I think I see is correct. But like I said this is what came default with the download as of yesterday. So do I need to edit this to say master branch?

    customconfigjson.txt

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted · Edited by g4sho
    Clarification

    3 hours ago, g4sho said:

    Here are the results of both commands.

    resultsofCatCommands.txt 1.11 kB · 2 downloads

    @pocopico It looks like your ixgbe driver was causing the issue, because it could not load dca.ko and exited with code 99. I deliberately left off 10gbe port from vm config to see if this was the cause and machine came up ready after loading. i will investigate more because this same driver is being used in a duplicate vm on same hardware, i can only think that i must have somehow not config 10gbe port in vm till after initial install was complete, I will try that now to see if that works. Thanks for pointing me in the right direction.

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted · Edited by g4sho
    added attachment

    4 hours ago, pocopico said:

     

    While on DSM with ssh :

     

    cd /dev/

    mount synoboot1 /mnt

    vi /mnt/boot/grub/grub.cfg

    umount /mnt

     

     

    Thanks alot Pocopico, got it installed on proxmox. But here is the next problem, which is weird to me. i am trying to install second instance of 3622xs to a duplicate vm in proxmox(same drivers, etc for both), but on the 2nd installation, I am in a never ending boot loop. I bootup, start the install, install finishes without error, it reboots back up and can be seen on the network, but status is not installed. Looking at the console over serial port, I don't see any error messages that are apparent that would give a clue to what is happening with the second install, as i duplicated the actions of my first install which was sucessful. Any thoughts?  Here is attachment showing boot sequence.

    bootupLoopSequence.txt.txt

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted · Edited by g4sho
    Clarification

    Hi all, I am in the process of installing DSM3622xs+(7.0.1-42218) on my proxmox server. And the problem i am having is with getting satamap, diskidx, etc. set correctly for my server. I usually can turn off sata in bios, when setting up bare metal, and my 12 disk will align correctly.(this is actually a 24port card, Adaptec-72405) In this case I cannot as I am using sata ssd to boot proxmox. I know how to edit the user config json when in tiny core loader mode. I also know how to directly change internal config in synoinfo.conf files as well as user config.json. What I need to know is how to change the satamap while loaded in to DSM7mode, via ssh. I normally would mount synoboot1, but seems with tiny core, the satamap is not in the grub.cfg file. Any guidance would be appreciated, because it is really time consuming having to keep switching between tinycore mode and dsm mode to make these changes and then see the results.

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    3 hours ago, Dvalin21 said:

    From what I can see you have the right driver so I dont think its that.  You seem to be having the same issue as me, except I just keep getting a fail. It could be along the lines of what @g4sho was saying as well. Possible glitch that is not showing the correct vid/pid for the usb. And @pocopico NEVER worry (at least with me) about jumping in when your bring better clarity.  Dont mind correction and want to learn.  Thank you so much for the willingness to help and do the work that you do so well.

    @pocopico I concur what @Dvalin21 is saying, thank you for everything. I am gaining knowledge from all of the things you show and have us do. I have gained more in the last few days working with you, than I had in months of lurking and reading the comments.

    • Like 1

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    3 hours ago, pocopico said:

    Sorry for jumping in but I want to clarify some things. @Dvalin21
    @g4sho

    The PCI bus is just the position of the card on the pci bus 

     

    The PCI:ID of the card is what defines which module will be loaded. The alias that each module supports is listed with the modinfo command. 


    the pci id can be listed with lspci -n eg 1000 is the vendor Id and 0072 is the product Id

     

    A database with PCI IDs that also the lspci uses : 

    https://pci-ids.ucw.cz

     

     

    @pocopico exactly what I was saying, mine is at 05:00.0 and that corresponds to pci slot 5 on my server. So we are in agreement. I mentioned to @Dvalin21 that I did not believe it had anything to do with satamap, diskidx etc.

    • Like 1

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    3 hours ago, Dvalin21 said:

    The only one that worked for me is the megaraid. mptsas-3 didnt work for me.  Now with the pci address, would that be used to figure out diskid?  As far as sata there's 8.  I went ahead and tried to lspci -vvv to see if there was some additional info.  where did you see the pci address?

    lspci -vvv 2.99 kB · 4 downloads

    I was referring to @Kaneske pci address of 10:00.0 yours is 08:00.0 as you stated. in my case mine is at 05:00.0 which corresponds to pci slot 5 on my server.

    • Like 1
×
×
  • Create New...