+ Antworten
Ergebnis 1 bis 10 von 523

Hybrid-Darstellung

  1. #1
    Erfahrener Benutzer Avatar von turulbird
    Registriert seit
    01.09.2012
    Beiträge
    136
    Thanks
    65
    Thanked 2 Times in 2 Posts
    Two UFS 910 bad, only one working; without sata.

    Added back panel 16 Gb usb pen, run after only booting... in vfd:

    Code:
    INIT: version  booting
    ------------------------------------------------------------
    deploy.sh version V0.13 (version for Kathrein UFS910)
    ------------------------------------------------------------
    
    <- Mounting USB stick ->
    ./deploy.sh: line 103: can't open /instsrc/Image_Installer.ini: no such file
    grep: /instsrc/Image_Installer.ini: No such file or directory
    grep: /instsrc/Image_Installer.ini: No such file or directory
    grep: /instsrc/Image_Installer.ini: No such file or directory
    grep: /instsrc/Image_Installer.ini: No such file or directory
    -------------------------------------
    Using the following settings:
    
    partition    :
    createmini   :
    keepsettings :
    keepbootargs :
    
    usejfs       :
    useext2e2    :
    
    usbhdd       :
    format       :
    update       :
    -------------------------------------
    sh: 1: unknown operand
    
    <- Formatting HDD (rootfs) ->
    mke2fs 1.46.5 (30-Dec-2021)
    /dev/sda1 contains a vfat file system labelled 'MULTIBOOT'
    Creating filesystem with 4095992 4k blocks and 1024000 inodes
    Filesystem UUID: 
    Superblock backups stored on blocks:
            32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
    
    Allocating group tables: done
    Writing inode tables: done
    Creating journal (16384 blocks): done
    Writing superblocks and filesystem accounting information: done
    
    sh: 1: unknown operand
    <- Skipping installation of root file system ->
    mount: mounting /dev/sda3 on /mnt failed: No such device or address
    umount: can't unmount /mnt: Invalid argument
    -rwxr-xr-x    1 0        0            15712 Aug 11  2022 fw_printenv
    lrwxrwxrwx    1 0        0               21 Aug 11  2022 fw_setenv -> /usr/sbin/fw_printenv
    <- Flashing U-Boot args: Warning: Bad CRC, using default environment
    Can't open /dev/mtd7: Permission denied
    Error: can't write fw_env to flash
    Warning: Bad CRC, using default environment
    Can't open /dev/mtd7: Permission denied
    Error: can't write fw_env to flash
    Warning: Bad CRC, using default environment
    Can't open /dev/mtd7: Permission denied
    Error: can't write fw_env to flash
    Warning: Bad CRC, using default environment
    Can't open /dev/mtd7: Permission denied
    Error: can't write fw_env to flash
    done ->
    
    <- Flashing kernel: done ->
    
    <- Checking HDD rootfs ->
    e2fsck 1.46.5 (30-Dec-2021)
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    ROOTFS: 11/1024000 files (0.0% non-contiguous), 90667/4095992 blocks
    
    <- Job done... ->
    Rebooting...
    booting...
    Geändert von turulbird (12.08.2022 um 21:17 Uhr)


  2. #2
    Developer
    Registriert seit
    18.07.2012
    Ort
    Ridderkerk, Niederlande
    Beiträge
    634
    Thanks
    144
    Thanked 713 Times in 304 Posts
    As stated before: you are using the wrong version. The "flash" version will only work with an internal SATA connected hard disk. There is a slight possibility to get the "flash" to work with an external USB hard disk, by swapping the installation stick and and external hard disk between USB ports until you have found a setup that results in the external hard disk being sda and the installation stick being sdb. This depends on the installation kernels order of scanning the USB ports: the port to which the external hard disk is connected must be scanned first. This however may be prevented altogether by limitations in the boot loader, that may refuse to load the installation kernel or flash files from a USB port other than the front panel one.

    "Two UFS 910 bad, only one working; without sata." Again: what are you trying to tell me? You have three UFS910's and two are broken? This information is not relevant given the problem.

    It seems to me you have flashed an miniFLASH.img with an installation kernel in it, together with a set of boot arguments that tell the boot loader to start the kernel in flash. This setup will never start an USB image residing on a USB stick.
    My suggestion is going back to a defined starting state, by first installing the original boot loader and a factory Kathrein firmware using AAF recovery tool. Then start over carefully obeying all installation instructions to the letter. As long as there is no working internal SATA hard disk in your UFS910, do NOT attempt to install a "flash" version: you will only end up with the problems you are experiencing now.

    Regards,

    Audioniek.
    Geändert von Audioniek (13.08.2022 um 12:02 Uhr)
    Receivers: Rebox: RE-4000, 8000, 9000, 2200, 2210, 2220, 4200, 4210, 4220, 8220, 8500, SAB Unix Triple, Golden Media Spark TripleX, Amiko Alien 2+, Sogno Spark Revolution, Kathrein UFS910(1 & 14W)/912/913/922(CX24116 & AVL2108 tuners), Vizyon revolution 820HD PVR, AB IPBox 91HD/9000HD/9000HD rev.2, Xsarius Alpha HD10, nBox BKSA/BSLA/BXZB/BZZB, Vitamin HD 5000
    Sats: Astra 1, 2 & 3, Hotbird
    Main activity: building my own E2 images for Fortis receivers

  3. The Following User Says Thank You to Audioniek For This Useful Post:



Berechtigungen

  • Neue Themen erstellen: Ja
  • Themen beantworten: Ja
  • Anhänge hochladen: Ja
  • Beiträge bearbeiten: Ja
  •