Reputation
541
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
2 10 24
Impact
~76k people reached

  • 0 posts edited
  • 1 helpful flag
  • 86 votes cast
Oct
24
awarded  Famous Question
Oct
16
awarded  Popular Question
Oct
9
revised Problem adding iptables rule
removed extraneous
Oct
9
accepted Problem adding iptables rule
Oct
9
asked Problem adding iptables rule
Oct
1
comment String comparison failing in bash
Fixed type-o in question (your second paragraph).
Oct
1
comment String comparison failing in bash
I see that four people have marked this for closure. There are also four upvotes, so clearly others think it is on-topic. Could someone please instruct me where questions of this nature belong? There is a /bash tag so I assumed this was acceptable use of the sub.
Oct
1
revised String comparison failing in bash
fixed logic
Sep
30
accepted String comparison failing in bash
Sep
30
comment String comparison failing in bash
Should that be [ "$i" = "green" ]? (EDIT, just tested - it works fine without quotes around green.)
Sep
30
revised String comparison failing in bash
edited body
Sep
30
asked String comparison failing in bash
Sep
28
comment wrong fs type, bad option, bad superblock when attempting to mount restored volume
Can I suggest some edits on your answer? There are a couple steps I took that are beneficial for others to know and use (assuming someone ever makes the same mistake I did last week!)
Sep
28
comment wrong fs type, bad option, bad superblock when attempting to mount restored volume
Ok just made a snapshot of the smaller partition and ran e2fsck on that. Success! Next is the much larger partition.
Sep
28
comment wrong fs type, bad option, bad superblock when attempting to mount restored volume
I do have backups, but on a very slow USB external drive. I verified that the images match the devices by running md5sum against each (which took quite a while across both images and devices).
Sep
28
comment wrong fs type, bad option, bad superblock when attempting to mount restored volume
I just ran e2fsck -n /dev/vg_ursula2012/lv_root, here's that output: gist.github.com/anonymous/b1c3543ec0173e7ef81e
Sep
28
revised wrong fs type, bad option, bad superblock when attempting to mount restored volume
added 30 characters in body
Sep
28
comment Restoring VG configuration from recovered drive
@Gravy any ideas here: unix.stackexchange.com/questions/232546/… ?
Sep
28
asked wrong fs type, bad option, bad superblock when attempting to mount restored volume
Sep
24
comment Restoring VG configuration from recovered drive
I'm imaging both sdb and sdc tonight. Takes a while since it's having to pipe across USB 2.0. Have you heard of or used rstudio?