<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by ibilgen on Medium]]></title>
        <description><![CDATA[Stories by ibilgen on Medium]]></description>
        <link>https://medium.com/@ismbil?source=rss-dbf02fde5ca6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*we5s8yDg3rKdUJlI</url>
            <title>Stories by ibilgen on Medium</title>
            <link>https://medium.com/@ismbil?source=rss-dbf02fde5ca6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:10:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ismbil/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Matplotlib Installation Error in Windows 10]]></title>
            <link>https://medium.com/@ismbil/matplotlib-installation-error-in-windows-10-4c38c0c98c0f?source=rss-dbf02fde5ca6------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c38c0c98c0f</guid>
            <category><![CDATA[matplotlib]]></category>
            <category><![CDATA[installation]]></category>
            <category><![CDATA[error]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[ibilgen]]></dc:creator>
            <pubDate>Wed, 07 Aug 2024 07:25:52 GMT</pubDate>
            <atom:updated>2024-08-07T07:25:52.448Z</atom:updated>
            <content:encoded><![CDATA[<p>I encountered an error while trying to install matplotlib using pip in Windows 10. I simply run the command below in a venv virtual environment to install matplotlib library.</p><pre>$ python -m pip install -U matplotlib</pre><p>However, it encountered an error while generating package metadata (pyproject.toml).</p><pre>Preparing metadata (pyproject.toml) ... error<br>  error: subprocess-exited-with-error<br><br>  × Preparing metadata (pyproject.toml) did not run successfully.<br>  │ exit code: 1<br>  ╰─&gt; [22 lines of output] </pre><p>As a neat solution to this easy yet to be time sink problem, I just added the --prefer-binary and the problem has solved.</p><pre>$ python -m pip install -U matplotlib --prefer-binary</pre><p>For more information, you can check out <a href="https://matplotlib.org/stable/install/index.html">Installation — Matplotlib 3.9.1 documentation</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c38c0c98c0f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Putty Running Error on macOS and How to Fix]]></title>
            <link>https://medium.com/@ismbil/putty-running-error-on-macos-and-how-to-fix-25bdeac7f89a?source=rss-dbf02fde5ca6------2</link>
            <guid isPermaLink="false">https://medium.com/p/25bdeac7f89a</guid>
            <category><![CDATA[cannot-open-display]]></category>
            <category><![CDATA[macos]]></category>
            <category><![CDATA[putty]]></category>
            <category><![CDATA[gtk-warning]]></category>
            <dc:creator><![CDATA[ibilgen]]></dc:creator>
            <pubDate>Thu, 13 Feb 2020 17:30:19 GMT</pubDate>
            <atom:updated>2020-02-13T17:46:04.841Z</atom:updated>
            <content:encoded><![CDATA[<p>I installed putty in macOS Catalina computer through terminal but I have got the following errors when I open putty</p><p><strong>&gt; putty</strong></p><pre>(process:6167): Gtk-<strong>WARNING</strong> **: 19:41:45.778: Locale not supported by C library.</pre><pre>Using the fallback ‘C’ locale.</pre><pre>(putty:6167): Gtk-<strong>WARNING</strong> **: 19:41:45.786: cannot open display:</pre><p>To solve this, I applied the following steps:</p><ol><li>Install X11 from <a href="https://www.xquartz.org/">https://www.xquartz.org/</a></li><li>Open X11 from Applications -&gt; Utilities -&gt; X11</li><li>Use “printenv” to see if the DISPLAY variable is set. If it is not set then use the following command to set</li></ol><p><strong>&gt; export DISPLAY=”:0&quot;</strong></p><p>4. See locale</p><p><strong>&gt; locale</strong></p><pre>LANG=&quot;&quot;<br>LC_COLLATE=&quot;C&quot;<br>LC_CTYPE=&quot;UTF-8&quot;<br>LC_MESSAGES=&quot;C&quot;<br>LC_MONETARY=&quot;C&quot;<br>LC_NUMERIC=&quot;C&quot;<br>LC_TIME=&quot;C&quot;<br>LC_ALL=</pre><p>5. If LANG is empty, see locale identifiers for your language</p><p><strong>&gt; locale -a</strong></p><p>6. Set LANG to that fits you</p><p><strong>&gt; export LC_ALL=”tr_TR.UTF-8&quot;</strong></p><p>7. Add necessary commands to your .profile settings in your home folder to set it every time you open a terminal</p><p>That’s all!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25bdeac7f89a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Recover Files from a RAID System using a Bootable Linux USB Flash Drive]]></title>
            <link>https://medium.com/@ismbil/how-to-recover-files-from-a-raid-system-using-a-bootable-linux-usb-flash-drive-c4a02727b34c?source=rss-dbf02fde5ca6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4a02727b34c</guid>
            <category><![CDATA[recover-files]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[raid]]></category>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[bootable-usb]]></category>
            <dc:creator><![CDATA[ibilgen]]></dc:creator>
            <pubDate>Fri, 08 Nov 2019 14:43:13 GMT</pubDate>
            <atom:updated>2022-01-24T17:02:10.501Z</atom:updated>
            <content:encoded><![CDATA[<p>When my Linux OS has failed to start, I decided to recover my important files using a bootable Linux USB disk before any attempt to fix the OS. I booted the computer from USB disk which was created with “Startup Disk Creator”. Then I selected “Try Ubuntu” option. But, I couldn’t see the the main disk which is setup with RAID system. After a search of the issue, I got that I need to mount the device to view the files.</p><p>First, run <strong>fdisk</strong> command to view all disk partitions. You can find the disk where the home directory exists from the size and type information.</p><pre>bilgen@ubuntu:~$ <strong>sudo fdisk -l</strong><br>[sudo] password for bilgen: <br>Disk /dev/loop0: 1.5 GiB, 1601015808 bytes, 3126984 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes</pre><pre>Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 4096 bytes<br>I/O size (minimum/optimal): 4096 bytes / 4096 bytes<br>Disklabel type: gpt<br>Disk identifier: F1DF14A1-CEAA-4358-8F23-7E045C825302</pre><pre>Device     Start        End    Sectors  Size Type<strong><br>/dev/sda1   2048 7814035455 7814033408  3.7T Linux RAID</strong></pre><pre>Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disklabel type: gpt<br>Disk identifier: C0D2CED1-16BC-4863-B338-4FFBF6BEA339</pre><pre>Device         Start       End   Sectors   Size Type<br>/dev/sdb1       2048      4095      2048     1M BIOS boot<br>/dev/sdb2       4096 195315711 195311616  93.1G Linux filesystem<br>/dev/sdb3  195315712 976771071 781455360 372.6G Linux filesystem</pre><pre>Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 4096 bytes<br>I/O size (minimum/optimal): 4096 bytes / 4096 bytes<br>Disklabel type: gpt<br>Disk identifier: 80FB5BD5-2E09-4AB8-8D25-BC6F0990DE11</pre><pre>Device     Start        End    Sectors  Size Type<br>/dev/sdc1   2048 7814035455 7814033408  3.7T Linux RAID</pre><pre>Disk /dev/sdd: 3.8 GiB, 4027580416 bytes, 7866368 sectors<br>Units: sectors of 1 * 512 = 512 bytes<br>Sector size (logical/physical): 512 bytes / 512 bytes<br>I/O size (minimum/optimal): 512 bytes / 512 bytes<br>Disklabel type: dos<br>Disk identifier: 0x6fee4eb0</pre><pre>Device     Boot   Start     End Sectors  Size Id Type<br>/dev/sdd1  *          0 3251199 3251200  1.6G  0 Empty<br>/dev/sdd2       3221944 3226935    4992  2.4M ef EFI (FAT-12/16/32)<br>bilgen@ubuntu:/media/ubuntu/3019fd60-4ebb-417f-87b6-a0ec185bc564/home$ cat /proc/mdstat <br>Personalities : <br>unused devices: &lt;none&gt;</pre><p>You can’t directly mount a disk with a RAID system. You need to run mdadm command to assemble the RAID array. I added <strong>force </strong>argument to accomplish the process.</p><pre>bilgen@ubuntu:~$ sudo mdadm --assemble --scan<br>mdadm: /dev/md/0 assembled from 2 drives - not enough to start the array while not clean - consider --force.</pre><pre>bilgen@ubuntu:~$ <strong>sudo mdadm --assemble --scan --force</strong><br>mdadm: Marking array <strong>/dev/md/0</strong> as &#39;clean&#39;<br>mdadm: <strong>/dev/md/0</strong> has been started with 2 drives (out of 3).</pre><p>Note: Install mdadm if it is not installed.</p><pre>bilgen@ubuntu:~$ sudo apt-get install mdadm</pre><p>You can mount the device now.</p><pre>bilgen@ubuntu:~$ sudo mount /dev/md/0 /home/bilgen/Desktop</pre><p>That’s it! Once you mounted it, you can access and copy your files.</p><pre>bilgen@ubuntu:~$ cd /home/bilgen/Desktop/<br>bilgen@ubuntu:~/Desktop$ ls<br>lost+found  user1 user2  VirtMach  workspace</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/890/1*S7Jv54jwUfH_NyT39W-oDg.png" /></figure><p>Below commands are useful for examination</p><p>$ cat /proc/mdstat</p><p>$ lsblk -o NAME,SIZE,FSTYPE,TYPE,MOUNTPOINT</p><p>After all done, it should look like below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/819/1*gXiCXbYNN883F0nLzc8qyQ.png" /></figure><p>Note: When md0 exists in /proc/mdstat but seems to be inactive , I stopped the service then try assembling.</p><p>$ sudo mdadm --stop /dev/md0</p><p>$ sudo mdadm --assemble --scan</p><p>Run the service</p><p>sudo mdadm --manage /dev/md0 --run</p><p>To make the RAID device automatically mount at boot time</p><p>$ mdadm --examine --scan &gt;&gt; /etc/mdadm/mdadm.conf</p><p>For more information:</p><p><a href="https://www.digitalocean.com/community/tutorials/how-to-create-raid-arrays-with-mdadm-on-ubuntu-18-04">https://www.digitalocean.com/community/tutorials/how-to-create-raid-arrays-with-mdadm-on-ubuntu-18-04</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4a02727b34c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>