Posted: Sat Feb 18, 2012 13:38 Post subject: hard drive does not start on boot
I have Asus RtN16. I have king mod with a usb connected external hard drive.
When I boot up or reboot the system, the /opt drive is empty. I check dmesg and it doesn't look like a drive was detected. This used to work, but I'm not sure how well it used to work since I rarely reboot my router.
I can get the drive to be recognized by powering down the external drive and then powering it back on. However, I'd like this to be automated.
Here is the dmesg after I cycle power on the hard drive manually.
Code:
Linux version 2.6.24.111 (bluebat@opensuse) (gcc version 4.1.2) #20 Fri Dec 16 15:22:59 CET 2011
CPU revision is: 00019740
Determined physical RAM map:
memory: 07fff000 @ 00000000 (usable)
Entering add_active_range(0, 0, 32767) 0 entries of 256 used
Zone PFN ranges:
Normal 0 -> 32767
HighMem 32767 -> 32767
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0 -> 32767
On node 0 totalpages: 32767
Normal zone: 0 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 32767 pages, LIFO batch:7
HighMem zone: 0 pages used for memmap
Movable zone: 0 pages used for memmap
Built 1 zonelists in Zone order. Total pages: 32767
Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd
Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, linesize 32 bytes.
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
PID hash table entries: 512 (order: 9, 2048 bytes)
CPU: BCM4716 rev 1 at 480 MHz
Using 240.000 MHz high precision timer.
console [ttyS0] enabled
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 124016k/131068k available (3550k kernel code, 6904k reserved, 1377k data, 188k init, 0k highmem)
Calibrating delay loop... 239.20 BogoMIPS (lpj=1196032)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
Generic PHY: Registered new driver
PCI: Using membase 8000000
PCI: Initializing host
PCI: Reset RC
PCI: no core
PCI: Fixing up bus 0
PCI/PCIe coreunit 0 is set to bus 1.
PCI: Fixing up bridge
PCI: Setting latency timer of device 0000:01:00.0 to 64
PCI: Fixing up bridge
PCI: Setting latency timer of device 0000:01:00.1 to 64
PCI: Enabling device 0000:01:00.1 (0004 -> 0006)
PCI: Fixing up bus 1
NET: Registered protocol family 2
Time: MIPS clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
RT-N16 GPIO Init
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
io scheduler noop registered
io scheduler deadline registered (default)
HDLC line discipline: version $Revision: 4.8 $, maxframe=4096
N_HDLC line discipline registered.
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 8) is a 16550A
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
MPPE/MPPC encryption/compression module registered
NET: Registered protocol family 24
PPPoL2TP kernel driver, V1.0
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
et_module_init: passivemode set to 0x0
PCI: Setting latency timer of device 0000:00:02.0 to 64
VID 0 is set in nvram, Ignoring
eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.138.9
PCI: Setting latency timer of device 0000:00:01.0 to 64
Physically mapped flash: Found 1 x16 devices at 0x0 in 8-bit bank. Manufacturer ID 0x0000c2 Chip ID 0x00007e
Amd/Fujitsu Extended Query Table at 0x0040
Physically mapped flash: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Flash device: 0x2000000 at 0x1c000000
bootloader size: 262144
nvram size: 32768
Physically mapped flash: Filesystem type: squashfs, size=0x920671
partition size = 9696256
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x01fe0000 : "linux"
0x001a0c00-0x00ae0000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
0x01fe0000-0x02000000 : "nvram"
0x00ae0000-0x01fe0000 : "ddwrt"
Found a 0MB serial flash
sflash: found no supported devices
Broadcom Watchdog Timer: 0.07 initialized.
u32 classifier
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (2048 buckets, 8192 max)
ctnetlink v0.93: registering with nfnetlink.
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
ClusterIP Version 0.8 loaded successfully
TCP bic registered
TCP cubic registered
TCP westwood registered
TCP highspeed registered
TCP hybla registered
TCP htcp registered
TCP vegas registered
TCP scalable registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Welcome to PF_RING 3.2.1
(C) 2004-06 L.Deri <deri@ntop.org>
NET: Registered protocol family 27
PF_RING: bucket length 128 bytes
PF_RING: ring slots 4096
PF_RING: sample rate 1 [1=no sampling]
PF_RING: capture TX No [RX only]
PF_RING: transparent mode Yes
PF_RING initialized correctly.
PF_RING: registered /proc/net/pf_ring/
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
decode 1f02
VFS: Mounted root (squashfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 188k freed
roboswitch: Probing device eth0: found a 53115!
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
USB20H mdio control register : 0x8000000c
PCI: Setting latency timer of device 0000:00:04.1 to 64
ehci_hcd 0000:00:04.1: EHCI Host Controller
ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:04.1: irq 5, io mem 0x18004000
ehci_hcd 0000:00:04.1: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
USB Universal Host Controller Interface driver v3.0
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
USB20H mdio control register : 0x8000000c
PCI: Setting latency timer of device 0000:00:04.0 to 64
ohci_hcd 0000:00:04.0: OHCI Host Controller
ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:04.0: irq 5, io mem 0x18009000
usb usb2: configuration #1 chosen from 1 choice
usb 1-2: new high speed USB device using ehci_hcd and address 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
SCSI subsystem initialized
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
device br0 entered promiscuous mode
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
device eth1 entered promiscuous mode
br0: port 2(eth1) entering learning state
br0: port 1(vlan1) entering learning state
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
device br0 entered promiscuous mode
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
br0: topology change detected, propagating
br0: port 1(vlan1) entering forwarding state
device vlan2 entered promiscuous mode
device vlan2 left promiscuous mode
etherip: Ethernet over IPv4 tunneling driver
usb 1-2: new high speed USB device using ehci_hcd and address 3
usb 1-2: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
scsi 0:0:0:0: Direct-Access WDC WD64 00AAKS-00A7B2 PQ: 0 ANSI: 2 CCS
sd 0:0:0:0: [sda] 1250263728 512-byte hardware sectors (640135 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 28 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 1250263728 512-byte hardware sectors (640135 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 28 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
/dev/scsi/host0/bus0/target0/lun0: p1 p2 p3
sd 0:0:0:0: [sda] Attached SCSI disk
usb-storage: device scan complete
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 128512k swap on /dev/scsi/host0/bus0/target0/lun0/part2. Priority:-1 extents:1 across:128512k
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
the dmesg when the hard drive fails to load is the same, except it ends at "etherip: Ethernet over IPv4 tunneling driver "
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Sat Feb 18, 2012 17:54 Post subject:
All that extra "filler" information means nothing to me. You should try and run "df -h" at a command prompt of your router. That will tell you if it is mounted and where
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Sun Feb 19, 2012 2:21 Post subject:
You mentioned "rebooting the hard drive manually", how did you do this?
In addition, you did not post your firmware version. It could possibly be that you have a "bad" version. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Sun Feb 19, 2012 16:55 Post subject:
As that is not standard firmware (it was created by someone else using the DD-WRT source), you will have to contact that person to get help with your problem. I know that Kong has made some minor modifications to make certain parts of DD-WRT work better. He would know how to help you in resolving the issue.
If your problem was with the "original" DD-WRT firmware 18010, then it would be an issue directly with the firmware here and I could possibly help you. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
I've run this build for some time and find it very stable and reliable. Try to reflash as a first action.
I beleive you are running Optware the right way: Since Kong has added some functionality when it comes to drive mounting it's a good idea to disable some of the service that may interact with the new mounting scheme. Don't think this is critical though.
I've run this build for some time and find it very stable and reliable. Try to reflash as a first action.
I beleive you are running Optware the right way: Since Kong has added some functionality when it comes to drive mounting it's a good idea to disable some of the service that may interact with the new mounting scheme. Don't think this is critical though.
thanks, glad to know it should be working.
I did used to run optware the right way, before I installed kong mod. I figured those settings would be overwritten. Are they still there because the init scripts on the hard drive were not removed? I did notice that I don't recognize recognize some of the things on the init directory. Here is what I have init. Things like twonky, I don't remember installing before or after I flashed kong mod.
No need to alter or delete the optware installation. Just flash the build according to the instructions for RT-N16 in the wiki (installation).
One important step is not in the wiki: Clear the browser cache before flashing!
After flashing you will have to reenter the settings in the gui.
You should consider refreshing your Optware installation and run the service "factdefault" which restores the router settings automatically after a clean flash.
You may disable at least the services "automount" and "swap" when running a KingKong build
No need to alter or delete the optware installation. Just flash the build according to the instructions for RT-N16 in the wiki (installation).
One important step is not in the wiki: Clear the browser cache before flashing!
After flashing you will have to reenter the settings in the gui.
You should consider refreshing your Optware installation and run the service "factdefault" which restores the router settings automatically after a clean flash.
You may disable at least the services "automount" and "swap" when running a KingKong build
I can't use backup/restore for the settings? I have to manually enter them?
Also, how do you refresh optware isntallation? ipkg update?
Since you seem to have trouble with the current setup I think the best thing is not to use backup/restore - also this option should only be used to restore to an identical build. Did you use this method when upgrading to Kongs build?
You refresh OTRW by running the same command as when you installed it (not the drive partitioning of course)
To disable services not present in the services menu you chmod -x "file name" in /opt/etc/init.d i.e
chmod -x S35automount will disable automount after the router is rebooted
I did what you said and did a whole clean install. Still had the same problem. Then I realized that transmission is on by default when you install optware. And the first thing transmission does is try to download a 4 MB blocklist file. So I decided to disable that service and see what happens. Well so far I have rebooted twice in a row and both times, the drive was mounted correctly.
So it's either that or that I have a faulty hard drive that doesn't always bootup. I'm too tired to look at this right now, so I'll just hope turning off transmission was the solution.
