09-26-2011
Does every UBIFS "partition" starts with UBI signature in header?
Im asking because first UBI signature is at 0xAD4000 offset (in big dump).
I think that bytes before 0xAD4000 are some kind of boot loader and it is not in UBIFS format.
Maybe this the reason why you have problems with mounting it.
What do you think?
10 More Discussions You Might Find Interesting
1. Solaris
I need to install a raid HBA internal card on a T5240. The reason is I have
more drives and the current mother board controller does not support more
than 4 drives.
My question is I have raidctl set up on current drives. If I install new HBA
card do I have to delete current raidctl and... (3 Replies)
Discussion started by: photon
3 Replies
2. UNIX for Advanced & Expert Users
Hi,
I need to redirect internal internet requests to a auth client site siting on the gateway. Currently users that are authenticated to access the internet have there mac address listed in the FORWARD chain. All other users need to be redirected to a internal site for authentication.
Can... (1 Reply)
Discussion started by: mshindo
1 Replies
3. Solaris
Hi all
i would like to ask some suggests about my next job!
I have to install a new Sun Netra T5220, with an additional internal StorageTek SAS HBA Raid.
The problem come in if every disk is now controlled by the HBA, how can I install the OS?
No disk is being detected by the OS.
SAS card... (2 Replies)
Discussion started by: kakabobo
2 Replies
4. UNIX for Advanced & Expert Users
I have a V490 that has couple internal disks attached to the same dual-port HBA card that I'm planning attach to the SAN for additional storage.
Would I sacrifice performance if I use the same HBA?
Is it better to throw in a new HBA instead? (1 Reply)
Discussion started by: kiem
1 Replies
5. Ubuntu
I need some assistance formatting a compact flash card in Ubtunu.
I connect up the CF card through a USB reader. Ubuntu recognizes the reader usb device, but does not "mount" the CF card as a device.
The CF card was formatted in FAT32 format.
Any help would be greatly appreciated.... (3 Replies)
Discussion started by: genesis211
3 Replies
6. AIX
Around a month ago we suffered a prolonged power outage, due to circumstances the servers and storage arrays were still in use when the UPS dropped. One of the servers was running a flash copy on the database while batch processing had commenced. This is the only server that suffered any further... (2 Replies)
Discussion started by: gull04
2 Replies
7. Shell Programming and Scripting
Hi All,
I have a rather stange set of requirements that I'm hoping someone here could help me with. We receive a file that is actually a concatenation of 4 files (don't believe this would change, but ideally the solution would handle n files).
The super-file looks like:... (7 Replies)
Discussion started by: Leedor
7 Replies
8. SuSE
I have noticed that when I copy files to flash disk and in UI I see message copy completed in notification area on task bar, usually copy is not completed. So, if I eject the media I loose data.
It is very serious problem because may cause loss of valuable and even critical data.
Moreover, when... (2 Replies)
Discussion started by: netwalker
2 Replies
9. Shell Programming and Scripting
Hi
I have been trying to figure a way to copy a file, (a template), that has internal variables. Using the values as defined for those variables in another script.
So a file called x -
#! /bin/bash
D=aa.$X.bb
And file y
#! /bin/bash
X=6
while read line
do
eval echo... (5 Replies)
Discussion started by: steadyonabix
5 Replies
10. AIX
Hey guys, wondering if this is possible to accomplish.
PowerHA SystemMirror7.1 active/passive cluster. Restored a clustered system in test and upgraded to the latest version of PowerHA. Things are working great. However in the interest of time during cut over to the new system, I was hoping to... (4 Replies)
Discussion started by: j_aix
4 Replies
LEARN ABOUT OPENDARWIN
wipefs
WIPEFS(8) System Administration WIPEFS(8)
NAME
wipefs - wipe a signature from a device
SYNOPSIS
wipefs [options] device...
wipefs [--backup] -o offset device...
wipefs [--backup] -a device...
DESCRIPTION
wipefs can erase filesystem, raid or partition-table signatures (magic strings) from the specified device to make the signatures invisible
for libblkid. wipefs does not erase the filesystem itself nor any other data from the device.
When used without any options, wipefs lists all visible filesystems and the offsets of their basic signatures. The default output is sub-
ject to change. So whenever possible, you should avoid using default outputs in your scripts. Always explicitly define expected columns
by using --output columns-list in environments where a stable output is required.
wipefs calls the BLKRRPART ioctl when it has erased a partition-table signature to inform the kernel about the change.
Note that some filesystems and some partition tables store more magic strings on the device (e.g. FAT, ZFS, GPT). The wipefs command
(since v2.31) lists all the offset where a magic strings have been detected.
When option -a is used, all magic strings that are visible for libblkid are erased. In this case the wipefs scans the device again after
each modification (erase) until no magic string is found.
Note that by default wipefs does not erase nested partition tables on non-whole disk devices. For this the option --force is required.
OPTIONS
-a, --all
Erase all available signatures. The set of erased signatures can be restricted with the -t option.
-b, --backup
Create a signature backup to the file $HOME/wipefs-<devname>-<offset>.bak. For more details see the EXAMPLES section.
-f, --force
Force erasure, even if the filesystem is mounted. This is required in order to erase a partition-table signature on a block device.
-h, --help
Display help text and exit.
-J, --json
Use JSON output format.
-n, --noheadings
Do not print a header line.
-O, --output list
Specify which output columns to print. Use --help to get a list of all supported columns.
-n, --no-act
Causes everything to be done except for the write() call.
-o, --offset offset
Specify the location (in bytes) of the signature which should be erased from the device. The offset number may include a "0x" pre-
fix; then the number will be interpreted as a hex value. It is possible to specify multiple -o options.
The offset argument may be followed by the multiplicative suffixes KiB (=1024), MiB (=1024*1024), and so on for GiB, TiB, PiB, EiB,
ZiB and YiB (the "iB" is optional, e.g. "K" has the same meaning as "KiB"), or the suffixes KB (=1000), MB (=1000*1000), and so on
for GB, TB, PB, EB, ZB and YB.
-p, --parsable
Print out in parsable instead of printable format. Encode all potentially unsafe characters of a string to the corresponding hex
value prefixed by 'x'.
-q, --quiet
Suppress any messages after a successful signature wipe.
-t, --types list
Limit the set of printed or erased signatures. More than one type may be specified in a comma-separated list. The list or individ-
ual types can be prefixed with 'no' to specify the types on which no action should be taken. For more details see mount(8).
-V, --version
Display version information and exit.
EXAMPLES
wipefs /dev/sda*
Prints information about sda and all partitions on sda.
wipefs --all --backup /dev/sdb
Erases all signatures from the device /dev/sdb and creates a signature backup file ~/wipefs-sdb-<offset>.bak for each signature.
dd if=~/wipefs-sdb-0x00000438.bak of=/dev/sdb seek=$((0x00000438)) bs=1 conv=notrunc
Restores an ext2 signature from the backup file ~/wipefs-sdb-0x00000438.bak.
AUTHOR
Karel Zak <kzak@redhat.com>
ENVIRONMENT
LIBBLKID_DEBUG=all
enables libblkid debug output.
SEE ALSO
blkid(8), findfs(8)
AVAILABILITY
The wipefs command is part of the util-linux package and is available from https://www.kernel.org/pub/linux/utils/util-linux/.
util-linux December 2014 WIPEFS(8)