**** BEGIN LOGGING AT Fri Nov 07 02:59:57 2008 Nov 07 03:13:20 look in /etc to find the file that lists the volume id information (should be blkid.tab or something like that). See if /dev/sdb1 is listed in there. Nov 07 11:57:54 good morning to everyone! Nov 08 01:32:55 hi Nov 08 01:33:44 hello Nov 08 01:33:52 I that problem i had yesterday with the drives is because of transmission Nov 08 01:34:38 so you got it fixed? Nov 08 01:35:17 when i resume a torrent it sarts to varify, my disk is at sdb1, the either it says permission denied or re starts the torret, now my disk is at sdc1, Nov 08 01:35:31 then* Nov 08 01:36:27 why does it keep doing this? Nov 08 01:41:11 how can I fix it? Nov 08 01:43:13 You fix it by mounting the drive by lable. Nov 08 01:43:27 that doees not work Nov 08 01:43:41 Works for me Nov 08 01:44:12 ok, so why cant I do it? Nov 08 01:44:30 That's a question that only you can answer, of course. Nov 08 01:44:33 duh, it my awsome luck Nov 08 01:44:41 XD Nov 08 01:45:05 I cant find a better explanation Nov 08 01:45:19 My experience is that those who posess "lucky rabbits feet" don't get very far with technical problems ;) Nov 08 01:45:40 Maybe you should consider a technique termed "debugging" instead :p Nov 08 01:45:58 Did you check the blkid file as I suggested yesterday? Nov 08 01:46:12 no, sorry by luck i ment bad luck Nov 08 01:46:32 good luck, bad luck -- same thing. Nov 08 01:46:33 I did not check it, Nov 08 01:46:43 dun no why Nov 08 01:46:49 dont* Nov 08 01:47:52 where is it? Nov 08 01:48:15 search in /etc Nov 08 01:48:39 It will list all the partitions detected, and the labels and uuids for them. Nov 08 01:48:56 is it /blkid.tab ? Nov 08 01:49:31 could be, don't remember. Does it look like it contains the info you need -- which would be the partition info for the drive that's giving you trouble? Nov 08 01:50:10 yes Nov 08 01:50:49 /dev/sdb1 Nov 08 01:51:06 and it seems that it did lable Nov 08 01:51:19 label* Nov 08 01:52:39 but I also have /dev/sdd2 Nov 08 01:52:48 device DEVNO="0x0833" TIME="1224421246" TYPE="swap">/dev/sdd3 Nov 08 01:52:56 /dev/sdc1 Nov 08 01:53:04 /dev/sdc2 Nov 08 01:53:12 /dev/sdc3 Nov 08 01:53:32 Right. Nov 08 01:53:47 So, what was the line you had in /etc/fstab? Nov 08 01:53:47 I only have 2 drives, sda1(root), sdb1(files) Nov 08 01:54:30 so is sdd2,3, sdc1,2,3 extra? Nov 08 01:54:49 left overs from earlier. Nov 08 01:54:58 but what was the line you had in /etc/fstab? Nov 08 01:55:05 should i remove it? Nov 08 01:55:13 No - what was it? Nov 08 01:55:33 this /dev/sdb1 /media/sdb1 ext3 rw,async,data=ordered Nov 08 01:55:58 Ok, but that's just a standard mount by device name Nov 08 01:56:04 yes Nov 08 01:56:56 I think we're failing to communicate here. Aren't you the guy who was trying to mount a device by a label -- you put a line in your fstab to do that? Nov 08 01:57:04 yes Nov 08 01:57:41 so should it be LABEL=250wd /harddrive/ ext3 defaults 0 0 Nov 08 01:58:08 Ok. I'm asking what that line was, so we can compare it to the informaiton in your blkid file. That like gave orders to Linux to mount a device using the label as an identifier; the blkid file is managed by linux and contains the mapping of device names (which change) to labels and UUIDs (which don't). Nov 08 01:58:27 Should it be that? Nov 08 01:58:44 line from /etc/fstab: /dev/sdb1 /media/sdb1 ext3 rw,async,data=ordered Nov 08 01:58:47 I though you had some other label used? Nov 08 01:59:04 we were going to use harddrive Nov 08 01:59:24 but its 250wd Nov 08 01:59:59 I think I don't see a /dev/sda listed. Nov 08 02:00:32 it the first line: /dev/dev/sda1 / ext3 defaults 1 1 Nov 08 02:00:50 Right. But it's not in the blkid table. Nov 08 02:01:16 it is first line:/dev/sda1 Nov 08 02:01:35 Oh, there it is. Nov 08 02:01:44 Ok, good. Nov 08 02:02:21 Then just edit the fstab, and replace the /dev/sdb1 with the LABEL=whatever bit. Nov 08 02:02:21 I have no problems with the sda disk Nov 08 02:02:27 ok Nov 08 02:03:10 and reboot Nov 08 02:03:13 no Nov 08 02:03:17 ok Nov 08 02:03:24 is anything using that drive? Nov 08 02:03:51 should not be Nov 08 02:04:06 then just try to umount it: umount /dev/sdb1 Nov 08 02:04:40 ok no error Nov 08 02:04:50 Good. Then type: mount -a Nov 08 02:04:54 What does it say? Nov 08 02:05:17 mount: mount point does not exist Nov 08 02:05:31 Excellent. Nov 08 02:05:37 cool Nov 08 02:05:56 Ok, look at the line that you have in the /etc/fstab -- where is it trying to mount that drive? Nov 08 02:06:30 /media/sdb1 Nov 08 02:06:44 List the contents of /media -- does sdb1 exist? Nov 08 02:07:20 yes Nov 08 02:07:57 hmm... ok. type "mount /media/sdb1" Nov 08 02:08:05 er, cancel that. Nov 08 02:08:10 ok Nov 08 02:08:15 type "mount" Nov 08 02:08:19 what is the outpu? Nov 08 02:08:53 shows every thing ok, last line is /dev/sdb1 on /media/sdb1 type ext3 (rw,data=ordered) Nov 08 02:09:37 Ok. I wonder what it was complaining about, then. Show us your fstab file in its entirety. Nov 08 02:09:57 ok Nov 08 02:10:02 one sec Nov 08 02:10:08 rootfs on / type rootfs (rw) Nov 08 02:10:18 /dev/root on /initrd type jffs2 (ro) Nov 08 02:10:25 /dev/sda1 on / type ext3 (rw,data=ordered) Nov 08 02:10:32 proc on /proc type proc (rw) Nov 08 02:10:40 sysfs on /sys type sysfs (rw) Nov 08 02:10:47 /dev/sda1 on /dev/.static/dev type ext3 (rw,data=ordered) Nov 08 02:10:55 tmpfs on /dev type tmpfs (rw) Nov 08 02:11:04 /dev/sda3 on /home type ext3 (rw,data=ordered) Nov 08 02:11:10 tmpfs on /var/volatile type tmpfs (rw) Nov 08 02:11:17 tmpfs on /dev/shm type tmpfs (rw) Nov 08 02:11:24 usbfs on /proc/bus/usb type usbfs (rw) Nov 08 02:11:28 That's the output from "mount", not the fstab. Nov 08 02:11:30 devpts on /dev/pts type devpts (rw) Nov 08 02:11:35 XD Nov 08 02:11:38 ok Nov 08 02:12:02 /dev/dev/sda1 / ext3 defaults 1 1 Nov 08 02:12:08 proc /proc proc defaults 0 0 Nov 08 02:12:16 tmpfs /var/volatile tmpfs mode=0755 0 0 Nov 08 02:12:24 #tmpfs /media/ram tmpfs defaults 0 0 Nov 08 02:12:30 tmpfs /dev/shm tmpfs mode=0777 0 0 Nov 08 02:12:36 usbfs /proc/bus/usb usbfs defaults 0 0 Nov 08 02:12:47 /dev/sda3 /home ext3 defaults 1 1 Nov 08 02:12:53 /dev/sda2 swap swap defaults 0 0 Nov 08 02:12:58 LABEL=250wd /media/sdb1 ext3 rw,async,data=ordered Nov 08 02:13:35 That's it? Nov 08 02:13:35 thats it Nov 08 02:13:45 ok. The first line is a bit bogus. Nov 08 02:13:51 ok Nov 08 02:14:05 I did nothing with it Nov 08 02:14:19 should be /dev/sda1 not /dev/dev/sda1, but if you didn't change it, then leave it be. Nov 08 02:14:33 ok Nov 08 02:14:55 Ok, well there's nothing obvious for why it complained about the mount point. But better safe than sorry. Nov 08 02:15:25 The /media directory is special, used for automounting stuff. Nov 08 02:15:42 So you don't want to use that manually, it could cause problems later on. Nov 08 02:15:54 ok Nov 08 02:16:41 Instead, create a directory in the root and use that instead -- exactly the way /home is done. For example, "mkdir /stuff" and then change that last line so that instead of /media/sdb1 it's /stuff Nov 08 02:17:34 then type "umount /media/sdb1" and type "mount /stuff" Nov 08 02:17:34 ok I will mount it in home. Is that ok? Nov 08 02:17:40 No Nov 08 02:17:44 :( Nov 08 02:18:52 You have a disk mounted on /home. So if you want to mount another one in /home/stuff, then you need to ensure that /home is mounted before /home/stuff is mounted -- and that's hard to do. The only reliable thing you can know for sure is that / will be mounted before anything else. Nov 08 02:19:17 ok Nov 08 02:19:32 People do it, but it's really bad practice. Nov 08 02:21:04 ok its mounted Nov 08 02:21:34 ill test it out and tell you how it works Nov 08 02:23:43 Cool. :) Nov 08 02:24:13 no Nov 08 02:24:19 not cool? Nov 08 02:24:33 I opend transmission /opt/bin/transmission-daemon -w /stuff/downloads/ Nov 08 02:24:44 opened a torrent Nov 08 02:24:52 it started to varify Nov 08 02:25:22 then it started to dl, but it unmounted from /stuff Nov 08 02:25:50 Pastebin the last 50 lines or so from "dmesg" Nov 08 02:26:26 from the bottem? Nov 08 02:26:52 how about a few that stand out Nov 08 02:26:54 <2>EXT3-fs error (device sdb1): ext3_readdir: directory #30670849 contains a hole at offset 0 Nov 08 02:27:03 <3>scsi 1:0:0:0: rejecting I/O to dead device Nov 08 02:27:17 Er, yeah. that sorta tells the tale. Nov 08 02:27:19 <3>Buffer I/O error on device sdb1, logical block 30691328 Nov 08 02:28:04 Hopefully the cat just got the cable. Nov 08 02:28:11 actually the whole thing is full of those Nov 08 02:28:32 Hope there wasn't any data on there that you value Nov 08 02:28:42 why does a cat need cable? Nov 08 02:29:34 uh, but I can ftp into the drive, watch my videos, whatever Nov 08 02:30:15 I have no idea, but sure do like to chew on them. They make little pin-holes with their teeth, and that results in all sorts of weird errors. but lots cheaper to get a new cable than a new disk. Nov 08 02:30:25 But it sounds like reading is ok. Nov 08 02:30:41 oh, I dont have a cat Nov 08 02:30:44 yet Nov 08 02:30:46 Then it might be that the disk is just corrupted and needs to be fsck'd Nov 08 02:31:01 uh Nov 08 02:31:05 ? Nov 08 02:31:11 Frankly -- I'd do that on a desktop Linux system; fsck can run out of memory on the NSLU2 on a big drive. Nov 08 02:31:31 I have a bootable knoppix Nov 08 02:31:59 That'll do nicely. Nov 08 02:32:02 :) Nov 08 02:32:42 Move the drive to that system, make sure that you "umount" it, and run fsck on it -- say "No" to everything the first time around, just to get an idea of what might be wrong. Nov 08 02:32:53 Google fsck to get some real-life examples on how to use it. Nov 08 02:33:41 hum, where did I put it..... Nov 08 02:34:07 oh, will I lose any data? Nov 08 02:35:11 You might. THat's why you say "no" first time through. Nov 08 02:35:30 Then you can decide how to try to save anything before you let it try to repair stuff. Nov 08 02:35:39 ok Nov 08 02:35:55 The problem is that the errors look an awful lot like disk i/o errors -- hardware. Nov 08 02:36:19 the hardware should be fine Nov 08 02:36:28 That's why I asked about the cable. Nov 08 02:36:44 I used it in my xbox, had all my movies and music in it Nov 08 02:37:35 oh, I have a extra usb ide adapter! Nov 08 02:37:44 just remembered Nov 08 02:39:29 yay found my knoppix Nov 08 02:39:50 the cd was unlabeled Nov 08 02:54:59 : uh, I conected the disk to a pc running knoppix and some folders are locked, Nov 08 02:55:21 like one of my download, and my whole media folder **** ENDING LOGGING AT Sat Nov 08 03:00:02 2008