Re: FAT drive on Disk 1 port appears twice (Unslung 6.8 beta)
- Hi Mike,
You are absolutely right. It is due to /etc/win_share.info not being
clean at boot time. This is caused by myself doing a reboot in ssh
session. When duplicate HDD_1_1_1 happens, /etc/win_share.info
actually contain two identical lines for HDD_1_1_1. If I do it
properly (i.e., use Restart Now in LinkSys GUI or even disconnect the
USB connector before rebooting), the duplicate HDD_1_1_1 won't occur.
By the way, when an unclean /etc/win_share.info file exists at boot
time, the result is unpredictable. Sometime no HDD_1_1_1 is mounted
(/var/log/messages shows disk error). I am 99% sure the problem of not
being able to use ssh is related to the duplicate HDD_1_1_1/unclean
win_share.info file problem.
I added a line to remove /etc/win_share.info in /etc/rc.d/rc.sysinit
as you suggested. Everything seems to be doing fine now.
--- In firstname.lastname@example.org, "Mike \(mwester\)" <mwester@...>
> a) remove FAT drive
> b) delete /etc/win_share.info
> c) reboot
> See if that cures the duplicate HD_ entries problem. Note that
> does not empty or delete that file at reboot, so if the problemcomes back
> regularly, you might need to add the line to delete that file to themiddle
> of /etc/rc/rc.sysinit.device
> As for the rest, more information would be helpful. Telnet into the
> when SSH is not responding, and check to see what if the sshd isrunning.
> Also check the log files in /var/log for any error messages or such,along
> with the output from dmesg. Something there might offer a clue.(Unslung 6.8
> Mike (mwester)
> ----- Original Message -----
> From: "seeocean_2000" <seeocean_2000@...>
> To: <email@example.com>
> Sent: Monday, July 16, 2007 10:30 AM
> Subject: [nslu2-linux] FAT drive on Disk 1 port appears twice
> Hi all,
> I have an FAT drive (in a 3rd party - read "cheap" - USB enclosure)
> which I want to attach to my slug running Unslung 6.8 beta (from a flash
> drive attached to Disk2 port). Since I use "Chinese Simplified CP936"
> character set setting in the Linksys GUI's System set up, FAT/NTFS
> drives are not supported by the default unslung 6.8 beta, so I followed
> this nslu2-linux wiki
> <http://www.nslu2-linux.org/wiki/Unslung/UnslungLanguageSupport> page
> and installed Kernel module for nls_cp936, and added /unslung/rc.modules
> script to load nls_cp936 at boot time as sugguested in the above wiki
> Now here is what I am seeing:
> 1) If I boot the slug, and then plug the FAT drive in Disk1 port, then
> all is well. I can see the drive, use it as expected.
> 2) If I boot the slug with the FAT drive ATTACHED, then things are kinda
> screwed up: my thttpd still works, but both the LinkSys GUI and LinkSys
> "Safe Drive Removal" utility on Windows show TWO, yes, 2, HDD_1_1_1_1
> drives that corresponds to the FAT drive. The LinkSys GUI shows 2
> "HDD_1_1_1_1" under "Disk 1 Shared Public Data", but I cannot browse the
> directory in either. And sshd won't respond to my connection request
> either, Even after I use "Safe Drive Removal" tool to remove the 2
> copies of FAT drive, ssh still doesn't work. I have to reboot.
> What I can tell is that, the kernel module nls_cp936 is loaded correctly
> (I can see it in /proc/modules), or case 1) above won't happen.
> Does anyone have any suggestions what might be wrong, or where I should
> look? Thanks for any suggestions.