SATA disks not recognized after flashing alt-f
GoogleCodeExporter opened this issue · comments
What steps will reproduce the problem?
1.Use DNS-323 firmware page to flash Alt-F-0.1RC1
2.Reboot
3.My 2 sata drives with an md jbod partition is MIA
I've rebooted multiple times, pulled the power plug and restarted and it ALMOST
always start with no disks detected. Sometime, it does detect the 2 SATA
drives and the two ext3 partitions are mounted at /mnt/sda4 /mnt/sdb4. (Not
positive about the actual mount point partition numbers). When it does mount
the partitions, any attempt to ls the contents of the directory shows an IO
error. Before flashing the DNS-323, I was using the latest 1.10 firmware and
had no issues with the drives ever.
Here is the output of dmesg.
# dmesg
Linux version 2.6.35.14 (jcard@silver) (gcc version 4.3.3 (GCC) ) #1 Wed Oct 12
14:15:37 WEST 2011
CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
CPU: VIVT data cache, VIVT instruction cache
Machine: D-Link DNS-323
Clearing invalid memory bank 0KB@0xffffffff
Clearing invalid memory bank 0KB@0xffffffff
Clearing invalid memory bank 0KB@0xffffffff
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x41000403
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 16384
free_area_init_node: node 0, pgdat c02ff47c, node_mem_map c0310000
Normal zone: 128 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 16256 pages, LIFO batch:3
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: root=/dev/ram console=ttyS0,115200 :::DB88FXX81:egiga0:none
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 55576k/55576k available, 9960k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xc4800000 - 0xfd800000 ( 912 MB)
lowmem : 0xc0000000 - 0xc4000000 ( 64 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0026000 ( 120 kB)
.text : 0xc0026000 - 0xc02d2000 (2736 kB)
.data : 0xc02ea000 - 0xc02ffaa0 ( 87 kB)
NR_IRQS:64
Calibrating delay loop... 332.59 BogoMIPS (lpj=1662976)
pid_max: default: 4096 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Orion ID: MV88F5182-A2. TCLK=166666667.
DNS-323: Identified HW revision B1
DNS-323: Found ethernet MAC address: 00:24:01:07:6c:dc.
bio: create slab <bio-0> at 0
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
PCI: CLS 0 bytes, default 32
Unpacking initramfs...
Freeing initrd memory: 6260K
squashfs: version 4.0 (2009/01/31) Phillip Lougher
aufs 2-standalone.tree-35-20100809
msgmni has been set to 120
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
console [ttyS0] enabled
loop: module loaded
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 2
scsi0 : sata_mv
scsi1 : sata_mv
ata1: SATA max UDMA/133 irq 29
ata2: SATA max UDMA/133 irq 29
physmap platform flash device: 00800000 at f4000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cmdlinepart partition parsing not available
RedBoot partition parsing not available
Using physmap partition information
Creating 5 MTD partitions on "physmap-flash.0":
0x000000000000-0x000000010000 : "MTD1"
0x000000010000-0x000000020000 : "MTD2"
0x000000020000-0x0000001a0000 : "Linux Kernel"
0x0000001a0000-0x0000007d0000 : "File System"
0x0000007d0000-0x000000800000 : "u-boot"
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:24:01:07:6c:dc
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 17, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
input: gpio-keys as /class/input/input0
i2c /dev entries driver
rtc-m41t80 0-0068: chip found, driver version 0.05
rtc-m41t80 0-0068: rtc core: registered m41t80 as rtc0
lm75 0-0048: hwmon1: sensor 'lm75'
md: linear personality registered for level -1
md: raid1 personality registered for level 1
Registered led device: power:blue
Registered led device: right:amber
Registered led device: left:amber
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP cubic registered
NET: Registered protocol family 17
rtc-m41t80 0-0068: setting system clock to 2012-02-06 02:43:26 UTC (1328496206)
ata1: link is slow to respond, please be patient (ready=0)
ata1: SRST failed (errno=-16)
ata1: link is slow to respond, please be patient (ready=0)
ata1: SRST failed (errno=-16)
ata1: link is slow to respond, please be patient (ready=0)
ata1: SRST failed (errno=-16)
ata1: limiting SATA link speed to 1.5 Gbps
ata1: SRST failed (errno=-16)
ata1: reset failed, giving up
ata2: link is slow to respond, please be patient (ready=0)
ata2: SRST failed (errno=-16)
ata2: link is slow to respond, please be patient (ready=0)
ata2: SRST failed (errno=-16)
ata2: link is slow to respond, please be patient (ready=0)
ata2: SRST failed (errno=-16)
ata2: limiting SATA link speed to 1.5 Gbps
ata2: SRST failed (errno=-16)
ata2: reset failed, giving up
Freeing init memory: 120K
aufs test_add:253:mount[53]: uid/gid/perm /tmproot/rootsq 0/0/0777, 0/0/0755
usbcore: registered new interface driver usblp
eth0: link up, 1000 Mb/s, full duplex, flow control disabled
There is nothing in /var/log/messages. Here is the only thing is
/var/log/boot.log
Feb 6 02:45:27 syslogd started: BusyBox v1.15.3
Feb 6 02:45:27 root: fsck 1.41.14 (22-Dec-2010) fsck.minix: BusyBox v1.15.3
(2011-10-12 14:14:40 WEST) /dev/mtdblock0 is clean, check is skipped
Feb 5 20:45:28 root: FIXME: Waiting 3 sec for kernel enumeration to finish...
Feb 5 20:45:31 root: FIXME: stop waiting.
Feb 5 20:45:31 root: IP from flash-defaults
Feb 5 20:45:31 syslogd exiting
Any ideas what the issue might be?
Thanks
John
Original issue reported on code.google.com by john.m.a...@gmail.com on 6 Feb 2012 at 2:57
What are the disk model?
Do they have a 1.5/3GB/s jumper?
Can you try remove (or insert) them?
Do you have another disk to test with?
Original comment by whoami.j...@gmail.com on 6 Feb 2012 at 3:47
I have 2 1TB Seagate drives, no jumper. Yes, i tried removing and reinserting
them. Powering down the unit, etc. I really needed to get access to the data
on my drives, so I ended up putting the dlink v1.10 back on the unit and my
drives were working fine after the reboot.
I definitely want to try out alt-f again and I'm not sure what the problem was,
but for now, this issue can be closed.
Original comment by john.m.a...@gmail.com on 7 Feb 2012 at 5:17
The issue has to be disk-dependent.
For future reference could you please post the complete brand/model?
Thanks
Original comment by whoami.j...@gmail.com on 7 Feb 2012 at 6:45
Sorry, I meant to copy/paste the model number on my previous post.
Both drives are identical and are: Seagate ST31000340AS
They are 1TB 7200rpm drives.
Original comment by john.m.a...@gmail.com on 7 Feb 2012 at 10:30
Of course the problem might be some kernel/hardware incompatibility, but a
search returned this:
http://www.theinquirer.net/inquirer/news/1050374/seagate-barracuda-7200-drives-f
ailing
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207951
Those are pretty old, and might not apply to your drives, mainly because they
work with the stock DNS-323 firmware.
Thanks.
Original comment by whoami.j...@gmail.com on 8 Feb 2012 at 12:52
Wow, I had no idea this drive series had this problem. I guess it's possible
that it could be the drive. Maybe I just got lucky after the last reboot and
it started working again. I've had these drives for a few years, but I've
probably only rebooted the NAS 4 or 5 times.
I'll see about applying the firmware update.
Original comment by john.m.a...@gmail.com on 8 Feb 2012 at 3:41
Closed as no further user feedback was received
Original comment by whoami.j...@gmail.com on 28 Feb 2012 at 5:04
- Changed state: Done