How to re-hide the hidden partition (Q) on Lenovo X220

Somehow I accidentally evoked the restore process which revealed the hidden 'Q' partition on my Lenovo X220 which is around 12GB in size. After some poking around I found how to re-hide it.

Download this little partition editor from Symantec. N.B Had to use a shortened URL as Posterous doesn't like FTP links.
Run the exe and select the 3rd partition as shown (If the partition is currently visible, it will be showing '07' like the other partitions)

Click in the first column and choose Set Type and select option '17', Hidden IFS (NTFS, HPFS) as I've done.

Save Changes, exit and reboot

Worked a treat for me after a nervous wait for it to reboot.

Comments

How to retain your GUI settings in Kodi

When you restore Kodi or copy your existing Kodi userdata folder to another device it will always default the guisettings.xml, always. Even if you drop your previous settings into Kodi via a network folder, it will still reload it to default upon restart. This is because the guisettings.xml can't be written into the userdata folder when Kodi is running. To prevent this from happening, overwrite the guisettings.xml with SSH using two programs. One to stop and start the Kodi process and one to copy over the backed up guisettings.xml file that contains all your GUI goodness.

Using ESPEasy with Home Assistant via MQTT

Preface: I've just started playing around with Home Assistant on a Raspberry Pi and exploring the world of MQTT to control devices on the network. Learning curve is a bit steep but worth the effort as MQTT is very fast. The hardware and software tools I'm using are as follows: 2 x Sonoff relay units 2 x NodeMCU Boards ESPEasy firmware (must be version 121 or above as that contains the MQTT 'retain' flag option. Home Assistant software on Raspberry Pi2 MQTT Test Software: PC: MQTT.fx Android: MQTT Dashboard

How to check what entities are filling up your Home Assistant database

If you use the Home Assistant MariaDB add-on, this tip will show you how to query the database so see what Home Assistant entity states are triggering the most, filling up your database. What were going to do: Install the phMyAdmin add-on for MariaDB. Query the MariaDB database. See what entity state changes have the most action. Paste the code below into the SQL query box: select entity_id,count( * ) from states group by entity_id order by count ( * ) desc; And if you're using the internal home-assistant_v2.db instead, you can use the SQLite Web add-on to achieve the same thing.

XBMCNut

Search This Blog