Wes,
OpenWGT is the project to re-flash netgear devices with linux busybox or debian
variants. Unfortunately, IMO the netgear camp is not as well organized as the
Linksys camp: Openwrt.org (I am an openwrt White Russian user).
You can use openwrt to research the Netgear ReadyNAS specs, but I
Hi,
while diving deeply in zfs in order to recover data I found that every
uberblock in label0 does have the same ub_rootbp and a zeroed ub_txg. Does it
means only ub_txg was touch while detaching?
Hoping it is the case, I modified ub_txg from one uberblock to match the tgx
from the label
Benjamin Brumaire wrote:
I try to calculate it assuming only uberblock is relevant.
#dd if=/dev/dsk/c0d1s4 bs=1 iseek=247808 count=168 | digest -a sha256
168+0 records in
168+0 records out
710306650facf818e824db5621be394f3b3fe934107bdfc861bbc82cb9e1bbf3
Is this on SPARC or x86 ?
ZFS stores
it is on x86.
Does it means that I have to split the output from digest in 4 words (each 8
bytes) and reverse each before comparing with the stored value?
bbr
This message posted from opensolaris.org
___
zfs-discuss mailing list
Seems kind of old. I am using Generic_127112-11 here.
Probably many hundreds of nasty bugs have been
eliminated since the version you are using.
I've updated to the latest available kernel 127128-11 (from 28 Apr) which
included a number of fixes to AHCI SATA driver and ZFS.
Didn't help.
Hello all,
Some time ago i did write a simple script to handle on the fly
filesystem(zfs) creation for linux clients
(http://www.posix.brte.com.br/blog/?p=102). I was thinking in improve that
script to handle more generic remote actions... but i think we could start a
project on this:
A
OK, I tried replying by email, and got a message that a moderator will approve
the message sometime... but that was a few hours ago, so I'm reverting to this
forum software again :)
Here's the reply I emailed:
Hi Richard,
I ran the format comand, selected the number of one of the disks in the
Thanks Max,
I have not been able to find any new firmware for these drives (Western Digital
WD7500AAKS) so I have sent an email to Western Digital to enquire about
firmware updates. I'll see what they reply with, but I'm not too hopeful.
In the meantime I decided to copy the files one at a
Hi Simon,
One quick note. You don't have to cp each file one at a time to see
which one it hangs on. Just run truss. It should be the last file
that it opened. To see this with truss, do:
truss cp -r ...
Don't worry about all the truss output. You are probably only
concerned with the
or work around the NCQ bug in the drive's FW by typing:
su
echo set sata:sata_max_queue_depth = 0x1 /etc/system
reboot
Rob
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
SV wrote:
OpenWGT is the project to re-flash netgear devices with linux busybox or
debian variants. Unfortunately, IMO the netgear camp is not as well organized
as the Linksys camp: Openwrt.org (I am an openwrt White Russian user).
You can use openwrt to research the Netgear ReadyNAS
Simon,
I think you should review the checksum error reports from the fmdump
output (dated 4/30) that you supplied previously.
You can get more details by using fmdump -ev.
Use zpool status -v to identify checksum errors as well.
Cindy
Simon Breden wrote:
Thanks Max,
I have not been able
Thanks Cindy.
Here's the zpool status -v output:
# zpool status -v tank
pool: tank
state: ONLINE
scrub: none requested
config:
NAMESTATE READ WRITE CKSUM
tankONLINE 0 0 0
raidz1ONLINE 0 0 0
c1t1d0
Okay, thanks.
I wanted to rule out that the checksum errors reported on 4/30
were persistent enough to be picked up by zpool status. ZFS is
generally quick to identify device problems.
Since fmdump doesn't show any add'l recent errors either, then I
think you can rule out hardware problems other
OK then, thanks Cindy.
I have 2 current lines of investigation left (at least):
1. assumption the problem could relate to a drive firmware bug
2. there's a new BIOS for the motherboard available which might possibly have
some effect
For the idea that it's a drive firmware bug, I'm currently
Assuming that this problem could be related to a drive firmware bug I have:
1. tuned off NCQ -- or in fact limited the queue depth to 1
2. used truss with the cp command
I found this for NCQ: http://blogs.sun.com/erickustarz/entry/ncq_tunable
=
NCQ
Rustam rustam at code.az writes:
Didn't help. Keeps crashing.
The worst thing is that I don't know where's the problem. More ideas on
how to find problem?
Lots of CKSUM errors like you see is often indicative of bad hardware. Run
memtest for 24-48 hours.
-marc
17 matches
Mail list logo
