**** BEGIN LOGGING AT Fri Sep 05 02:59:56 2008 Sep 05 06:44:02 03bzhou * r9027 10optware/trunk/make/mutt.mk: mutt: 1.5.15 -> 1.5.16, added libidn to DEPENDS Sep 05 06:50:32 03rwhitby * r9028 10optware/trunk/ (3 files in 3 dirs): optware-bootstrap: Moved syno-e500 directory to /volume1/@optware Sep 05 15:32:25 03bzhou * r9029 10optware/trunk/platforms/packages-syno-x07.mk: packages-syno-x07: latest bluez-hcidump & bluez-utils do not build with syno-x07 toolchain Sep 05 15:32:28 03bzhou * r9030 10optware/trunk/sources/optware-bootstrap/target-specific.mk: optware-bootstrap: moved REAL_OPT_DIR to /volume1/@optware on syno-x07 Sep 05 16:20:37 is there any way of seeing why a harddrive isn't working under unslung? Sep 05 16:21:11 telnet in and have a look at what dmesg /var/log/messages /var/log/messages.old says Sep 05 16:22:50 doesnt say anything about the disk Sep 05 16:23:25 mine does Sep 05 16:23:37 well, its like it doesn't discover the disk at all Sep 05 16:23:58 does the slug led light up? Sep 05 16:24:02 nop Sep 05 16:24:09 not for the drive Sep 05 16:24:11 is there enough power Sep 05 16:24:21 new psu Sep 05 16:24:22 3.5" or 2.5"? Sep 05 16:24:31 3.5" Sep 05 16:24:39 ahh, so external power Sep 05 16:24:42 yep Sep 05 16:25:17 so you don't see any messages in /var/log/messages when you plug in? Sep 05 16:25:47 nop Sep 05 16:26:05 what about the other port Sep 05 16:26:20 same Sep 05 16:26:26 nothing happens Sep 05 16:26:39 and the drive works in your pc? Sep 05 16:26:42 yep Sep 05 16:26:46 wth usb i mean Sep 05 16:26:49 yep Sep 05 16:27:34 makes it a bit hard to format and unsling to it Sep 05 16:28:36 kinda annoying because it has been working with usb and then it just didn't Sep 05 16:28:38 03bzhou * r9031 10optware/trunk/ (3 files in 2 dirs): bluez-{utils,hcidump}: worked around and promoted on syno-x07 Sep 05 16:29:10 ahh, so this wasn't a new drive you were trying? Sep 05 16:29:19 sounds like a hardware prob Sep 05 16:29:37 have you tried a flash stick or something to try to get the slug to light up Sep 05 16:31:31 hrm Sep 05 16:31:40 i think there's no power on the usb ports Sep 05 16:31:55 my phone is the only thing i have around that acts like usb mass storage Sep 05 16:32:05 strange, they are hardwired to the power plug Sep 05 16:32:07 but it doesn't ask me to go into that mode Sep 05 16:32:09 almost Sep 05 16:32:23 which it should as soon as it gets 5v Sep 05 16:34:42 what does your bootup log show? Sep 05 16:34:56 the whole messages? Sep 05 16:35:20 leave the drive hooked up, reboot it, and have a look, it may point to something Sep 05 16:35:28 pci probe begin Sep 05 16:35:28 ehci_hcd 00:01.2: NEC Corporation USB 2.0 Sep 05 16:35:28 ehci_hcd 00:01.2: irq 26, pci mem c3872f00 Sep 05 16:35:39 the beginning of the good bits with mine Sep 05 16:35:48 rebooting it Sep 05 16:35:49 ehci_hcd 00:01.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-19/2.4 Sep 05 16:35:50 Device descriptor:8 bytes received. Sep 05 16:35:50 Device descriptor:18 bytes received. Sep 05 16:35:50 hub.c: USB hub found Sep 05 16:35:50 with disk in Sep 05 16:36:44 is that fron /var/log/messages ? Sep 05 16:36:53 03bzhou * r9032 10optware/trunk/make/ (bluez-hcidump.mk bluez-utils.mk): bluez-{hcidump,utils}: same problem and workaround for vt4 Sep 05 16:37:00 yep, or /var/log/messages.old if it overflows Sep 05 16:39:03 http://pastebin.com/m47b9739b Sep 05 16:39:28 better idea than clogging up the channel Sep 05 16:40:56 i hate debugging hardware issues that possibly could be software Sep 05 16:41:18 but from what i can tell, there's no usb driver loading Sep 05 16:41:50 so no more after that? Sep 05 16:42:00 nop Sep 05 16:42:30 shame i don't know what teh boot log should look like for a non hdd slug.. Sep 05 16:46:23 ah well Sep 05 16:46:25 thanks for the help Sep 05 16:46:36 dont want to waste more time with this Sep 05 16:46:43 i wrecked the firmware now hopefully Sep 05 16:46:49 so i can just get it changed in for a new one Sep 05 16:46:50 i am digging thru my old logs, but they are all with the hdd attached Sep 05 16:46:54 you can reflash Sep 05 16:47:05 nop, didn't read the eraseall warning Sep 05 16:47:09 so i trashed the bootloader Sep 05 16:47:21 huh? Sep 05 16:47:28 but you can boot into it? Sep 05 16:47:38 now i just did the funny thing of cat /dev/urandom > /dev/mtdblock4 Sep 05 16:47:42 and its dead Sep 05 16:47:42 :D Sep 05 16:47:58 which means warranty should still be intact since they can't see what firmware i used Sep 05 16:48:26 no comment Sep 05 16:48:48 its not the most expensive device Sep 05 16:48:58 that was short perseverence in solving Sep 05 16:48:59 but thanks for the help anyways :) Sep 05 17:03:58 * mwester reads the backlog, and shakes his head sadly... Sep 05 22:02:38 03bzhou * r9033 10optware/trunk/make/mutt.mk: mutt: 1.5.16 -> 1.5.17 Sep 05 22:02:38 03bzhou * r9034 10optware/trunk/make/mutt.mk: mutt: 1.5.17 -> 1.5.18, with gpgme Sep 05 22:02:38 03bzhou * r9035 10optware/trunk/make/newsbeuter.mk: newsbeuter: 1.1 -> 1.2 Sep 05 22:13:29 03bzhou * r9036 10optware/trunk/make/mutt.mk: Sep 05 22:13:29 Revert "mutt: 1.5.17 -> 1.5.18, with gpgme" Sep 05 22:13:29 need xsltproc on build machine Sep 05 22:13:29 This reverts commit 157c455b158640927090a7a5bd9e86e780589169. Sep 05 23:58:03 03bzhou * r9037 10optware/trunk/make/py-bazaar-ng.mk: bzr: 1.6 -> 1.6.1 Sep 05 23:58:16 03bzhou * r9038 10optware/trunk/make/pcre.mk: pcre: 7.7 -> 7.8, separated pcre-dev Sep 06 00:00:31 03bzhou * r9039 10optware/trunk/make/cherokee.mk: cherokee: 0.8.0 -> 0.8.1 Sep 06 01:24:06 03bzhou * r9040 10optware/trunk/make/erlang.mk: erlang: R12B-3 -> R12B-4 **** ENDING LOGGING AT Sat Sep 06 02:59:57 2008