Skip to main content

installing fedora on reiserfs

Natively, this is not possible, but I did it anyway to get around a faulty disk with bad sectors on a notebook.

Step 1

I used knoppix live distribution to boot the machine since the whole previous OS was corrupted by the disk anyway.

Step 2

Next, I started the guessing game on how much of the disk I didn't want. Ok, its not that graceful, but i didn't want to spend like 2 hours scanning to look for bad sectors. Although one of the things I would do is to try to find them later.

I spilt the disk to 2 x 20 Gb partitions and left some out of that for swap of the 2nd partition.

fdisk /dev/hda
(d)elete
(n)new partition
(p)rimary partition <1>
(n)new partition
(p)rimary partition <2>
(w)rite partition and exit

*optional as this gets blown away in disk druid anyway. Just leave some room for swap. Traditionally, its 2 x RAM available.
(n)new partition
(p)rimary partition <3>

After exiting the fdisk tool. You have created partitions, but not formated them. I wanted a journalised file system so i formated the created partitions to reiserfs. Its quite a good FS which I have been relatively impressed with since my Mandrake machine came with reiser as the default filesystem.

# mkreiserfs /dev/hda1
# mkreiserfs /dev/hda2


Step 3

Reboot to Fedora install and select manually use disk druid for install. Convert the last partition to swap and attempt to install to first partition

When prompted to format say no. they will still force you to format the swap, so thats cool.


Step 4

As predicted the first attempt at installation to /dev/hda1 failed.

No worries. Run the install again and select /dev/hda2 as / mount aka root mount aka mount as / just in case I haven't confused you enough.


Step 5

Wait. In fact my installation is still running. Hopefully it goes sucessfully. This should breathe some life into old notebooks which will be a waste trying to pick up a new harddisk for it.

Comments

Aaron Lee said…
Home user, my ass!
You show use the word verification. You're getting spammed too.

Popular posts from this blog

Multiple Broadlink RM mini 3 integration using MQTT

Broadlink now has quite a lot of integration options almost out of the box. If you enable Broadlink IHC, you can directly link it to Alexa by giving the device a unique name.

There is a homebridge plug in for homekit integration but I haven't tried or tested this. https://lprhodes.github.io/slate/

I wanted to put the device in domoticz so I can have more control over what can trigger my broadlink. I decided to use broadlink-mqtt for this, which is a fairly easy method to trigger from any source.

Setup Instructions for broadlink-mqtt

1. git clone https://github.com/eschava/broadlink-mqtt

2. vi /home/pi/broadlink-mqtt/mqtt.conf

3. Update the mqtt.conf file with the device type set as multiple_lookup

device_type = 'multiple_lookup'
mqtt_multiple_subprefix_format = '{type}_{mac_nic}/'
4. Start the python script and check that it started and detected all the RM devices.
Check the log file to see what the IP / MAC addresses are. DEBUG Connected to RM2 Broadlink device at …

Fibaro HCL Virtual Device Slider

How to setup Fibaro home center lite (HCL) slider for virtual devices.

As the Fibaro HCL does not support LUA. The question was how to update the number value of the slider to send to the HTTP string. Thanks to this site which is a really good reference https://www.vesternet.com/resources/application-notes/apnt-88/

The 2 use cases here are;

Sonos HTTP API Volume

To allow for volume control for all Sonos devices, add a virtual device with the IP address for SONOS HTTP API and specify the default port to 5005. Create Slider and put the following text into the string.

GET /volume/_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A


Domotiz Virtual Devices

GET /json.htm?type=command&param=switchlight&idx=XX&switchcmd=Set%20Level&level=_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A

Replace XX with the device ID.

Restart Fibaro HCL when it stops working automatically

It seems that the Fibaro HCL seems to hang every now and then. Instead of trying to restart it regularly, which doesn't really work, as it's almost impossible to predict when this will happen.

This method checks that the HCL is actually running and in the event it stops working, trigger a script that will restart it.


1. Get a non Fibaro controlled power plug and scripts to control it.

I used a wifi smart plug, TP-link HS100 and downloaded the scripts from

https://blog.georgovassilis.com/2016/05/07/controlling-the-tp-link-hs100-wi-fi-smart-plug/

2. Create a bash script to restart the Fibaro, e.g. restart_fibaro.sh

#!/bin/bash

ip_addr=
scripts=

$scripts/tplink-smartplug.py -t $ip_addr -c off
sleep 10
$scripts/tplink-smartplug.py -t $ip_addr -c on


3. Create a test global variable in the Fibaro HCL

Go to the variables panel and create a test variable, e.g. Test


4. Add a cron entry to test that the Fibaro API is still working and restart if it's not.

The cron script is scheduled ev…