**** BEGIN LOGGING AT Fri Jul 14 02:59:57 2006 Jul 14 03:01:37 ahh.... did the de-underclock mode, and now gentoo won't load from the usb drive? wtf? Jul 14 10:48:00 npt: If you look at the deunderclocking page on the wiki, there are some other reports like that. Jul 14 10:48:28 I expect it's a matter of the power supply not taking the additional load. Jul 14 16:29:25 I'm about to flash my slug for the first time. I've read the Unslung-6.8-beta-README.txt carefully and I have demonstrated that I can get the redboot prompt. I'm not sure I undertand everything about port1 vs. port2 but I hope that will become more clear later. Anyone have any last words for me? Jul 14 16:29:49 And yes, I have my disks unplugged from the slug. Jul 14 17:03:59 Hi Jul 14 17:11:06 Hi.... Jul 14 17:12:48 Anybody whos actually active in this channel? Jul 14 17:16:31 * theorbtwo has been wondering that for some time. Jul 14 17:17:01 Well theorbtwo... Are you able to help me a little? Jul 14 17:17:09 I doubt it. Jul 14 17:17:18 I certianly can't, however, if you don't ask your question. Jul 14 17:17:43 I don't know how to telnet into my nslu2 Jul 14 17:18:22 I've tried after some tutorials, but the path i have to use doesn't seem to work Jul 14 17:19:46 Could you be more specific? Jul 14 17:20:37 I can try ;) Jul 14 17:22:17 Do you have a linux box, other then the nlsu2, handy? Jul 14 17:22:48 The tutorials tells me to connect to http://192.168.1.77/Managment/telnet.cgi but the file doesn't exists?!? Jul 14 17:23:09 And no... I only have the nslu2 which is running linux Jul 14 17:23:43 What firmware are you running? Jul 14 17:24:07 2 secs Jul 14 17:24:18 Current Firmware Version: V2.3R63 Jul 14 17:24:26 Ah. Jul 14 17:24:37 In that case, there seems to be a vastly easier method, and the old methods won't work. Jul 14 17:25:00 Okay... How should i do it then? Jul 14 17:26:43 Hm, perhaps not so easy. Jul 14 17:26:47 http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoLinksysR29 Jul 14 17:26:52 Okay :( Jul 14 17:27:01 Note that I don't actually own a slug yet, I'm just considering it. Jul 14 17:27:11 Okay :P Jul 14 17:27:44 It's a nice little box!! I just wanted some more out of it now Jul 14 17:28:15 I'm not even considering it's designed purpose; I'm looking for an in-car computer. Jul 14 17:29:28 okay, well then i don't know if the nslu2 is useable for that Jul 14 17:30:04 And I think i have to forget to ever telnet into it :S Jul 14 17:31:30 But I will sign out... Thanks for the help... Or that you tried to help me ;) Jul 14 17:31:37 Have you tried the howto I linked to? Jul 14 17:31:48 Yes Jul 14 17:32:27 ...where'd you get lost, I'd ask, were you still here... Jul 14 17:46:27 I just flashed my slug and now I have a telnet connection. Jul 14 17:47:18 the readme says "Check the web interface to make sure that the disk has been recognized by the Linksys software." Jul 14 17:47:27 It does not seem to be recognizing my disk. Jul 14 17:52:38 Is there anyone that can help me? Jul 14 17:53:48 but the nslu recognized your disc before? Jul 14 17:54:13 Yes. When I'm not running telnet it seems to display the contents of my disk. Jul 14 17:54:45 I used NSLU2 to format my disk previously and I'm also wondering if I need to format it again to unsling it. Jul 14 17:55:55 it says it is not formatted. Jul 14 17:56:48 this happens when you boot with the disk attached or without, or in both cases? Jul 14 18:00:19 Odd. I just refreshed my browser after plugging in a second disk and now they both appear as FORMAT (EXT3). I had gone to and from this page several times previously and the "FORMAT(EXT3)" had not shown up. Maybe my browser was caching the page? Jul 14 18:00:57 Can you help me understand whether I want to unsling to disk1 or disk2? I've read the explanations several times now. Jul 14 18:01:05 this is possible Jul 14 18:01:45 that depends... do you use a device which is ntfs formatted? Jul 14 18:03:06 I have two new disks. My slug has foramtted both of them. I think it formated them as FAT32. I would like to have a dual partition with NTFS and EXT3 eventually. Jul 14 18:05:01 assuming that you have flashed unslung-6.8, you should unsling to the disk which is attached to port2, and is ext3 formatted, so you could use the "ntfs" disk on port1.. Jul 14 18:07:16 Can I unsling multiple times? Jul 14 18:07:39 In case I get it wrong the first time? Jul 14 18:15:04 It says: "Error: /share/flash/data (disk2, /dev/sda1) is not a mounted disk" Jul 14 21:01:36 Hi there, I could use a little help with the installation of Unslung on my NSLU2... Jul 14 21:04:23 did you read this? http://www.nslu2-linux.org/wiki/Unslung/HomePage Jul 14 21:05:31 Yes... And my problem isn't actually to install it, as i have allready done that... But I can't unsling Jul 14 21:07:12 sorry, can't hel you there. Jul 14 21:07:43 but i can't unsling... means what, in detail? Jul 14 21:09:24 I send the command # /sbin/unsling disk1 -nopw in the telnet-thingy and then it just comes with an error about the disk isn't mountet... But I've followed the readme, slavish step by step Jul 14 21:11:35 so your external storage (disk/usb stick?) would mounted before (with linksys fw)? Jul 14 21:12:35 Yes, it did work before I installed the Unslung firmware Jul 14 21:15:15 well, now you flashed unslung-6.8, reboot the slug, plugged in the disk (?) and wait some minutes (depends on the size of the disk), enable the telnetd and log in, use the mount command (to make sure, that your storage is mounted read/write) and then use the /sbin/unsling command ? Jul 14 21:15:48 Yes, exactly Jul 14 21:17:53 what kind of external storage you would use ? and with which size ? Jul 14 21:18:17 A usb2.0 harddisk at 250GB Jul 14 21:20:05 k, that would be take around 10 minutes, after plug in, before the disk is mounted read/write, so you should wait period, before you verify (with the mount command) that the disk is mounted rw Jul 14 21:21:54 Okay, I'll try that... Thx Jul 14 21:32:34 Hmm, still got a problem... Jul 14 21:32:46 USB Port 1: Ready, 6MB (3% Free) Jul 14 21:33:17 And I have waitet a little longer than 10 minutes Jul 14 21:34:05 this is your disk, which is attached on port1 ? Jul 14 21:34:12 Yes Jul 14 21:34:39 When it is pluged in during boot it says that all the 250gb is present Jul 14 21:34:51 when you telnet in, what is the output of the mount command? Jul 14 21:35:13 Error: /share/hdd/data (disk1, /dev/sdb1) is not a mounted disk Jul 14 21:41:05 When logged into the device, instead of the "unsling" command, what ouput do you get when you type the command: "mount"? Jul 14 21:41:50 morning, mwester Jul 14 21:41:53 . /dev/mtdblock4 on / type jffs2 (rw) Jul 14 21:42:03 . /proc on /proc type proc (rw) Jul 14 21:42:12 usbdevfs on /proc/bus/usb type usbdevfs (rw) Jul 14 21:42:19 . /dev/mtdblock4 on /dev.state type jffs2 (rw) Jul 14 21:42:26 ramfs on /dev type ramfs (rw) Jul 14 21:42:35 . /dev/mtdblock4 on /var.state type jffs2 (rw) Jul 14 21:42:42 ramfs on /var type ramfs (rw) Jul 14 21:42:49 none on /tmp type ramfs (rw) Jul 14 21:43:10 Without the dots at the begining Jul 14 21:43:25 hm.. Jul 14 21:44:05 Is this bad? Don't know what it means... Jul 14 21:44:08 Ok. That means that the device did not mount the disk. Either it did not recognize it as a "mountable" disk at all, or it recognized it but found some error when it attempted to automatically mount it. Jul 14 21:44:42 :( Jul 14 21:44:45 Was the device originally formatted by the NSLU2? Jul 14 21:44:53 Yes Jul 14 21:45:31 And it does work when i boot with the HD attached to the NSLU2 Jul 14 21:47:17 What port is the disk plugged into, and what type of disk is it? Jul 14 21:48:42 A usb2.0 harddisk at 250GB Jul 14 21:48:52 It is plugged into port 1 Jul 14 21:50:07 What is the output from the command "fdisk -l /dev/sdb" ? Jul 14 21:51:11 isk /dev/sdb: 255 heads, 63 sectors, 30401 cylinders Jul 14 21:51:20 Units = cylinders of 16065 * 512 bytes Jul 14 21:51:36 Device Boot Start End Blocks Id System Jul 14 21:51:47 . /dev/sdb1 1 30371 243955026 83 Linux Jul 14 21:51:56 . /dev/sdb2 30372 30386 120487+ 83 Linux Jul 14 21:52:09 . /dev/sdb3 30387 30401 120487+ 82 Linux swap Jul 14 21:52:50 Ok. Let's mount it manually. Jul 14 21:53:12 okay Jul 14 21:53:23 How do i do that, then? Jul 14 21:53:36 mount /dev/sdb1 /share/hdd/data Jul 14 21:53:46 and let us know what it says... Jul 14 21:54:23 Nothing happens Jul 14 21:55:02 ??? Jul 14 21:55:05 Ok Jul 14 21:55:15 Try "mount /dev/sda1 /share/hdd/data" Jul 14 21:55:26 With the "? Jul 14 21:55:36 No, no quotes Jul 14 21:55:49 okay Jul 14 21:56:13 mount: Mounting /dev/sda1 on /share/hdd/data failed: No such device or address Jul 14 21:57:02 Ok. Well then I guess the first form mounted without any warnings or errors. That's good, but not what I expected. Let's mount the second partition: Jul 14 21:57:12 mount /dev/sdb2 /share/hdd/conf Jul 14 21:57:50 USB Port 1: Ready, 234497MB (100% Free) Jul 14 21:58:03 Do i still need to mount the second partition? Jul 14 21:58:07 Yes. Jul 14 21:58:10 Okay Jul 14 21:58:36 Done Jul 14 21:58:41 No messages? Jul 14 21:58:46 nope Jul 14 21:59:17 a successful mount hould results in a zero output.. Jul 14 21:59:22 Ok, let's verify, what is the output from: Jul 14 21:59:24 df -k Jul 14 21:59:50 Filesystem 1k-blocks Used Available Use% Mounted on Jul 14 22:00:02 rootfs 6528 6332 196 97% / Jul 14 22:00:13 . /dev/mtdblock4 6528 6332 196 97% / Jul 14 22:00:20 . /dev/mtdblock4 6528 6332 196 97% /dev.state Jul 14 22:00:27 . /dev/mtdblock4 6528 6332 196 97% /var.state Jul 14 22:00:40 . /dev/sdb1 240125792 526000 237160244 0% /share/hdd/data Jul 14 22:00:47 . /dev/sdb2 116661 4150 111307 4% /share/hdd/conf Jul 14 22:00:53 That's all Jul 14 22:02:28 Ok. There's nothing wrong with the filesystem integrity or the drive. Usually if the *content* of the partitions is "funny", the Linksys code will call the disk "unformatted" (and not show it as "6MB" in size -- that's the flash memory size). Jul 14 22:03:02 Okay... So I am able to Unsling now? Jul 14 22:03:06 Which implies that there's some other problem -- perhaps timing -- that is preventing the device from mounted. Jul 14 22:03:10 No do not Unsling now Jul 14 22:03:16 okay Jul 14 22:03:37 But the webinterface has changed from: Jul 14 22:03:48 USB Port 1: Ready, 6MB (3% Free) Jul 14 22:03:49 to Jul 14 22:03:51 USB Port 1: Ready, 234497MB (100% Free) Jul 14 22:04:05 Yes, the web interface is now correct, but Jul 14 22:04:12 it didn't mount the disk on its own. Jul 14 22:04:22 Yes? Jul 14 22:04:45 Before we unsling, we need some assurance that the device can mount the disk without a great deal of manual effort each time you start it, no? Jul 14 22:05:31 some hanging usb_detect.pid's ? Jul 14 22:05:42 Yes... But before, while I had Unslung installed, it could use the HD if i just booted while it was plugged in Jul 14 22:05:57 Let's shut the device down, unplug the disk, boot it back up, telnet back in, and try some diagnostics (caplink811-log has a good suggestion) Jul 14 22:06:37 Okay, I'll try Jul 14 22:06:47 vipen, it might work -- if you wish to do it that way, you can unsling. But unless one knows why it isn't working right, who can tell what other problems might be encountered? Jul 14 22:07:13 Yes, you're right... I'll do what you told me Jul 14 22:07:20 BTW, this is Unslung 6.8, right? Jul 14 22:07:24 Yes Jul 14 22:10:27 Hmm, it takes some time for the NSLU2 to boot... Never mind, it just beeped Jul 14 22:11:36 Now I've telneted back in Jul 14 22:14:19 How do i run the diagnostics? Jul 14 22:16:04 Run the "dmesg" command, and note the last several lines (we're actually interested in what lines get *added* after we plug in the drive, so we need to make sure we can find which lines are the new ones) Jul 14 22:17:16 Wow, it prints alot of stuff Jul 14 22:17:35 Yeah - the record of everything that was done as the kernel booted up. Jul 14 22:17:46 Okay Jul 14 22:17:57 Now lets change to the /var/run directory, and list the contents: Jul 14 22:17:59 cd /var/run Jul 14 22:18:01 ls Jul 14 22:18:38 do_umount.pid onetouch_det.pid power_button.pid reset_button.pid thttpd.pid Jul 14 22:18:45 upnpd.pid usb_det.pid Jul 14 22:18:56 cat usb_det.pid Jul 14 22:19:25 476 Jul 14 22:19:35 ps -ef | grep USB Jul 14 22:20:00 473 root 1900 S /usr/sbin/USB_Detect Jul 14 22:20:05 476 root 1900 S /usr/sbin/USB_Detect Jul 14 22:20:12 575 ttyp0 root 2668 S grep USB Jul 14 22:20:15 That's all Jul 14 22:21:00 Is this a break in your conversation where I may ask a question? Jul 14 22:21:22 Sure; I need to check something quickly anyway :) Jul 14 22:21:56 Thanks: I'm trying to unsling my slug for the first time. Jul 14 22:22:00 The read me says: Jul 14 22:22:25 If the disk has not been previously formatted on the NSLU2 then now is is the time to do that. Jul 14 22:22:28 Waht does this mean? Jul 14 22:22:38 I already formated it thru the web interface. Jul 14 22:22:59 Has the NSLU2 formatted your disk, the first time you plugged it in? Jul 14 22:23:11 so its formatted and its ready to go Jul 14 22:23:29 Yeah. It said FORMAT(EXT3). Jul 14 22:23:51 When I try to unsling it via telnet it says: Error: /share/flash/data (disk2, /dev/sda1) is not a mounted disk Jul 14 22:24:03 LOL, it's the same error i get Jul 14 22:24:16 Which we are trying to solve Jul 14 22:24:21 hm Jul 14 22:24:37 try port 2 Jul 14 22:24:45 and unsling to there Jul 14 22:24:53 I am on port 2 already. Jul 14 22:24:57 oh Jul 14 22:25:07 And I try to unsling on port 1 Jul 14 22:25:46 mwester has located the error to be that the disk is not automatically mounted Jul 14 22:25:56 hm Jul 14 22:26:03 As it did work when he guided me to mount it manually Jul 14 22:26:28 Is there a unix mount command we need to issue from the telnet prompt? Jul 14 22:27:16 I was hoping a "fdisk -l" would work. Jul 14 22:27:28 Yes, I have it earlier in this conversation... 2 secs, and i will find it Jul 14 22:27:40 But it is the commands to mount on port 1 Jul 14 22:28:00 I was going try a unix mount command but I don't know the available devices. Jul 14 22:28:03 mount /dev/sdb1 /share/hdd/data Jul 14 22:28:24 Shall I try mount/dev/sdb2 /share/hdd/data ? Jul 14 22:28:33 mount /dev/sdb2 /share/hdd/conf Jul 14 22:28:46 Well, don't know Jul 14 22:29:10 hmmm... no such device or address... Jul 14 22:29:26 But it was the 2 commands i used to mount Jul 14 22:30:12 The device you use depends on the port into which you plug the drive. As the wiki explains, USB port 2 is usually preferred, and corresponds to /dev/sda devices. Jul 14 22:30:56 Since I want to use NTFS I want port 2. Jul 14 22:31:05 Hi again mwester Jul 14 22:31:45 :) I think you mean "Since you *NEED* to use NTFS..." -- you'll find ntfs on the NSLU2 to be "flakey" as the Linksys driver has some problems under laod. Jul 14 22:31:51 s/laod/load/ Jul 14 22:31:51 mwester meant: :) I think you mean "Since you *NEED* to use NTFS..." -- you'll find ntfs on the NSLU2 to be "flakey" as the Linksys driver has some problems under load. Jul 14 22:32:34 Oh... Jul 14 22:32:49 siegfried - what type and size of disk are you attempting to unsling to? Jul 14 22:33:02 Seagate 300GB. Jul 14 22:33:02 s/laod/load/? Do you mead s/load/load? Jul 14 22:33:44 vipen: editor command to have "capbot" correct the typo in my previous post. Jul 14 22:33:56 Can UnSlung serve an NFS disk thru samba to get around that flakeyness? Jul 14 22:34:14 Never tried such a thing... Jul 14 22:34:25 ahh Jul 14 22:34:31 My command "mount /dev/sda1 /share/hdd/data" did not produce an error! Jul 14 22:34:56 siegfried: when you plug your drive in, what does the web interface report about the status of the disks (before you manually mounted the disk just now)? Jul 14 22:36:17 Can i proceed? Or do we wait for siegfried? Jul 14 22:36:39 Hmm... It says "USB port 2: Type: Not Foramted Free Space". I proceeded anyway because I had previosly seen it display FORMAT(EXT3). Jul 14 22:37:19 Ok. This problem has been reported previously; the common theme seems to be very large drives. Jul 14 22:37:53 I'm trying the /sbin/unsling disk2 again. Jul 14 22:38:51 vipen: you printed out the contents of the .pid file -- that file is a lock, and the digits would be process number of the USB disk detection process (Linksys software). The "ps" command you executed verified that the process does exist, and matches the number in the file. All is well there, too. Jul 14 22:39:22 Okay... Jul 14 22:39:43 We can try some experimenting, but let's just limit it to this: Can you plug the drive into USB Port 1 or 2 (whichever you have selected)... Jul 14 22:39:46 Do I get it right, it's just the auto-mount thing that doesn't work? Jul 14 22:40:05 Yes Jul 14 22:40:07 Yep, the automount is failing. In mid-mount. Strange. Jul 14 22:40:30 The HD is turned on now Jul 14 22:40:48 Type "dmesg" again, and if you can cut and paste in the lines that are added, that would be useful info. Jul 14 22:40:49 my "/sbin/unsling disk2" failed with the same error. Jul 14 22:40:56 okay Jul 14 22:41:16 siegfried: yes, you don't have both partitions mounted manually. Hold tight a moment. Jul 14 22:42:21 wait Jul 14 22:42:37 Huh? It wasn't what i copied Jul 14 22:42:49 Strange. Jul 14 22:43:10 read capacity ok!!! Jul 14 22:43:16 The capacity is 488397168 Jul 14 22:43:23 *** 49 Jul 14 22:43:29 Vendor: SAMSUNG Model: SP2514N Rev: VF10 Jul 14 22:43:38 Type: Direct-Access ANSI SCSI revision: 02 Jul 14 22:43:48 Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0 Jul 14 22:43:56 SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB) Jul 14 22:44:06 31 port connect!!!!! Jul 14 22:44:12 Partition check: Jul 14 22:44:19 . /dev/scsi/host1/bus0/target0/lun0: p1 p2 p3 Jul 14 22:44:26 WARNING: USB Mass Storage data integrity not assured Jul 14 22:44:33 USB Mass Storage device found at 2 Jul 14 22:44:42 kjournald starting. Commit interval 5 seconds Jul 14 22:44:48 so far so good... Jul 14 22:44:53 EXT3-fs warning: maximal mount count reached, running e2fsck is recommended Jul 14 22:45:07 EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,17), internal journal Jul 14 22:45:15 EXT3-fs: mounted filesystem with ordered data mode. Jul 14 22:45:23 kjournald starting. Commit interval 5 seconds Jul 14 22:45:29 I'm holding tight... I accidently cycled the power on my drive and then refresed my browser display. It now sees the drive. Jul 14 22:45:37 XT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,18), internal journal Jul 14 22:45:56 EXT3-fs: recovery complete. Jul 14 22:46:06 EXT3-fs: mounted filesystem with ordered data mode. Jul 14 22:46:14 Adding Swap: 120480k swap-space (priority -1) Jul 14 22:46:23 EXT3-fs warning: maximal mount count reached, running e2fsck is recommended Jul 14 22:46:31 EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,17), internal journal Jul 14 22:46:35 And that's all Jul 14 22:47:51 Ok. The only thing there is that it wants you to run the file-system check program, but for no reason other than you've mounted the disk enough times that it thinks a check would be wise. That won't prevent it from mounting the disk, it'll just complain about it. Jul 14 22:48:23 Okay... Jul 14 22:49:04 I've suspected that this might be a timing problem related to large disks and the Linksys software. Probably not much more we can do to diagnose right now; let's get the disk mounted correctly and unsling to it. Jul 14 22:49:28 Okay Jul 14 22:50:07 Let's restart the NSLU2 to begin, and telnet in as the root user once again. Then plug in the drive, and let me know when it's ready after that. Jul 14 22:50:39 siegfried -- these are probably the same steps you'll need to be doing Jul 14 22:50:54 Hmm, I'll just manually mounted the disk Jul 14 22:51:02 Shall I reboot anyways? Jul 14 22:51:18 I'm trying to decipher them. where do I start? Jul 14 22:52:46 Well, i haven't done anything, so is it necessary to reboot? Jul 14 22:52:53 It takes a long time Jul 14 22:53:22 vipen: what command did you start with to mount the partitions? Jul 14 22:53:24 I was suggesting we start afresh with a reboot of the NSLU2 just to make sure the system is in a consistent state. We can skip that, but issue the "mount" command again. Jul 14 22:53:51 I have issued both the mountcommands I used before Jul 14 22:53:54 and let's see where the disk is currently mounted: those would be the two lines referencing "/dev/sd" Jul 14 22:54:14 siegfried: what port are you unslinging too? Jul 14 22:54:31 2 Jul 14 22:54:51 Ok, then you would probably need to use the following command: Jul 14 22:55:17 mount /dev/sda2 /share/flash/conf Jul 14 22:55:31 I think you already mounted /dev/sda1 Jul 14 22:55:45 then just type: Jul 14 22:55:47 mount Jul 14 22:56:33 and let me know what the mount command has to say about /dev/sda (should be two lines with that text in them) Jul 14 22:57:14 Shall I just try to unsling now? Jul 14 22:57:22 argh... Jul 14 22:57:48 How do I paste multiple lines? Jul 14 22:57:59 You can't Jul 14 22:58:08 Just take one line at a time Jul 14 22:58:10 One at a time is best or the IRC system will boot you off! Jul 14 22:59:20 # mount Jul 14 22:59:54 Oh shucks. Jul 14 23:00:03 It is interpreting the slash. Jul 14 23:00:22 put a space or a period first... Jul 14 23:00:29 Space won't work Jul 14 23:00:35 I've tried... Jul 14 23:00:56 .# mount Jul 14 23:01:03 ./dev/mtdblock4 on / type jffs2 (rw) Jul 14 23:01:09 ./proc on /proc type proc (rw) Jul 14 23:01:17 .usbdevfs on /proc/bus/usb type usbdevfs (rw) Jul 14 23:01:22 ./dev/mtdblock4 on /dev.state type jffs2 (rw) Jul 14 23:01:28 .ramfs on /dev type ramfs (rw) Jul 14 23:01:33 ./dev/mtdblock4 on /var.state type jffs2 (rw) Jul 14 23:01:39 .ramfs on /var type ramfs (rw) Jul 14 23:01:45 none on /tmp type ramfs (rw) Jul 14 23:01:52 ./dev/sda1 on /share/hdd/data type ext3 (rw) Jul 14 23:02:02 ./dev/sda1 on /share/flash/data type ext3 (rw) Jul 14 23:02:06 Now I have unslung the disk, and it mounts fine :D Jul 14 23:02:12 ./dev/sda2 on /share/flash/conf type ext3 (rw,sync) Jul 14 23:02:12 done. Jul 14 23:02:32 I guess that means there is hope for me :) Jul 14 23:02:58 Ok, that matches. You should be ok to run the "unsling" command now -- try it and see if it stops complaining about the disk! Jul 14 23:03:42 But all I have done is the "mount" command. Did that fix something? Jul 14 23:04:36 Oh, something is happening! Jul 14 23:04:41 New password! Jul 14 23:04:44 No. it just got around the fact that the disk was not automatically mounted when hot-plugged. Since you can't do that when Unslung anyway, it's a problem that you should be able to ignore Jul 14 23:05:19 It's working then. Follow the instructiosns; it should be fine. Jul 14 23:06:09 Hmm, now my password to the root/telnet doesn't work Jul 14 23:06:14 I really wish I had a better way to figure out what's happening when this occurs. Of course, it works fine for me because I don't have a 250GB or bigger drive on my development slug! Jul 14 23:06:39 vipen: your password should be what you set when you did the unsling. Jul 14 23:06:48 So did this command do the trick: "mount /dev/sda1 /share/hdd/data" Jul 14 23:06:50 ? Jul 14 23:07:00 I used the -nopw so I didn't have to change... Jul 14 23:07:26 vipen: that left the password on your hard drive unchanged. Unchanged from what it was when Linksys set it. Jul 14 23:07:35 We don't know the Linksys password. Jul 14 23:07:42 Argh Jul 14 23:07:51 Argh indeed. Jul 14 23:08:00 Thougt that I still could use uNSLUng Jul 14 23:08:22 (I thought the README was pretty clear on that, but perhaps it needs more emphasis ;) Jul 14 23:09:04 vipen: Shut down the NSLU2, disconnect the drive, reboot without the drive. Jul 14 23:09:04 Well, maybe I just didn't understand that part clearly... But I thougt so Jul 14 23:09:42 So now the readme says to reboot. I guess I do that? What did I just accomplish? I copied all the stuff to the hard disk so now I have more room to install packages? Jul 14 23:11:42 siegfried: yes - reboot. And yes, that's exactly what you did: the original "mini-load" on the 6MB flash memory is now copied to the hard drive, and when it reboots, the drive will be detected, the boot will see that the OS files exist there, and it will switch to run from the disk instead of the flash. Once that's done, you have a system that is behaving more like a normal Linux system,... Jul 14 23:11:43 ...with room for packages. Jul 14 23:12:37 OKay, it is booted now Jul 14 23:12:55 Ok. Plug in the drive... Jul 14 23:13:16 Oopps, I booted with a drive in. Jul 14 23:13:20 Was that wrong? Jul 14 23:13:43 The drive is turned on Jul 14 23:14:21 I guess I to the web page first and enable telnet first, right? Then plug in the drive? Jul 14 23:14:22 siegfried: No, from now on the drive should remain plugged in at all times (unless you have a problem that you are trying to resolve). Jul 14 23:14:56 Check the web page: on the bottom it will tell you if it is running from flash or if it is runnign from disk... Jul 14 23:15:19 And now I have telnet connection Jul 14 23:15:32 should I be able to telnet too? Jul 14 23:15:34 vipen: check to see if the drive has been mounted automatically (probably not), and if not, mount it manually as we did before. Jul 14 23:15:45 okay Jul 14 23:16:07 siegfried: yes, you should be able to telnet it: when you telnet in, the banner at login should tell you that you are in "unslung" mode. Jul 14 23:17:12 telnet is not working... The web page is... Jul 14 23:17:54 oops, it powered itself off. Jul 14 23:18:05 It has done that several times today. Jul 14 23:18:52 It's mounted Jul 14 23:19:24 Is it mounted on /share/flash/... or /share/hdd/... ? (I've forgetten by now, sorry!) Jul 14 23:19:32 hdd Jul 14 23:20:58 I'm rebooting again. Jul 14 23:21:26 vipen: what is the output from "ls -l /etc/passwd" ? Jul 14 23:22:22 OK, I got the web page. telnet could not open connection to the host... shall I goto to the Manage Telnet page? Jul 14 23:22:53 I'm in... Jul 14 23:23:01 lrwxrwxrwx 1 root root 22 Jul 15 01:31 /etc/passwd -> /share/hd Jul 14 23:23:01 d/conf/passwd Jul 14 23:24:07 vipen: use the "passwd" command to set the password to whatever you want. Then check the output from the "ls -l /etc/passwd" command again. Jul 14 23:24:11 shall issue the command "mount /dev/sda1 /share/hdd/data" again? Is that what vipen did? Jul 14 23:25:12 -rw-r--r-- 1 root root 480 Jul 15 01:42 /etc/passwd Jul 14 23:25:26 siegfried: have you telnet'd in? Jul 14 23:25:54 yes -- I'm so happy! Now what do I do? I don't think I have a password problem. Jul 14 23:26:02 Did it print a banner when you logged in similar to: ---------- NOTE: THIS SYSTEM IS CURRENTLY UNSLUNG ---------- ? Jul 14 23:26:15 Thx, now it works!!! :D Jul 14 23:26:20 yes! Jul 14 23:26:25 vipen: you're not done yet! Jul 14 23:26:39 Huh? I thougt so Jul 14 23:27:06 siegfried: you're done - congratulations. Jul 14 23:27:34 vipen: you've updated the passwd database, but if you do the "ls -l /etc/passed" command again, you should see that it is no longer a link to the hard drive. Jul 14 23:27:48 Well, should I be able to see my files from my desktop machine without telnet and without the web? Jul 14 23:28:10 siegfried: whatever it used to do before you unslung, it should do now as well. Jul 14 23:28:36 Okay, so what to do now? Jul 14 23:28:44 vipen: what's the output from the "ls -l /etc/passwd" command? Jul 14 23:28:57 -rw-r--r-- 1 root root 480 Jul 15 01:42 /etc/passwd Jul 14 23:29:11 Good. normal file. we need to copy it around to the right places. Jul 14 23:29:15 I SEE MY FILES! Hurray! Jul 14 23:29:32 let me go check where we need to copy it to. Jul 14 23:29:39 okay Jul 14 23:29:46 Thanks MWester! Now I will have to repeat this procedure with a second drive and slug! Jul 14 23:30:12 You're welcome siegfried. Jul 14 23:30:15 Enjoy! Jul 14 23:30:28 vipen: the following commands should do it: Jul 14 23:30:41 cp /etc/passwd /usr/local/passwd Jul 14 23:30:55 Yes... Jul 14 23:31:27 cp /etc/passwd /share/hdd/conf/passwd Jul 14 23:31:41 Yes... Jul 14 23:32:11 (I'm searching my slug's disk..." Jul 14 23:32:37