recovery

摘要 Recovery模式指的是一种可以对安卓机内部的数据或系统进行修改的模式（类似于windows PE或DOS）。也可以称之为安卓的恢复模式，在这个所谓的恢复模式下，我们可以刷入新的安卓系统，或者对已有的系统进行备份或升级，也可以在此恢复出厂设置（格式化数据和缓存）。 1. Recovery相关概念 Recovery： Recovery模式指的是一种可以对安卓机内部的数据或系统进行修改的模式，也指Android的Recovery分区 OTA: Over－the－Air Technology，即空中下载技术，是 Android 系统提供的标准软件升级方式。 它功能强大，提供了完全升级、增量升级模式，可以通过 SD 卡升级，也可以通过网络升级。不管是哪种方式，都有几个过程：生成升级包、下载升级包、安装升级包。 RecoverySystem：Android系统内部实现的一个工具类，Android应用层操作Recovery模式的一个重要途径，它提供了几个重要的API，用于实现OTA包校验、升级以及恢复出厂设置（格式化数据和缓存）。 Main System：主系统模式，即Android正常开机所进入的Android系统 Bootloader：Bootloader是嵌入式系统在加电后执行的第一段代码，在它完成CPU和相关硬件的初始化之后

I want to set the Recovery Options on a Windows Service I'm installing on a Windows Server 2003. I know this is possible to do manually, but I want to set the Recovery configuration when I install the service. I use SC script to do this: SC create MyService displayname= "MyService" binpath= "C:\Program Files\MyService\MyService.exe" start= auto SC failure MyService reset= 86400 actions= restart/1000/restart/1000/run/1000 SC failure MyService command= "C:\Program Files\Myservice\MyService.exe" The problem is when the first whitespace is hit, it cuts off the path and takes the rest of the path

1、服务器状况，mysql无法启动，日志提示Error: page 13476 log sequence number 2、使用service mysql start命令启动mysql失败 3、查询mysql的日志文件localhost.localdomain.err,提示Error: page 13476 log sequence number 50961222223 4、查询资料和解决办法 5、编辑mysql的配置文件my.cnf，添加innodb_force_recovery属性 设置 innodb_force_recovery = 1，然后保存修改，执行service mysql start命令，启动mysql innodb_force_recovery = 1不行就改成2,2不行改成3，以此类推，最大值为6， 我是在innodb_force_recovery = 3时启动成功的（俗称抢救模式，临时开启，可拿下数据，） 6、导出数据库中的数据 7、删除数据库 8、将my.cnf中的innodb_force_recovery 属性改为0，innodb_force_recovery = 0，或者删掉这个属于 9、重启mysql数据库 10、新建数据库，将导出的数据再导入进去即可（也可以重装mysql然后导入数据） 来源： https://www.cnblogs.com

ORA-00257: archiver error. Connect internal only, until freed 错误的处理方法 方法一: 参考: http://blog.csdn.net/panys/article/details/3838846 archive log日志已满 ORA-00257: archiver error. Connect internal only, until freed错误的处理方法 1.用sys用户登录 sqlplus sys/pass@tt as sysdba 2.看看archiv log所在位置 SQL> show parameter log_archive_dest; NAME TYPE VALUE --------------------------------- --- ----------- ------------------------------ log_archive_dest string log_archive_dest_1 string log_archive_dest_10 string 3.一般VALUE为空时，可以用archive log list;检查一下归档目录和log sequence SQL> archive log list; Database log mode Archive Mode

实验系统：ubuntu-16.04.6-server-amd64 我在VMware安装完这个系统后进入发现卡在了’SMBus Host Controller not enabled‘里，后来查过网络发现，需要禁止i2c_piix4驱动的加载，禁止需要编辑blacklist.conf： 方法如下： 1、在ubuntu开机时进入grub启动选项 2、选择Advanced options for Ubuntu 3、进入Ubuntu的恢复模式（recovery mode） 4、在Recovery Menu中选择root进入root shell 5、输入：mount -o remount,rw / （注：“，”号两边不加空格） 6、编辑blacklist.conf （路径：/etc/modprobe.d/blacklist.conf）（命令：vi /etc/modprobe.d/blacklist.conf） （！注意：在编辑文本前，请确定自己是否会使用vi，ubuntu的vi与centos、Redhat的vi有很多不同，若之前没用过ubuntu的vi，请在网上查询ubuntu的vi的使用方法） 7、在blacklist.conf的最后一行加上：blacklist intel_powerclamp 8、保存后重启即可 来源： https://www.cnblogs.com/howielu/p

Let's say, I delete a PostgreSQL docker container which had its data only here: $ docker inspect postgres1 ... "Source": "/var/lib/docker/volumes/4948af..../_data" "Destination": "/var/lib/postgresql/data" $ docker rm postgres1 If there was no other container referencing the volume, I cannot reconnect to this volume with --volumes-from any more, even though the files are still on disk somewhere in: /var/lib/docker/volumes/... This presents me with two problems: What is the best way to locate the data , if I do not know the volume UUID of the directory? Doing ls /var/lib/docker/volumes/

I obliterated all my work and would prefer not to explain how. The only thing I have left are the git objects. More then anything I would like to recover some of the loss packed Image files. From the size of the object files I can tell which ones they are. Is there a way to turn them back into usable files? first thing: make a backup! then work on a copy of that backup. if the git objects are still in the correct directory ( .git/objects/xx/xxx… ) you can use git fsck --full for git to discover them — it will probably list every object in your repository. now look for the ones labeled commit

Help, I screwed up. I have a somewhat complex python script that is currently running in a putty window to a Ubuntu server. I accidentally overwrote the script using another putty window, so the copy on the hard drive is now gone, but the script is still running from memory in the first window. This happened before I had a chance to run my backups for this folder. Is there a way I can get the script, (that is currently running) from the memory in the first putty window? I haven't stopped the script, my guess is once I stop it it will be gone forever. Can I send it to a background process