tag:blogger.com,1999:blog-61852891706106244512024-03-19T21:06:32.373-07:00Tecsun's Linux JourneyTecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.comBlogger84125tag:blogger.com,1999:blog-6185289170610624451.post-74021212088135432682018-08-29T06:28:00.000-07:002018-08-29T06:28:59.560-07:00Device Not Found when Removing HDD from mdadm RAID<div>
I have encountered a case when I'm trying to fail and remove a disk from a mdadm RAID array using the following two commands:</div>
<div>
<ul>
<li><b><i>mdadm --manage /dev/md1 --fail /dev/sdf --remove /dev/sdf</i></b></li>
<li><b><i>mdadm /dev/md1 --fail /dev/sdf --remove /dev/sdf</i></b></li>
</ul>
<div>
<div>
I encountered error "device not found".</div>
</div>
</div>
<div>
<br /></div>
<div>
Looking at the Disks (gnome-disks), the device /dev/sdf is still shows as a member of RAID /dev/md1.</div>
<div>
<br /></div>
<div>
<br /></div>
<div>
<span style="color: #0b5394; font-size: large;"><b>What is the solution?</b></span></div>
<div>
<i><br /></i></div>
<div>
After examine using both:</div>
<div>
<ul>
<li><b><i>mdadm --detail /dev/md1</i></b></li>
<li><b><i>cat /proc/mdstat</i></b></li>
</ul>
<div>
Confirming that /dev/sdf is not currently active in the RAID array, I execute <b><i>mdadm --zero-superblock /dev/sdf</i></b>. This reset the HDD and now it appears as an empty disk in Disks (gnome-disks).</div>
</div>
<div>
<br /></div>
<div>
I can then re-add the HDD to the array again as a spare unit, <b><i>mdadm --add /dev/md1 /dev/sdf</i></b>.</div>
<div>
<br /></div>
Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-59840483931210847022018-05-26T09:18:00.001-07:002018-05-26T21:16:19.847-07:00Setting Up Red Hat Virtualization with Single Server<div dir="ltr">
Red Hat Virtualization is an interesting and powerful platform software, but it is rather challenging to setup with only a single host when compared to Hyper-V, VMware and VirtualBox. One may argue that RHEV is not design for single host (I guess that is why there is no single article about how to do the setup), but who really care if just want to use for a tiny scale deployment? Single host rules!</div>
<div dir="ltr">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhyPzjjvQqMV_h4xYJ2WBjsHSKQt6ukj2rMTmlZtOJJA-LDUXfcfFlnDaafJBs0zsBwV-veHIhyphenhyphenE-9OkqGWpNcnaKET6CW8zJnKtqA9K5Y5GdllvKNQpJ7tuxYfzer0ybzgbkzTbMfqASI/s1600/471.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="500" data-original-width="660" height="242" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhyPzjjvQqMV_h4xYJ2WBjsHSKQt6ukj2rMTmlZtOJJA-LDUXfcfFlnDaafJBs0zsBwV-veHIhyphenhyphenE-9OkqGWpNcnaKET6CW8zJnKtqA9K5Y5GdllvKNQpJ7tuxYfzer0ybzgbkzTbMfqASI/s320/471.png" width="320" /></a></div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
Well, I could go for RHEL + KVM, but I simply like the interface of RHEV. </div>
<div dir="ltr">
Getting it up and running requires user to have experience from numerous area of expertise. This simplified guide is not for newbie. </div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
Setting up the RHVH is not hard. I'm going to skip it. Now, in order to get the hosted-engine up and running, please make sure the following are done:</div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
1. Change the hostname <b>localhost.</b><b>localdomain</b><b> </b>to hostname. In my case, I use <b>robustpoc</b><b>.</b><br />
2. Be sure to set a fix IP in <i>/etc/</i><i>sysconfig</i><i>/</i><i>network-scripts</i><i>/</i><i>ifcfg-</i><b><i>eth0</i></b><i> </i>and reconnect using the new IP using <i>ifdown</i><i> </i><i>eth0</i><i> </i><i>and</i><i> </i><i>ifup</i><i> </i><i>eth0</i><i>.</i><br />
<i>3. </i>Edit <i>/</i><i>etc/hosts </i>to resolve the host IP address to the hostname. <br />
4. In order to make this IP change persistent, be sure to change the settings in <i>/</i><i>var</i><i>/lib/</i><i>vdsm</i><i>/persistence/</i><i>netconf</i><i>/nets/</i><i>ovirtmgmt</i></div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
Note: If the server is in a VLAN Network, be sure to set a correct gateway otherwise it would not be able to connect to Internet or reach by others in the network. </div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
5. Now, before proceed with executing <i>hosted-engine</i><i> --deploy</i>, you require to add your FQDN to <i>/</i><i>etc/hosts.</i><i> </i>In my case, I use 192.168.0.26 <b>robustpoc.com</b><b>.</b> This is critical.<br />
6. Next, setup NFS share. Follow the guide below:</div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
<u>Setup NFS </u>server: <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">https://</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">access.redhat.com</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">/documentation/</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">en-us</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">/</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">red_hat_enterprise_linux</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">/7/</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">html</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">/</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">storage_administration_guide</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">/</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">nfs-serverconfig</a></div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
<u>Configuring NFS </u>server: <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">https://</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">access.redhat.com</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">/documentation/</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">en-us</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">/</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">red_hat_enterprise_linux</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">/7/</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">html</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">/</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">storage_administration_guide</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">/</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">nfs-</a><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig">serverconfig</a></div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
7. At this point, we are ready to execute <i>hosted-engine</i><i> --</i><i>deploy</i>. </div>
<div dir="ltr">
<b>Three critical </b><b>settings</b><b> </b><b>to</b><b> </b><b>take</b><b> note </b><b>during</b><b> </b><b>the</b><b> process:</b><br />
8. Be sure NOT to set the memory of the VM to maximum available memory of the system as per suggested by the setup. Setting to maximum will lead to no available memory to create any single Virtual Machine. <br />
9. Be sure to use a fixed IP for the engine. Make sure gateway is correct too. <br />
10. Be sure to answer YES when asked whether to update the <i>/etc/hosts</i> for both the host and engine VM. The default answer is NO. Missing out this would be a killer later.</div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
Until this point, everything critical should have already been taken care of. Cross finger and I wish you the best luck!</div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
Common errors that I have encountered but do not guarantee to happen:<br />
1. Error: [Get Local VM IP] failed<br />
2. Info: [Waiting for local VM to be up] <br />
3. [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook; then I can access to RHEV Manager but an failed <i>external</i><i> </i><i>hosted</i><i> </i><i>engine</i> present in the Compute > Hosts. </div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
Welcome to share with me your installation experience, I'm happy to listen and learn from you. </div>
Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com1tag:blogger.com,1999:blog-6185289170610624451.post-78230356161890526472015-12-23T17:13:00.001-08:002015-12-23T17:13:38.670-08:00Mdadm Must Be Configured on PartitionRefer to my previous post <a href="http://linuxtecsun.blogspot.my/2015/06/missing-mdadam-array-after-reboot.html" target="_blank">Missing mdadm array after reboot</a>, I would like to add on the reason why auto-scan does not work once system rebooted - it requires the RAID to be configured on a partition instead of the disks!<br />
<br />
This is going to have problem:<br />
<blockquote class="tr_bq">
mdadm --create --level=6 --raid-devices=5 /dev/md0 /dev/sd[b-f]</blockquote>
and this would be correct, please take note of the digit at the end of line:<br />
<blockquote class="tr_bq">
mdadm --create --level=6 --raid-devices=5 /dev/md0 /dev/sd[b-f]1 </blockquote>
<br />
It means you must format all the disks with at least one partition, and building the RAID using the partition.<br />
<br />
I hope this would be helpful for novice users who trying to get the RAID run properly.Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-73102249908950118692015-11-09T16:42:00.001-08:002015-11-09T16:42:54.609-08:00Problem Updating Repo List in Ubuntu 12.10The sources list has been changed to <i>old-releases</i>. To replace the sources list easily, use the following command:<br />
<br />
<b><i>sudo sed -i -e 's/archive.ubuntu.com\|security.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list</i></b><br />
<div>
<br /></div>
<div>
If you have choose another mirror then your sources list might contain <i>us.archive.ubuntu.com</i>, then the above changes would still be invalid. You would need to remove the <i>us.</i> from it. Using the command below will help remove it:</div>
<div>
<br /></div>
<b><i>sudo sed -i -e 's/us.old-releases.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list</i></b>Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-85739125676675988302015-10-04T03:37:00.000-07:002015-10-04T03:37:40.571-07:00Houdini Start-Up Crashed on Render NodeAFAIK, Houdini could not start its main application (GUI) without OpenGL enabled graphics card. Hence if you are trying to start it in a render node with ASPEED on-board graphics, it is impossible. All you can do is to run the render using CLI.<br />
<br />
As for user encounters the same issue, if you are using Nvidia graphics card, you would need to switch the XORG graphics driver to Nvidia proprietary driver. You can do it at:<br />
<br />
<i><b>Menu > Settings > Software and Update > Additional Drivers</b></i><br />
<br />
Sometimes the latest driver may not work well.<i><b> </b></i>So you may have to tried different version to get it work.<br />
<br />
<i>Tips: To get a clearer picture of why Houdini failed to start, instead of running it from software menu, you can run it from terminal. The error message will be more readable than the crashed dump file.</i>Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-35082338222466092712015-06-17T21:50:00.001-07:002015-12-23T17:07:10.079-08:00Missing mdadm array after rebootIt is heart-attack when you reboot your linux storage server and realized mdadm array gone missing!<br />
<ul>
<li>RAID volume not showing in <i><b>gnome-disks.*</b></i></li>
<li><i><b>gparted</b> </i>reports empty partition on all the RAID disks</li>
</ul>
<i><b>sudo mdadm --examine --scan -v</b></i> shows:<br />
<blockquote class="tr_bq">
mdadm: looking for devices for /dev/md0<br />
mdadm: Cannot assemble mbr metadata on /dev/sda<br />
mdadm: Cannot assemble mbr metadata on /dev/sdb<br />
mdadm: Cannot assemble mbr metadata on /dev/sdc<br />
mdadm: Cannot assemble mbr metadata on /dev/sdd<br />
mdadm: Cannot assemble mbr metadata on /dev/sde</blockquote>
<i><b>sudo mdadm --examine /dev/sd* </b></i>or <i><b>mdadm --query /dev/sd* </b></i>shows:<br />
<blockquote class="tr_bq">
mdadm: No md superblock detected on /dev/sd*</blockquote>
<i><b>sudo mdadm --assemble /dev/sd[b-f] </b></i>shows:<br />
<blockquote class="tr_bq">
mdadm: device /dev/sdb exists but is not an md array.<br />
mdadm: No arrays found in config file or automatically</blockquote>
If you go into <i>/etc/mdadm/mdadm.conf </i>(Debian / Ubuntu) or <i>/etc/mdadm.conf </i>(Fedora), you would realize there is no ARRAY being defined. In some system the<i> mdadm.conf </i>simply does not exist.<br />
<br />
No matter how hard you try, the mdadm array just won't show up. There are numerous suggestion on the web, being the most common is to add an auto examine during boot in the <i>mdadm.conf</i>:<br />
<blockquote class="tr_bq">
sudo mdadm --examine --scan --config=mdadm.conf >> /etc/mdadm/mdadm.conf</blockquote>
However the above simply does not work for me. I have also try adding the ARRAY manually by doing the following, in which the UUID is the first hdd used for the array (to show the UUID, use <i><b>blkid</b></i>. Strange enough I could not get the UUID of my GPT hdd in Ubuntu, and only can get by using Fedora):<br />
<blockquote class="tr_bq">
ARRAY /dev/md0 metadata=1.2 UUID="0db0c336:f56bd888:2f9e92e4:c1d64c09" >> /etc/mdadm/mdadm.conf </blockquote>
It does not work as well. I have no other solution except try to re-create the array again. Be very careful of this step, I'm more daring to take this step because I already backup my data one day before I lost the array. When you re-create the array, <b>BE SURE </b>to use <i><b>--assume-clean</b></i> and make sure the parameter set is EXACTLY the same as what you used to create it the first time. In my case, it is very simple and straightforward: <br />
<blockquote class="tr_bq">
mdadm --create --assume-clean --level=6 --raid-devices=5 /dev/md0 /dev/sd[b-f]</blockquote>
The RAID array is being created and immediately I got all my data back!! It is advisable to backup your data now and once the backup is done, do a data scrubbing to ensure it is running well.<br />
<br />
I hope you will be as lucky as I do, to have all the data back without losing great memory and important works.<br />
<br />
<br />
External link that I used as reference:<br />
<ul>
<li>A very useful read: <a href="https://raid.wiki.kernel.org/index.php/RAID_Recovery">https://raid.wiki.kernel.org/index.php/RAID_Recovery</a> </li>
<li><a href="https://hiringsolved.com/blog/goodbye-big-data-mdadm-no-recognizeable-superblock/">https://hiringsolved.com/blog/goodbye-big-data-mdadm-no-recognizeable-superblock/</a></li>
<li><a href="http://ubuntuforums.org/archive/index.php/t-2090527.html">http://ubuntuforums.org/archive/index.php/t-2090527.html</a></li>
<li><a href="http://kevin.deldycke.com/2007/03/how-to-recover-a-raid-array-after-having-zero-ized-superblocks/">http://kevin.deldycke.com/2007/03/how-to-recover-a-raid-array-after-having-zero-ized-superblocks/</a> (be very careful with this, I would not suggest zero out the superblock unless you know what it does) </li>
<li><a href="http://ubuntuforums.org/showthread.php?t=1950154">http://ubuntuforums.org/showthread.php?t=1950154</a></li>
<li><a href="http://superuser.com/questions/603481/how-do-i-reactivate-my-mdadm-raid5-array">http://superuser.com/questions/603481/how-do-i-reactivate-my-mdadm-raid5-array</a></li>
<li>Changing UUID of a mdadm partition: <a href="https://itooktheredpill.irgendwo.org/2010/change-uuid-of-a-mdadm-partition/">https://itooktheredpill.irgendwo.org/2010/change-uuid-of-a-mdadm-partition/</a></li>
<li>This is not useful in my case, but maybe helpful for others: <a href="http://askubuntu.com/questions/247981/software-raid-mdadm-re-find-my-array">http://askubuntu.com/questions/247981/software-raid-mdadm-re-find-my-array</a></li>
</ul>
<br />
<br />
* <i><b> </b>If it is shown, then you are lucky because it simply changes
its name from /dev/md0 to something like /dev/md127. You can still use
it by changing the mounting command to the new array name.</i>Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-18615013405887946812015-04-28T19:49:00.002-07:002015-04-28T19:49:18.756-07:00Never sign up VPS from this companyRecently I have sign up a VPS from a company call WideVPS, and it is really the worst hosting company that I have ever encounter. For those of you who like an affordable hosting, please be careful with the company:<br />
<br />
<ol>
<li>The VPS is activated after a few hours of waiting. (<i>they claimed it is instant activation</i>)</li>
<li>Support ticket tooks 4 hours to response. (<i>they claimed 1-hour response</i>)</li>
<li>Ticket was closed even the issue has not been resolved. I created a Windows VPS for testing before moving to linux, during the sign up I have key-in a password for the VPS. When it is finally up after 4-hours, the password I entered is not working!! I then open a ticket and email, it tooks 2 days and never resolved! All I get is.... <i>I will send you the info in next email.</i><b><i> Then? I receive no email at all.</i></b></li>
<li>Submitted a PayPal dispute, but they never response to the dispute. (<i>so you can see they are not serious in the business at all</i>)</li>
</ol>
<div>
And this morning I receive their invoice asking me to renew the hosting, but until today I'm not able to use the VPS at all!</div>
<div>
<br /></div>
<div>
Guys and Gals, be careful. I'm glad if you have good experience with them. But if you are still considering, just make sure you contact them before sign up and then judge yourself. I hope you will then not wasting money like I did.</div>
Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-51851096215417882612015-04-22T11:58:00.001-07:002015-04-22T11:58:14.942-07:00Ubuntu Boot to Blank Screen with Blinking Underscore (Cursor)Today I was installing the Ubuntu 14.04.02 LTS into a server using a USB thumbdrive. Everything went smooth, as usual the setup asked to remove the USB thumbdrive before continue to Reboot.<br />
<br />
After reboot, it hangs on a black screen with blinking underscore / cursor. Waited for 15 mins, nothing happen. If you encounter the same error like I do, it is possibly caused by:<br />
<br />
<ol>
<li>a corrupted GRUB</li>
<li>the setup simply installed the GRUB onto the USB thumbdrive accidentally. (I suspect it is because I have chosen to umount the thumbdrive during the setup)</li>
<li>graphics driver not supported (it sounds a bit weird to me, if the setup could run well in GUI, why should a reboot not?)</li>
</ol>
<div>
For the first two reasons, a simple solution is to repair the GRUB. <a href="https://help.ubuntu.com/community/Boot-Repair" target="_blank">Here's the complete guide</a> for Ubuntu users. For my case, because I knew the GRUB is in the thumbdrive, so I simply plug it in and choose my HDD as first boot device, it then boot into Ubuntu successfully, then I run the following command in terminal:</div>
<div>
<pre style="background-color: #f3f3f3; border: 1px dashed rgb(193, 180, 150); color: #333333; font-family: UbuntuMono, courier, monospace; font-size: 13px; line-height: 16px; margin-bottom: 8px; padding: 4pt; vertical-align: baseline; white-space: pre-wrap; word-wrap: break-word;">sudo add-apt-repository ppa:yannubuntu/boot-repair
<span class="anchor" id="line-2" style="border: 0px; font-family: inherit; font-style: inherit; font-weight: inherit; line-height: 1; margin: 0px; padding: 0px; vertical-align: baseline;"></span>sudo apt-get update
<span class="anchor" id="line-3" style="border: 0px; font-family: inherit; font-style: inherit; font-weight: inherit; line-height: 1; margin: 0px; padding: 0px; vertical-align: baseline;"></span>sudo apt-get install -y boot-repair && boot-repair</pre>
</div>
<div>
and then follow what is being instructed by the boot-repair. The only steps that caused a confusion is which disk or partition to select as GRUB install location. A rule of thumbs is don't select the partition, select the disk.</div>
<div>
<br /></div>
<div>
For 3rd reason - graphics driver broken. I personally do not try it, but someone from online said it can be fix by inserting the <b>-nomodeset</b> in between <i><b>ro quiet splash</b>. </i>And I do believe you realize one thing now... if you could see the GRUB and able to insert the <b>-nomodeset</b>, well, then it is most likely your problem is more challenging, good luck hunting it down!</div>
<div>
<br /></div>
Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-11268990742139599132015-04-21T10:06:00.001-07:002015-04-21T10:06:41.806-07:00XFCE4 Desktop Not ShowingSometimes when you login the desktop wallpaper, icons are all missing. It is due to the <i style="font-weight: bold;">xfdesktop </i>not loaded properly. To fix it, simple type <i><b>xfdesktop</b> </i>in terminal, there will have some message appeared but can be safely ignore.Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-43851735329959552882015-01-07T01:20:00.001-08:002015-01-07T01:21:13.242-08:00[Fedora] Fix Yum Update crashed at the middle of updatIf the problem you having is duplicates packages, simply refer to the following info to attempt the fix:<br />
<br />
<pre>sudo yum check all # tells you of any problems
sudo package-cleanup --problems # lists all known package problems
sudo package-cleanup --dupes # lists duplicate packages
sudo package-cleanup --cleandupes # actually cleans up duplicates
sudo yum check all # run again to check for remaining problems
sudo yum-complete-transaction --cleanup-only</pre>
<pre></pre>
<pre><span style="font-family: 'Times New Roman'; white-space: normal;">
</span></pre>
<pre><span style="font-family: 'Times New Roman'; white-space: normal;">Thanks to </span><span style="font-family: Times New Roman;"><span style="white-space: normal;">https://destefano.wordpress.com/2013/08/13/yum-update-fail/#comment-2714</span></span></pre>
Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-38667748814212791592014-12-29T10:08:00.001-08:002014-12-29T10:08:51.171-08:00CIFS failed to allocate memory?If you are mounting your Windows network shares in your Ubuntu, do not hurry to move your files to this newly added mount point. Most probably you will be regret very soon, as the system may give you error <b style="font-style: italic;">Failed to allocate memory </b>and soon after that your files will gone missing. Yes, all gone! That's what happened to me.<br />
<br />
The issues seems to cause by Windows rather than Ubuntu itself. There is a good explanation in this link:<br />
https://wiki.archlinux.org/index.php/Samba/Troubleshooting<br />
<br />
But I will copy & paste some of the content here, in case the link broken in the future.<br />
<br />
======== Copy & Paste from archlinux.org, please contact me if remove is required ========<br />
<h3>
<span class="mw-headline" id="Windows_7_connectivity_problems_-_mount_error.2812.29:_cannot_allocate_memory">Windows 7 connectivity problems - mount error(12): cannot allocate memory</span></h3>
A known Windows 7 bug that causes "mount error(12): cannot allocate
memory" on an otherwise perfect cifs share on the Linux end can be fixed
by setting a few registry keys on the Windows box as follows:
<br />
<ul>
<li><code style="display: inline-block; padding: 0.1em 0.3em;">HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache</code> (set to <code style="display: inline-block; padding: 0.1em 0.3em;">1</code>)
</li>
<li><code style="display: inline-block; padding: 0.1em 0.3em;">HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size</code> (set to <code style="display: inline-block; padding: 0.1em 0.3em;">3</code>)
</li>
</ul>
Alternatively, start Command Prompt in Admin Mode and execute the following:
<br />
<pre>reg add "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v "LargeSystemCache" /t REG_DWORD /d 1 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" /v "Size" /t REG_DWORD /d 3 /f
</pre>
Do one of the following for the settings to take effect:
<br />
<ul>
<li> Restart Windows
</li>
<li> Restart the Server service via services.msc
</li>
<li> From the Command Prompt run: 'net stop lanmanserver' and 'net start
lanmanserver' - The server may automatically restart after stopping it.
</li>
</ul>
<br />
<br />
<br />
<div style="background-color: #ddddff; border: thin solid #BBBBDD; margin: 0.50em 0; overflow: hidden; padding: 5px;">
<strong> Note: </strong>Googling
will reveal another tweak recommending users to add a key modifying the
"IRPStackSize" size. This is incorrect for fixing this issue under
Windows 7. Do not attempt it.</div>
Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-60166869077992655832014-09-07T00:54:00.001-07:002014-09-07T00:54:57.606-07:00How to extend screen to second monitor in Linux / Fedora?Here's the command that could extend the screen to second monitor, in case Linux does not do the job automatically:<br />
<blockquote class="tr_bq">
<b><i>xrandr --output VGA1 --mode 1920x1080 --output eDP1 --mode 1366x768 --left-of VGA1</i></b></blockquote>
Where you need to replace the screen size manually. By running <i style="font-weight: bold;">xrandr</i> in terminal, you could get the screen size range for each display output.<br />
<br />
Beside <i style="font-weight: bold;">--left-of</i>, there are other options such as <i style="font-weight: bold;">--above</i>, <i style="font-weight: bold;">--below</i>, <b><i>--right-of</i></b>Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com1tag:blogger.com,1999:blog-6185289170610624451.post-13338323653080049712014-08-31T06:24:00.002-07:002014-08-31T06:25:31.274-07:00[Alt] key problem when remote desktop Windows via RemminaIf you are using Xfce 4 and encounter the following problems using [Alt]<alt> key inside Microsoft Windows remote desktop session:</alt><br />
<br />
<ul>
<li><alt> [Alt] key does not work as per expected</alt></li>
<li>clicking [Alt]<alt> + mouse middle button move you away from your remote desktop session</alt></li>
</ul>
<div>
then you should try this simple and straight forward trick before going too technical.</div>
<div>
<ul>
<li>Go Settings > Settings Manager > Window Manager Tweaks > Accessibility > <b>"Key used to grab and move windows"</b> > set it to "<b>None</b>"</li>
</ul>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjgqjOtHkTadWBTb_4wOXNCIsRVGpAlTPucpjTq7KuCbm8Mepurbe0rVBHGtF6vrctt9hTq3fSHLQiaZ44ZwmH6BFG-K9D98VeeEGXPrWaZKe_TE9Ws3g7W58iA-XI14bgW_aEnFUW7jJE/s1600/disable_RDP_altKey.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjgqjOtHkTadWBTb_4wOXNCIsRVGpAlTPucpjTq7KuCbm8Mepurbe0rVBHGtF6vrctt9hTq3fSHLQiaZ44ZwmH6BFG-K9D98VeeEGXPrWaZKe_TE9Ws3g7W58iA-XI14bgW_aEnFUW7jJE/s1600/disable_RDP_altKey.png" height="261" width="320" /></a></div>
<div>
<br /></div>
<div>
Voila! Now it should works like charm. Otherwise... you might have to Google around and read about re-map key, etc.. Good luck!</div>
</div>
Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com3tag:blogger.com,1999:blog-6185289170610624451.post-44063151752027875992014-08-19T08:02:00.001-07:002014-08-19T08:02:09.281-07:00Remmina - Unable to connect RDP ServerHave you ever encountered sudden failure to RDP to your Windows desktop using Remmina? There are two known reasons to me:<br />
<br />
<ol>
<li>your RDP plugin for Reminna is missing. In Fedora, type <b>sudo yum install remmina-plugins-rdp</b>, or Ubuntu <b>sudo apt-get install remmina-plugin-rdp</b>. You may require to reboot after install in order to load the RDP plugin. Sometimes <i>Import</i> simply won't work.</li>
<li>your remote desktop's fingerprint has changed. It is impossible to reset the fingerprint within Remmina's interface. What you can do is fire up terminal, go to <b>~/.freerdp/</b> and delete <b>known_hosts</b>.</li>
</ol>
<div>
Now try again and voila! Your remote desktop is back!</div>
Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com2tag:blogger.com,1999:blog-6185289170610624451.post-1286522511384356462014-06-21T17:56:00.001-07:002014-06-21T18:22:12.823-07:00[Fedora] Omit GUI and boot with or into command lineBefore you start, you need to know what is <b>runlevel</b>.<br />
<blockquote class="tr_bq">
<b>runlevel</b> is a number that indicates which mode the
computer to boot into. For instance, runlevel 5 is graphical mode, where
runlevel 3 is text-only mode. Runlevel 1 is single-user mode, commonly used for troubleshooting.
</blockquote>
And GRUB (GRand Unified Bootloader), a bootloader which allow you to choose which OS to boot into during computer start up. Here's a screenshot of GRUB.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi0UrKsoFVzdfta4IT-YKKq9kCVMvz02ceNtphb96IsqBsRa6udOCgWybIDQaQTH33ZJNi8OdzUlzdrr9fMOnPdcP8x2-HADZ0NB07xUvJvu3awZ_owQZJceo6mZDSfNfx-MlZP6nsiXwI/s1600/grub2-fedora.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi0UrKsoFVzdfta4IT-YKKq9kCVMvz02ceNtphb96IsqBsRa6udOCgWybIDQaQTH33ZJNi8OdzUlzdrr9fMOnPdcP8x2-HADZ0NB07xUvJvu3awZ_owQZJceo6mZDSfNfx-MlZP6nsiXwI/s1600/grub2-fedora.png" height="176" width="320" /></a></div>
<br />
Now, there are two options:<br />
<ol>
<li>boot with command line, means omit the filling up Fedora logo and show the boot progress by command line</li>
<li>boot into command line, means completely omit booting into GUI and end up in command line</li>
</ol>
What you need to do is at the GRUB screen, select your Fedora OS name and press "<b>e</b>".<br />
Then find <i><b>rhgb</b> </i>in the line start with <i><b>linuxefi /vmlinuz</b></i>. On the right side of <i><b>rhgb</b> </i>should be word "<i><b>quiet</b></i>".<br />
<br />
<b>For option 1</b>: Remove the <i><b>rhgb</b></i> from the line and press CTRL+X or F10. This should show the command lines as boot progress instead of the Fedora logo. Useful for identifying what has failed during boot progress. The system will still end up in GUI afterwards.<br />
<blockquote class="tr_bq">
Sample = ... <b><strike>rhgb</strike></b> quiet ... </blockquote>
<br />
<b>For option 2</b>: Here's why you have to understand the <b>runlevel</b>. You achieve this by simply add a runlevel number "<b>3</b>" after the word "<i><b>quiet</b></i>" (space in between two words) and press CTRL+X or F10. This should boot the system into CLI instead of GUI.<br />
<blockquote class="tr_bq">
Sample = ... rhgb quiet <b>3</b> ...</blockquote>
<br />
Note:<br />
<ul>
<li><b><i>rhgb</i></b> = RedHat Graphical Boot </li>
</ul>
Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-36005940189090277292014-04-10T06:26:00.000-07:002014-04-10T06:26:19.201-07:00Enable Samba browsing in ThunarIf you enter location path start with <i><b>smb://</b></i> and get a red stop sign, it means you don't have <i><b>gvfs-smb</b> </i>install. Simply fire up your terminal and type:<br />
<blockquote class="tr_bq">
<b>sudo yum install gvfs-smb -y</b></blockquote>
You might want to install <i><b>Gigolo</b> </i>too to manage your network folder.<br />
<blockquote class="tr_bq">
<b>sudo yum install gigolo</b> <b>-y</b></blockquote>
Voila! Your address bar should work with <i><b>smb://</b></i> now. Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-90235489312852565652014-01-16T09:21:00.000-08:002014-01-16T09:21:15.731-08:00Problem connecting XrdpIf the error appeared as "problem connecting" when connecting to remote desktop using <i><b>xrdp</b></i>, it is most likely the remote Linux does not have VNC server installed.<br />
<br />
(1) To verify this, you can type:<br />
<code>sudo tail /var/log/<span class="posthilit">xrdp</span>-sesman.log</code><br />
<br />
(2) If you see the error message below, then it means you don't have VNC server installed.<br />
<code>[ERROR] another Xserver is already active on display xx </code><br />
<br />
(3) To fix this, simply run this command:<br />
<code>sudo apt-get install tightvncserver</code><br />
<br />
(4) After that, restart <i><b>xrdp </b></i>service by running:<br />
<code>sudo service xrdp restart</code><br />
<br />
<u><b>Here's why:</b></u><br />
<span style="font-weight: bold;"><span style="font-style: italic;"><span class="posthilit">xrdp</span></span></span>
is the daemon that handles RDP remote desktop access from Windows
machines to your Linux Mint PC. But it's not enough to install only <span class="posthilit">xrdp</span> - you need a <span style="font-weight: bold;">VNC server</span>. Unfortunately it's not automatically installed with the <span class="posthilit">xrdp</span> package.<br /><br />The error message "error - <span class="posthilit">problem</span> <span class="posthilit">connecting</span>"
after a successful login message isn't very helpful either. Searching
the Internet can drive you in circles - I wasted at least 2 hours on
finding out that I forgot to install the VNC server - ouch.<br />
<br />
Thanks <i><b>powerhouse </b></i>from Linux Mint forum who shared this useful information. Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com2tag:blogger.com,1999:blog-6185289170610624451.post-8537174381953864732013-12-05T03:32:00.001-08:002013-12-05T03:32:18.277-08:00Samba Share Permission in a NutshellIn this post I'm writing all the troubles that I faced when setting up samba shares for Windows and MAC, to help novice users get the samba up and running as quickly as possible. Do note that all the tips & tricks shared here is meant to get things up and running quickly, it might create security hole. Use at your own risk and be sure to research more if you are deploying for high security concern mission.<br />
<br />
<u><b>New created folder or copy & paste into samba shared folder do not follow permission set by smb.conf</b></u><br />
The key settings are the following (e.g. permissions 775) <br />
<ul>
<li>create mask = 0775</li>
<li>force create mode = 0775</li>
<li>security mask = 0775</li>
<li>force security mode = 0775 </li>
</ul>
<ul>
<li>directory mask = 2775</li>
<li>force directory mode = 2775<i> (If you change this to 0755, it won't work. So this parameter is very important)</i></li>
<li>directory security mask = 2775 </li>
<li>force directory security mode = 2775</li>
</ul>
Now, why 2775?<br />
<ul>
<li>2 = the setgid
bit is set (2) which makes newly created directories have the same group ownership as the
parent.</li>
<li>77 = owners and group members of the files have full access to them</li>
<li>5 = everyone else can enter the directories and view the file names (use with caution)</li>
</ul>
To be continue... Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-36559501129831220752013-10-12T19:20:00.003-07:002013-10-12T19:32:00.399-07:00Terminal does not have history and not showing path?What happen when a new user's terminal (xterm, lxterminal etc):<br />
<br />
<ol>
<li>does not display any path (only show $>)</li>
<li>does not support Up key for recall previous command?</li>
</ol>
<div>
It is because the new user is using <b>/bin/sh</b> instead of <b>/bin/bash</b>. To solve this, simply do <i style="font-weight: bold;">sudo chsh</i>, then key in <b>/bin/bash</b> when prompted to choose an option.</div>
<div>
<br /></div>
<div>
Restart the terminal then you should be able to get all the features back.<br />
<br />
The root cause for this is nothing is specified when the user is being created using command line. Be sure to specify to use <b>/bin/bash</b> to avoid this.</div>
Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-80045368544876399502013-08-07T20:52:00.000-07:002013-08-07T20:52:31.964-07:00Fast apt-get with apt-fastEver experience slow download even with 10Mbps++ internet? The author has written a very useful article to share how to speed everything up with apt-fast:<div>
<a href="http://www.webupd8.org/2012/10/speed-up-apt-get-downloads-with-apt.html">http://www.webupd8.org/2012/10/speed-up-apt-get-downloads-with-apt.html</a><br /><div>
<br /></div>
</div>
Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-69751869708165268242013-08-07T08:46:00.001-07:002013-08-07T09:14:04.117-07:00[Linux] file_mode, dir_mode or permission not working correctly in Samba Share or Mount folderUsers permission in Linux is really complicated, for samba share, you need to take care:<br />
<br />
<ol>
<li>the folder permission of the parents folder where your samba share is located (at server side)</li>
<li>the folder permission of the parents folder where your fstab mounted folder is located</li>
<li>the <b>create mask</b> and <b>directory mask</b> in <i><b>/etc/samba/smb.conf</b> </i>on your server</li>
<li>the <b>file_mode</b>, <b>directory_mode</b>, <b>noperm</b>, <b>rw</b> and <b>credentials</b> in your <i><b>/etc/fstab</b> </i>on client PC</li>
</ol>
<div>
General rules are parent folders permission will always overwrite the <i style="font-weight: bold;">smb.conf </i>& <b style="font-style: italic;">fstab</b>. </div>
<div>
<br /></div>
<div>
<b><u>When do I need to check the parents folder permission?</u></b></div>
<div>
<ol>
<li>If you have set everything in both files and still cannot get the correct permission for new created file/directory in your samba shares. <u>Check client PCs mount folder's parent's permission</u></li>
<li>If client PCs has problem access the samba shares, even with the correct username & password entered. <u>Check server samba share parent's folder permission</u></li>
<li>When you need <i style="font-weight: bold;">valid users = xxx, xxx </i>to give access to client PCs. C<u>heck server samba share parent's folder permission</u></li>
</ol>
<div>
<u><b>I have set the samba/fstab/parent folder permission, but I still don't have write permission?</b></u></div>
</div>
<div>
<ol>
<li>you need to add <i style="font-weight: bold;">uid=***your current user name***</i> at the fstab mount option.</li>
</ol>
<div>
<b><u>Known Issue</u></b></div>
</div>
<div>
<ol>
<li>When creating file/directory in the mount folder (using Ubuntu 12.10), it does not honor the <b>create mask </b>& <b>directory mask </b>set by the server's <b style="font-style: italic;">smb.conf</b>. I'm still looking for a solution... appreciate if anyone can help.</li>
</ol>
</div>
<div>
<b><u><br /></u></b></div>
Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-76610845716694917672013-08-03T01:09:00.002-07:002013-08-03T01:09:27.896-07:00[Ubuntu] Can access samba network share by IP but not Netbios name from WindowsAfter whole long day of troubleshooting why we cannot resolve samba shared folders using the NetBIOS Name defined in <i>smb.conf</i><b style="font-style: italic;">.. </b>finally I have figured out the root of the problem:<blockquote class="tr_bq">
Hostname <b>CANNOT equal to </b>NetBIOS name!!!</blockquote>
A bit of background...<br />
<br />
<ol>
<li>our server hostname is <b>server</b>1</li>
<li>our NetBIOS name is <b>server1</b> (defined in <i>smb.conf</i>)</li>
<li>IP-address is 10.0.0.2</li>
</ol>
<br />
From Windows 7 / OSX we can access the samba shares using <i>\\10.0.0.2\share</i>, as well as <i>\\server1.local\share</i> (the .local is a result of running <i>avahi-daemon</i>). We can also <i>ping</i> <i>10.0.0.2</i><b style="font-style: italic;"> </b>or<b style="font-style: italic;"> </b><i>server1 </i>or <i>server1.local</i>, but we simply cannot access with <i>\\server1\share</i><br />
<i><br /></i>
By changing the Hostname in <i style="font-weight: bold;">/etc/hosts </i>& <i style="font-weight: bold;">/etc/hostname</i> to any name other than "server1", or change the NetBIOS name in <b style="font-style: italic;">smb.conf</b> to any other name, we can now get it work.<br />
<br />
This is rather weird for a Windows user like me, where only hostname need to be set and we can access directly from other PC in the network without bothering what is NetBIOS. Linux is indeed too tricky!<br />
<br />
Anyway, kind of fun when able to figure out what's wrong. It makes me love and hate Linux at the same moment!Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-78435799059822864002013-08-03T00:12:00.000-07:002013-08-03T00:12:04.131-07:00[Ubuntu] Can ping internet IP address but cannot resolve web addressIf you got error when trying to ping any web address e.g. www.google.com, but can ping its IP address, there could be something wrong with the <b>resolv.conf</b>.<br />
<br />
Despite you could have set the <b>dns-nameservers </b>in <b>/etc/network/interfaces</b>, the <b>resolv.conf</b> may not be updated yet. And if you have some running process and could not do <b>ifdown / ifup</b>, you can do <b>nano /etc/resolv.conf</b>, comment the original <i>nameserver 127.0.0.1 </i>to <i><b>nameserver 8.8.8.8</b> </i>(or the DNS provided by your ISP).<br />
<br />
Ubuntu should now resolve the web address correctly!Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-459276779402051552013-07-31T01:24:00.001-07:002013-07-31T01:24:23.136-07:00How to solve chmod doesn't work on mounted folderWhen <i><b>chmod</b></i> does not have any effect on mounted folder, it could be wrong filesystem flag being used:<br />
<ul>
<li>try <i><b>umount</b> </i>the folder first</li>
<li>if you mount folder is a HDD, check its filesystem type by <i><b>fdisk -l</b></i></li>
<li>if it is a NTFS, use the following in fstab :</li>
<ul>
<li> /dev/sda1 /mnt/<i>folder</i> ntfs-3g rwx,uid=xe4,iocharset=utf8,umask=000 0 0</li>
</ul>
<li> then <i><b>mount -a</b></i></li>
</ul>
Then the <i><b>chmod </b></i>should work now.Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0tag:blogger.com,1999:blog-6185289170610624451.post-36133010724138928202013-07-30T09:45:00.001-07:002013-07-30T09:45:41.333-07:00Damn you, buggy Samba 3.6.3I have been finding solution to address a samba sharing (Ubuntu 12.04.2 LTS) for few days, the errors that I faced:<br />
<br />
<ol>
<li>windows 7 cannot access share</li>
<li>windows 7 keep asking password to access samba share</li>
<li>windows 7 computer on other VLAN cannot browse the Ubuntu server with Windows Explorer</li>
<li>troubleshoot using smbclient -L localhost -U% give errors such as:<br />- tree connect failed, NT_STATUS_CONNECTION_INVALID</li>
</ol>
<div>
And very very luckily... I found a discussion & an article which discussed about the bug found in Samba 3.6.3, and suggest to upgrade to 3.6.7:</div>
<div>
<a href="http://unix.stackexchange.com/questions/55534/samba-server-3-6-3-crashes-on-simple-setup-on-linux-mint-13">http://unix.stackexchange.com/questions/55534/samba-server-3-6-3-crashes-on-simple-setup-on-linux-mint-13</a></div>
<div>
<a href="https://www.monlore.nl/blog/?p=226">https://www.monlore.nl/blog/?p=226</a> (Marcel's blog)</div>
<div>
<br /></div>
<div>
Thanks god their suggestion work.. and damn Ubuntu & Samba, how could they release such a buggy version for LTS and do not issue immediate upgrade in the official repository?!!</div>
<div>
<br /></div>
<div>
Alright, here's the solution copy from Marcel's blog:</div>
<div>
<ul>
<li>sudo add-apt-repository ppa:nathan-renniewaldock/ppa</li>
<li>apt-get update</li>
<li>apt-get install samba</li>
</ul>
<div>
Voila! Now Samba works like a charm!</div>
</div>
Tecsun Yeephttp://www.blogger.com/profile/07182904194406343604noreply@blogger.com0