Superblock issue

Looking for a little guidance from the gurus.
Unable to get our V480 to boot. Booted single user from cdrom. When I run fsck on the root file system I get a bad superblock error and am not able to repair it.
So I try to find alternate superblocks and get the following error:
# newfs -Nv /dev/rdsk/c0t0d0s0
mkfs -F ufs -o N /dev/rdsk/c0t0d0s0 640 640 1 8192 1024 16 10 5 2048 t 0 -1 8 16 n
mkfs: bad value for size: 640 must be between 1024 and 640
mkfs: size reset to default 640
Warning: inode blocks/cyl group (42) >= data blocks (42) in last cylinder group. This implies 640 sector(s) cannot be allocated.
/dev/rdsk/c0t0d0s0: 0 sectors in 0 cylinders of 1 tracks, 640 sectors 0.0MB in 0 cyl groups (16 c/g, 5.00MB/g, 2432 i/g)
super-block backups (for fsck) at:
<blank>
I am a bit stumped. Been looking all over the web, man pages and anything else I can find.
Any ideas would be greatly appreciated.

Hi,
Please try this, would help you......
#newfs -N /dev/rdsk/c0t0d0s7
it will generate the identical superblock.
then run.......
#fsck -o b=535952 /dev/rdsk/c0t0d0s7
all the best
Bhupal

Similar Messages

Authorization issues since 7.3.2

Since upgrading to iTunes 7.3.2 I've been having issues with purchased content. I'm asked to authorize my computer, which was previously authorized and now uses up an additional slot of my 5 allowed. When I try to play a movie, I'm asked to authorize again, and then it errors out saying I need iTunes 4.0 or later to play back the video. Syncing purchased items to my iPod or iPhone only allow a video with 0:00 total time to play and music just skips ahead to the next track.
I've tried deauthorizing and reauthorizing several times and reinstalling iTunes. I've also run the Disk Utility and checked my hdd is fine (everything checked out), so I'm kind of stuck at the moment.
Any ideas?

monzer4819 wrote:
Thank you for this post. Same problem, same drive. Assuming you leave your server on 24/7, I'm guessing you bought your drive 5 days before me
Did the firmware correct the issue?
Hehe cool and yes all sorted now
Only ill effect was having to run a full recovery on the separate RAID in the system which lost its superblocks or something due to IO completely dying so many times during rebuilds.

Slow startup and password issue.

Hi all...
Happy new year...!
As a little christmas present for myself I purchased a Crucial M4 256GB SSD for my MacPro 4,1 (2.26GHz, 22GB RAM, 10.8.2). I'm a semi-pro photographer and wanted a bit of a speed up for my processing etc etc. So yesterday I cloned my existing system drive to the SSD with Carbon Copy Cloner. I then installed the SSD in the spare superdrive bay (my other 4 bays are used).
Just as a background my previous startup/shutdown times on this machine where quite slow averaging around 90s for startup and around 45s for shutdown. I had assumed that this was normal and was just a slow syetm HD issue. When I changed the startup disk to the new SSD and booted up the startup time did decrease but not significantly... its now exactly 59s whilst the shutdown times go down to around 30s. In use the speed of the OS is massively improved with applications and local file copying blazingly fast. I've a few friends who upgraded MacBook Pro's and others macs with SSD's and their startups are around 10-15 seconds....!!! I'm not overly bothered by the slow startups/shutdowns but I am curious as to what might be causing these delays. In testing today I deleted everything unecessary from my user account startup items, disabled various apps and checked the /library/startupitems for anything that shoudnt be there. After a couple of hours trying I cant find anything that is effecting the startups and am lost. I'll likely just accept it and move on as in use the SSD is impressive but if anyone has any ideas it'd be appreciated!
A second thing that has happened is that whenever I try to delete/modify/move an app I am now asked to type in my user password. I have tried repairing permissions, checking the permissions of my .Trash folder etc etc but as of yet nothing has worked. Any ideas...??
Many thanks and Happy New Year yet again.
Richie

The traditional way an Operating System deals with "deleted" files is to remove ONLY the Directory information and simply add the data blocks to the free pool. Those "deleted" data blocks are not cleared.
This works in rotating drives because:
1. The logical block size is the same or larger than the physical drive block size.
2. Rotating magnetic media are block-for-block re-writable.
In SSDs physical blocks are much larger "superblocks", and re-writing a portion of a superblock is a slow and difficult read-modify-write operation. In addition, since the OS did not notify the drive what data are no longer needed, deleted data continue to be carefully maintained and re-written by the drive. Soon every write operation becomes a read-modify-write, and performance deteriorates.
In my opinion, this nearly-full condition is likley to cause drive failure. Something more than wishful thinking is required.
Apple enables TRIM on the drives they install directly. They do not do so for third-party drives, but that is likely because those drives have not been tested by Apple.
I have been using a very small SSD as a boot drive for a while, and periodically consolidate free space followed immediately by erasing free space with a third-party utility. I believe this has kept me out of trouble. My son has been using SSD in his laptop and doing nothing for maintenece, and he has killed two drives in a year.
Trim Enabler utility from groths seems to be working, and makes things simple. Your mileage may vary.
if I notice significant performance slips
You added a much lower latency drive and startup times did not improve significantly. Much of the time required for startup is needed for memory testing. The rest is largely attributable to disk Read/Write times. What more evidence do you need?

Mounting issues after kernel update (2.6.25)

After installing the recent kernel update, mounting has gone haywire. When I put in a cd (in either of my 2 drives) it doesn't mount. In thunar, when I click on the cd drive, it displays this error:
mount: wrong fs type, bad option, bad superblock on /dev/sr0,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
I did dmesg | tail and I got this:
EXT3-fs: mounted filesystem with ordered data mode.
Adding 1044216k swap on /dev/sda5. Priority:-1 extents:1 across:1044216k
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
ivtv0: Encoder revision: 0x02060039
[drm] Initialized drm 1.1.0 20060810
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:02.0 to 64
[drm] Initialized i915 1.6.0 20060119 on minor 0
UDF-fs: No VRS found
Also, when booting a few minutes ago, it was stuck on the "checking filesystems" for a few minutes, when it usually does that step almost immediately. I also couldn't mount an iso, this is what happened:
[root@eric-arch eric]# mount -o loop -t iso9660 /path/to/iso.iso /mnt/iso2
mount: could not find any device /dev/loop#
Note: I am not certain that it was caused by the kernel update, but that is the only thing I did to my machine before this started happening.
Please help asap because I need to do schoolwork which is on a cd.

jealma wrote:I know the solution to the /dev/loop-problem. The new 2.6.25 kernel has the loop device as a module. Please try a `modprobe loop`, that gives you a /dev/loop. I don't know whether that will be persistent after a reboot, so you may need to add "loop" to the modules-list in /etc/rc.conf.
That worked, but I still have other issues with cd mounting, so I downgraded my kernel for now.

Superblock.. make my system unstable.

Yo, i tried a install in an old computer and superblock cause gnome to have serious issues and partition are almost broken..
i don't understand what to do with them..
Gparted before partioning : http://i.imgur.com/8L35M0A.png
Gparted when partionnated : http://i.imgur.com/y5RODDU.png
I get space used ,, when i clearly have nothing ..
I tried
dd if=/dev/zero of=/dev/sda
Not deleting the superblocks..
So i did :
mke2fs -n /dev/sda
/dev/sda is entire device, not just one partition!
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
61054976 inodes, 244190646 blocks
12209532 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
7453 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
i did :
e2fsck -b 32768 /dev/sda
e2fsck 1.42.8 (20-Jun-2013)
e2fsck: Bad magic number in super-block while trying to open /dev/sda
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
I wanna remove them from backing up in my partion, or repair them..
Edit : i think, i posted in a wrong section, 1000 sorry.
Last edited by localhostabc (2013-08-31 04:54:32)

i finaly found how to use e2fsck
I created a full ext4 partiition and run multiple command
e2fsck <SUPERBLOCK> /dev/sda1

[SOLVED] "The superblock could not be read..."

Good Evening.
In the beginning, I want to apologise if my English isn't as correct and comprehensible as I want it to be.
I am rather clueless Linux user with penchant for learning. I have used Slackware for some time, but I wanted to try out Arch because of it's superior package management, rolling release system and minimalism. I read through installation guides, and performed basic installation using 2009.08 CD without any problems. When I tried to boot into my new system I got following message:
:Mounting Root Read-only [DONE]
:Checking Filesystems [BUSY]
/dev/hda1:
and then
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock is corrupt and you might try running e2fsck with an alternate superblock:
e2fsck -b -8193 <device>
and finally
FILESYSTEM CHECK FAILED
Please repair manually and reboot. Note that the root file system is currently mounted read-only. To remount it read-write type:
mount -n -o remount,rw /
When you exit the maintenance shell the system will reboot automatically.
I tried to run fsck, of course, as well as e2fsck or remounting / read-write but I always got the second message "The superblock could not be read... etc.".
My partitioning scheme is kinda tricky, because I make no distinction beetween production and testing machine. What is interesting, when I wanted to look at it using cfdisk from my indispensable Knoppix DVD I got something like:
FATAL ERROR: Bad primary partition 0:
Partition ends in the final partial cylinder.
Press any key to exit cfdisk.
But when I tried with root privileges it worked, and my 80GB hard drive looks something like that:
hda1 Primary Linux ext3 (/)
hda2 Boot Primary NTFS
hda3 Primary Linux
hda5 Logical W95 FAT32
hda6 Logical BeOS fs
hda7 Logical Linux ext2 (boot)
hda8 Logical Linux ReiserFS (tmp)
hda9 Logical Linux ReiserFS (usr)
hda10 Logical Linux ReiserFS (var)
hda11 Logical Linux ext3 (home)
hda12 Logical Linux Swap/Solaris (swap)
Only hda1, hda7, hda8, hda9, hda10, hda11 and hda12 are part of my Arch installation. I'm currently booting Windows XP through GRUB from NTFS partition (hda2) too.
Does anyone know how to make my Arch working installation?
Last edited by Schirase (2010-07-14 13:14:03)

My bad, I actually didn't read Begginers' Guide very carefully. I didn't realize that setting this UUIDs in fstab is so important. Now my fstab looks something like that (mind that this is slightly different partitioning scheme):
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
UUID=7a6e9456-69d4-4346-bf4d-803e5f61f100 / ext3 defaults,noatime 0 1 #/dev/hda5
UUID=bf4e4d66-2658-4e39-b1f8-b84cc157ba72 /boot ext2 defaults 0 2 #/dev/hda6
UUID=d3a5e92f-454e-47f9-8bfa-86804a322e55 /tmp reiserfs defaults,notail 0 2 #/dev/hda7
UUID=5333292d-4f3d-45a9-aa44-9df8c930244b /usr reiserfs defaults,notail 0 2 #/dev/hda8
UUID=bb25bd08-eeaa-4732-93a6-87e238c06029 /var reiserfs defaults,notail 0 2 #/dev/hda9
UUID=38298476-ea3d-4d15-a5d2-8c221a20ebe8 swap swap defaults 0 0 #/dev/hda10
UUID=de1d9d94-09ef-4429-b63e-fddea5e81195 /home ext3 defaults,noatime 0 2 #/dev/hdb1
and I am happily using Arch right now. However, I have got strange non-critical issues with partitions and disks which I explained in http://bbs.archlinux.org/viewtopic.php? … 82#p791582.

[fsck] Superblock last write time is in the future

Hello,
I have HARDWARECLOCK="localtime" in my rc.conf but every time I reboot I get the below fsck error
Superblock last write time is in the future
then I am required to enter root password to get a shell. I usually fix the issue by remounting the root partition as read-write and rebooting. Strangely, on next reboot fsck will fix the issue, run a complete fsck and then give me my Arch Linux.
Some notes:
1) I have always had this last write time issue, but previously (1 month ago?) fsck just fixed it and continued the boot process, didn't stop asking me the root password
2) if I use 'rw' in the kernel command-line I can never boot because it always stops asking for root password, even after running fsck through a livecd, so I am currently using 'ro'
Has somebody any clue about this problem?
My relevant fstab line is:
LABEL=LINUX / ext3 defaults,noatime 0 1
Thanks
Last edited by legolas558 (2009-10-06 10:59:43)

Ramses de Norre wrote:I encountered this too and I worked around it by setting my bios clock to my system time, it was a month off. I never encountered this issue before though and I guess this is a bug in some program (fsck?).
So until this is fixed, try setting your bios clock to the same time your system's at. And maybe file a bug.
This is not a solution! There is a reason if I keep localtime in my system, and no I am not going to change it because of a bug. That's Windows solutions, not Linux.
Some bug reports found with uncle Google:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540575
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343662
https://bugs.launchpad.net/ubuntu/+sour … bug/427822

Raid5 issue after upgrade

TLDR = scared to death to answer 'yes' to the following from e2fsck:
Superblock has an invalid journal (inode 8).
Clear<y>? cancelled!
After upgrading to linux 3.2.14-1 (along with others important packages like udev, mkinitcpio, etc) my raid5 array would not assemble. I don't have the original message but after two days have passed and watching the forums I'm sure it was related to this: https://bugs.archlinux.org/task/29344
Anyways I'm past that issue and am now having filesystem problems with my raid array after recreating. Note I'm currently using
filesystem 2012.2-2
linux 3.2.14-1
mkinitcpio 0.8.5-1
udev 181-5
During the past two days of tinkering I've never let fsck touch the filesystem nor have I done anything like mkfs on it either. Only thing I've done is re-create the array using mdadm and then seeing if I can mount it.
The raid5 array contains /dev/sdb1 /dev/sdc1 and /dev/sdd1. My initial though was thinking that somehow maybe the drive labels got renamed during the kernel upgrade so I've tried re-creating the array will all six possible permutations of the disks. Nothing worked. I know the original order was sdb1/sdc1/sdd1.
Here is the dumpe2fs info for each of the disks:
# dumpe2fs /dev/sdb1
dumpe2fs 1.42.1 (17-Feb-2012)
Filesystem volume name: <none>
Last mounted on: /mnt/raid
Filesystem UUID: 08bb1bfd-4932-494a-93ba-fe8fd37ea22c
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 122101760
Block count: 488379968
Reserved block count: 488379
Free blocks: 106448913
Free inodes: 121612868
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 907
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
RAID stride: 16
RAID stripe width: 32
Filesystem created: Thu Oct 8 23:09:57 2009
Last mount time: Mon Apr 2 10:19:36 2012
Last write time: Fri Apr 6 19:15:06 2012
Mount count: 13
Maximum mount count: 38
Last checked: Sun Oct 30 06:54:03 2011
Check interval: 15552000 (6 months)
Next check after: Fri Apr 27 06:54:03 2012
Lifetime writes: 12 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 84ce591f-34ae-43d0-846c-d8dae91ef4b9
Journal backup: inode blocks
dumpe2fs: A block group is missing an inode table while reading journal inode
# dumpe2fs /dev/sdc1
dumpe2fs 1.42.1 (17-Feb-2012)
dumpe2fs: Bad magic number in super-block while trying to open /dev/sdc1
Couldn't find valid filesystem superblock.
# dumpe2fs /dev/sdd1
dumpe2fs 1.42.1 (17-Feb-2012)
dumpe2fs: Filesystem revision too high while trying to open /dev/sdd1
Couldn't find valid filesystem superblock.
When I create the array I see the following from mdadm. Which is expected as it sees the existing filesystem:
# mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 --metadata=0.90 /dev/sdb1 /dev/sdc1 /dev/sdd1
mdadm: layout defaults to left-symmetric
mdadm: chunk size defaults to 512K
mdadm: layout defaults to left-symmetric
mdadm: /dev/sdb1 appears to contain an ext2fs file system
size=1953519872K mtime=Mon Apr 2 10:19:36 2012
mdadm: /dev/sdb1 appears to be part of a raid array:
level=raid5 devices=3 ctime=Sun Apr 8 10:01:02 2012
mdadm: layout defaults to left-symmetric
mdadm: /dev/sdc1 appears to be part of a raid array:
level=raid5 devices=3 ctime=Sun Apr 8 10:01:02 2012
mdadm: layout defaults to left-symmetric
mdadm: /dev/sdd1 appears to contain an ext2fs file system
size=2066852100K mtime=Sat Apr 7 05:08:08 2029
mdadm: /dev/sdd1 appears to be part of a raid array:
level=raid5 devices=3 ctime=Sun Apr 8 10:01:02 2012
mdadm: size set to 976759808K
Continue creating array? y
mdadm: array /dev/md0 started.
The raid array is created without issue:
# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sdb1[0] sdd1[2] sdc1[1]
1953519616 blocks level 5, 512k chunk, algorithm 2 [3/3] [UUU]
# mdadm --detail /dev/md0
/dev/md0:
Version : 0.90
Creation Time : Sun Apr 8 14:56:14 2012
Raid Level : raid5
Array Size : 1953519616 (1863.02 GiB 2000.40 GB)
Used Dev Size : 976759808 (931.51 GiB 1000.20 GB)
Raid Devices : 3
Total Devices : 3
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Sun Apr 8 18:07:19 2012
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
UUID : fe541eb6:764599e3:5d64d1b1:6d03292e (local to host jackshrimp)
Events : 0.19
Number Major Minor RaidDevice State
0 8 17 0 active sync /dev/sdb1
1 8 33 1 active sync /dev/sdc1
2 8 49 2 active sync /dev/sdd1
# mdadm --examine --scan
ARRAY /dev/md0 UUID=00000000:00000000:00000000:00000000
spares=1
ARRAY /dev/md0 UUID=fe541eb6:764599e3:5d64d1b1:6d03292e
This is how I originally created the filesystem on the array (back in 10/2009). Here with "-n" to show the superblock locations:
# mkfs.ext3 -n -v -m .1 -b 4096 /dev/md0
mke2fs 1.42.1 (17-Feb-2012)
fs_types for mke2fs.conf resolution: 'ext3'
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=16 blocks, Stripe width=32 blocks
122101760 inodes, 488379904 blocks
488379 blocks (0.10%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
14905 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
I've tried running e2fsck with (-b) each of those blocks and none worked. Here is what I get from e2fsck:
# e2fsck /dev/md0
e2fsck 1.42.1 (17-Feb-2012)
e2fsck: Group descriptors look bad... trying backup blocks...
e2fsck: Filesystem revision too high when using the backup blocks
e2fsck: going back to original superblock
e2fsck: Group descriptors look bad... trying backup blocks...
e2fsck: Filesystem revision too high when using the backup blocks
e2fsck: going back to original superblock
Superblock has an invalid journal (inode 8).
Clear<y>? cancelled!
e2fsck: Illegal inode number while checking ext3 journal for /dev/md0
/dev/md0: ********** WARNING: Filesystem still has errors **********
While I'm quite sure the data is still there I'm freaking out about letting fsck do anything!
Should I let fsck do what it want to do? Any thoughts on how I can recover this array? Any suggestions on other things I should try?
Thanks for any and all help.

Then it looks similar to bug 6651232
May I suggest you get in touch with Oracle support for this?

What is the correct fsck syntax for issue with invisible disk ?

Hello everybody,
My problem actually (I also have a problem with the 17" Install DVD) is to repair *3 disks* with *fsck command*, as the filesystems are damaged. I phoned Apple Assistance Saturday, for about 30 minutes, but finally the Advisor sent me a link to one of their thousands (and sometimes obsolete) articles, and the solution wasn't there entirely.
I'll describe you the problem :
One of my USB external disks (4TB data) *doesn't appear* after Startup, but when I use the Install DVD and Disk Utility, the application tells me it's OK, that the disk "SEEMS" to be alright etc. That's false.
When I reboot with *Cmd + S* (root level), and tell Terminal (I have been obliged to print the four states of an American Extended keyboard) :
"sudo fsck -fy /dev/disk4s1"
the reply is :
"BAD SUPER BLOCK: MAGIC NUMBER WRONG
LOOK FOR ALTERNATE SUPERBLOCKS? yes
SEARCH FOR ALTERNATE SUPER-BLOCK FAILED. YOU MUST USE THE
-b OPTION TO FSCK TO SPECIFY THE LOCATION OF AN ALTERNATE
SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(8)."
So, I use the *-b option* of *fsck command*, and :
"fsck: -b flag *requires a number*"
"-b size Specify the size, in bytes, of the physical blocks used by
the -B option."
So, I'm searching *since 3 days* (and *I'm learning a lot*, but nothing, of course, concerning my problem) the full info command to know *what sector address* I have to tell to -b to install an alternate superblock, because I need to know exactly at which places filesystems and *data start* and end.
You understand, I suppose, that I can't use any of my softwares, because the disk is INVISIBLE (doesn't exist) after normal restarting.
It's not MOUNTED nor UNMOUNTED.
It exists (very well, thank you) when rebooting *with Apple Install DVD*.
I'm under *Snow Leopard 10.6.5*, and I don't know if, perhaps,
*there wouldn't be a problem* (or more) with this update ...
That's what I've seen, in any case, on other places here,
about several different issues.
Please, Bob, Gary, Camelot, etresoft, Bill, Jun, Nils, Cole, Charles, Michael,
gimme some help !
If someone has the full solution, a beginning of solution,
or a path to solution,
thank you very, very much in advance !
With my best regards
Vialatte

Dear Camelot,
First, thank you very much for answering me and try to help me ;
Secundo, please read, if you have time, what I replied to Bill Scott,
and I have to thank you also for your slightly better contribution and understanding.
Some words of what I've replied to him are written for you too :
"I type *sudo fsck -fy /dev/disk4s2* (not s1, of course, and *Camelot is perfectly right*, having remarked this mistake, as *s1 is dedicated to partition map* volumes).
There's also *a strange thing* with Disk Utility when starting from DVD :
it doesn't display the s1 volumes as usual."
As you've read it in my reply to Bill, it's a *complicated issue* and *Apple has no response*.
You tell me : "+Good luck with that.+" It starts badly.
"+It's been a long time since I've had to deal with superblocks+"
I totally ignored their existence …
"+- they just don't come up any more,+" What is the meaning of this sentence ?
"+but I don't know any way of recovering the superblock address after a disk has failed.+" That's the matter of my question : *Is it a failure ?*
"+Typically (at least, historically) you get the superblock addresses in advance, storing them somewhere safe until you need them.+"
That's a total discovery for me.
You tell me then : "+Are you talking about in the Finder here?+" Yes and no, I talk about the Sidebar (see below), but it's part of the Finder.
"+Have you checked the Finder's preferences to make sure it's just not hiding external drives?+" I did, when you told me to do so.
"+Since everything else tells you that the drive is OK+" Yes, you're right, when starting from Install DVD, that's *very strange*, but remember fsck doesn't say *the same at all* as Disk Utility ... "+this just sounds like a Finder preference setting to me.+"
I'm sorry, it would have been wonderful. My settings are correct, that means :
NOTHING on Desktop, ALL (including Computer) in the Sidebar (and clicking on Computer allows me to check that *no volume* has vanished from Sidebar (it happens sometimes).
"+If it's not the Finder prefs, then please post the output of diskutil list in order to troubleshoot further.+"
Here it is (a little far below), but there's *none of the 2 4TB volumes* (yes, there are two disks missing now) here, because, as I already said that, they are invisible for the Finder and *Disk Utility*, and I think *it's the same for Terminal.*
You'll note there's *no BOOTCAMP partition* here (I removed it temporarly to solve this issue), and don't be afraid if there are several systems on the internal HD.
As I noticed it here and there, there are problems with 10.6.5.
So, I try to work with 10.6.4 (delivered with MBP 17"), but have also an universal 10.6.0 Snow Leopard, with which I can configurate 10.6 *at any state*.
Unfortunately, I *can't use* (it so that Apple decided to do) the DVD delivered with my 15" MBP (rejected by 17"), because it is with my MBP 15" that I formatted those disks.
*Another thing :* If I didn't want my wife *to install herself* (with me to help her) the 15" MBP I've gave to her (there's the 17" new 500GB 5400rpm installed in it by me), I would already have tried to connect these two 4TB, just to see.
Last login: Fri Nov 26 21:22:38 on ttys005
sys171064:~ OH$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *500.1 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Seagate 149.9 GB disk0s2
3: Apple_HFS System 17 64.9 GB disk0s3
4: Apple_HFS Sys171064 34.9 GB disk0s4
5: Apple_HFS For Alu Black System 149.6 GB disk0s5
6: Apple_HFS SL 10.6.x 100.0 GB disk0s6
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Applepartitionscheme *16.1 GB disk1
1: Applepartitionmap 32.3 KB disk1s1
2: Apple_HFSX olivier_herrbach 16.1 GB disk1s2
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *1.0 TB disk2
1: EFI 209.7 MB disk2s1
2: Apple_HFS HSD 01 TM 600 Go 599.9 GB disk2s2
3: Apple_HFS HSD 01 400 Go 120.6 GB disk2s3
4: Apple_HFS DiskTools > Seagate ... 279.1 GB disk2s4
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *1.5 TB disk3
1: EFI 209.7 MB disk3s1
2: Apple_HFS HELP ÉNERGIE 1,5 To 1.5 TB disk3s2
/dev/disk4
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *1.0 TB disk4
1: EFI 209.7 MB disk4s1
2: Apple_HFS HSD USB 03 1To 999.9 GB disk4s2
/dev/disk5
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *32.0 GB disk5
1: EFI 209.7 MB disk5s1
2: Apple_HFS Patriot USB Key 32 Go 31.7 GB disk5s2
/dev/disk6
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *1.5 TB disk6
1: EFI 209.7 MB disk6s1
2: Apple_HFS WD USB 1,5 To 1.1 TB disk6s2
3: Apple_HFS WD 02 350 Go Seagate 349.9 GB disk6s3
/dev/disk7
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *1.0 TB disk7
1: EFI 209.7 MB disk7s1
2: Apple_HFS HSD USB 02 50 Go 49.9 GB disk7s2
3: Apple_HFS HSD USB 02 715 Go 714.6 GB disk7s3
4: Apple_HFS HSD USB 02 110 Go 110.0 GB disk7s4
5: Apple_HFS HSD USB 02 100 Go 99.9 GB disk7s5
/dev/disk8
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *2.0 TB disk8
1: EFI 209.7 MB disk8s1
2: Apple_HFS WD USB 2To 2.0 TB disk8s2
/dev/disk9
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *2.0 TB disk9
1: EFI 209.7 MB disk9s1
2: Apple_HFS FW 03 TM 2To 2.0 TB disk9s2
/dev/disk10
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *1.5 TB disk10
1: EFI 209.7 MB disk10s1
2: Apple_HFS FW 02 1,2 To 1.2 TB disk10s2
3: Apple_HFS FW 02 200 Go 199.9 GB disk10s3
4: Apple_HFS FW 02 CS5MC 50 Go 49.9 GB disk10s4
5: Apple_HFS FW 02 Leopard 50 Go 50.0 GB disk10s5
/dev/disk11
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *2.0 TB disk11
1: EFI 209.7 MB disk11s1
2: Apple_HFS FC 02 Time Machine 1.0 TB disk11s2
3: Apple_HFS FC 02 SL 1To 999.5 GB disk11s3
/dev/disk12
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *2.0 TB disk12
1: EFI 209.7 MB disk12s1
2: Apple_HFS FC 01A USB 1To 700.0 GB disk12s2
3: Apple_HFS FC 01C 300 Go Leo 299.9 GB disk12s3
4: Apple_HFS FC 01B USB 1To 699.8 GB disk12s4
5: Apple_HFS Leopard 125 Go 300.0 GB disk12s5
/dev/disk13
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *2.0 TB disk13
1: EFI 209.7 MB disk13s1
2: Apple_HFS FW 04 TM 2To 2.0 TB disk13s2
3: Apple_HFS eDrive 12.9 GB disk13s3
/dev/disk14
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *2.0 TB disk14
1: EFI 209.7 MB disk14s1
2: Apple_HFS FW 05 2To 2.0 TB disk14s2
sys171064:~ OH$
As you and I see, I strongly believe that disk15s2 and disk16s2 (with s3, s4, s5 etc. partitions) are missing.
I must find a way to prove what I say to you. Remember that we are not in the case where I use *Cmd + s* after rebooting with Install DVD, but under normal utilisation. What follows has no interest :
Last login: Fri Nov 26 21:23:55 on ttys006
sys171064:~ OH$ sudo fsck -fy /dev/disk15s2
Password:
/dev/disk15s2: No such file or directory
Can't stat /dev/disk15s2
Can't stat /dev/disk15s2: No such file or directory
sys171064:~ OH$
So, I will now restart my MacBook Pro with Mac OS X 10.6.4 Install DVD, and go :
—1 in *Disk Utility* ;
—2 in Terminal (with *Cmd + s*).
I'll *note all* what I see, and then write you what I found.
You'll be nice to tell me if there's a way, in these conditions,
a) to *save Disk Utility log* ; or/and
b) to *save Terminal Output(s)* (.txt) ; or/and
c) to *take and save screenshots*, ; or/and
d) to *print anything*. (?)
as I don't know how it's possible to save these informations.
Thank you once more for your help. I'll do things now, but as it is 23:02 here in France, maybe I won't write you till tomorrow.
But, if you can answer to a), b), c) or d) above, post it to me please, because I'll go back here tonight.
And, also, *but I don't want to bore you*, I'd like to learn how to *copy and paste parts of messages* as you did, and how to *insert a Grab item (.png)* in a discussion, because an image is better than thousand words (that's what we say in France, but I'm sure we are not alone on Earth — like in the Universe).
With my best regards
Vialatte

Filesystem check failed + monitor issues = problematic combo.

Hi,
I've been using arch for a while but I still lack PLENTY of knowledge and linux feels like a stranger to me. (btw: now I'm writing from my wind, which has never troubled me with arch). My PC is driving me crazy. Randomly stops booting on "The superblock could not be read or does not describe a correct ext2 filesystem" (I've got ext3, so it's a bit weird?) but when I reboot everything comes back to normal. It's a fresh install (64bit finally) done from cd and arch complained about /dev/sr0 reading problems, but finally installed itself. I've always did it from usb stick. Can this have something to do with bad superblock or w/e?
What's more I've got some trouble with my screen which has jumping pixels. When I've unplugged stuff from usb ports and plugged it back it seemed to help, tried changing monitor cable, helped for a while, now I switched to built in vga card and no trouble yet. What would you do? Cause I'm not sure if it's not because of mainboard, which has problems with usb ports, graphic card or screen itself.
Last edited by muchzill4 (2009-08-25 07:16:01)

But what is the command? mkinitcpio -p kernel26 ? Also how do I fix this grub issue? I'm assuming grub created a default menu.lst after I copied the config files and setup the hd0 but I actually don't recall checking that.
Just re-did all steps including rebuilding the kernel, I still can't get the boot menu when I reboot. It goes directly to grub console.
I checked the generated menu.lst, it lists my root as the device where /boot partition is and the kernel line root enrty is defined for the arch system I want to boot :\
Last edited by Grimn (2011-05-31 17:50:02)

Reformat external hard drive - "bad superblock", "magic number wrong" error

i was just given a brand new 300GB USB hard drive, however, as it came NTFS-formatted, immediately after plugging it in for the first time, i fired up Disk Utility, and attempted to format it with UFS.
The problem arose when the progress bar just sat there for an hour at a constant 5%. Assuming the program had stalled (it hadn't...though it would have sat there indefinitely), i quit Disk Utility, opened it back up, and again attempted to format the drive--only this time, almost immediately the program output:
BAD SUPER BLOCK: MAGIC NUMBER WRONG
LOOK FOR ALTERNATE SUPERBLOCKS? yes
SEARCH FOR ALTERNATE SUPER-BLOCK FAILED. YOU MUST USE THE
-b OPTION TO FSCK TO SPECIFY THE LOCATION OF AN ALTERNATE
SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(8).
i opened up Terminal and tried manually to find an alternate superblock, to no avail.
fsck -b32 /dev/disk2s3
i've been unable to find any solutions to this issue online, but i'd really like to use my drive i've heard that this problem has to do with hardware that's about to fail, however, this is a brand new drive, and i'm quite certain the error is as a result of the aborted reformat operation.
Does anyone know how to remedy this? Thanks in advance.

Hello TheRedWino, and a warm welcome to the forums!
Hmmm, what kind of Case/Chipset does it have?
Have you tried erasing it with Zeros one Pass?
"Disk Utility
1. Insert the Mac OS X Install disc that came with your computer, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the Erase tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume, then choose MacOS Extended Journalled, select the Partition tab.
6. Click Erase & look for Security Options. choose Zero 1 pass."
Formatting & Partitioning a Hard Drive in OS X - Tiger and Leopard...
http://www.kenstone.net/fcphomepage/partitioningtiger.html

[SOLVED] Superblock has invalid ext3 journal after change of VMSPLIT

I'm not sure if this is the appropriate forum for this, but here goes..
I recently recompiled a custom kernel (toofishes' Eee kernel) which had NOHIGHMEM=y and VMSPLIT2G=y, enabling highmem and changing the split back to VMSPLIT3G. However, when it came to booting it, my login manager never popped up and instead I got a tty. Logging in gave me this output:
/bin/ls: /lib/librt.so.1: unsupported version 372 of Verdef record
and when I try to start X:
xauth: creating new authority file /home/jickel/.serverauth.1892
/usr/bin/X: error while loading shared libraries: libm.so.6: ELF load command alignment not page-aligned
giving up.
xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error.
Plus some segfaults when quitting. It seems I did not configure the new memory setting properly, though I did remember to change the CONFIG_PAGE_OFFSET_ VALUE at least.
Now when I try to boot using the default arch kernel to replace the faulty kernel, the file system check fails, and when I manually run fsck I get this question:
Superblock has an invalid ext3 journal (inode 8).
Clear<y>?
I'm still pretty new to Linux, but it seems the change of memory might have forced a change in the FS journal. No idea where to go from here though, and I that answering yes to the above might hose my FS. What do you suggest I do? I recently backed up my system, luckily.
Last edited by Jickel (2008-07-08 20:10:30)

I did it manually, I'll try doing it the other way later then. Thanks for the advice!
I guess those segfaults must have damaged the journals then. I'm still not sure how to repair this though.
UPDATE: Well I deleted the journal, had the file system repaired, and had a new journal created. The fsck command reports everything is fine now, but I still get the "FILE SYSTEM CHECK FAILED - Please repair manually and reboot" box-thingy when I try to reboot. Any idea how do progress from here? I need a working system to update the kernel back to a working one.
Oh, I found another thread where the OP has the same issue http://bbs.archlinux.org/viewtopic.php?pid=385792 . I'll go through the solutions suggested there and see if anything works. No word on results in that thread though.
Last edited by Jickel (2008-07-08 05:37:44)

Mount.ocfs2: Bad magic number in superblock on RAC Node2

Everytime I try to start ocfs2 or mount a filesystem on node2, I get the following error:
"mount.ocfs2: Bad magic number in superblock while opening device /dev/sdb1
uname -r : 2.6.9-78.0.1.ELsmp
[root@rac1 ~]# /etc/init.d/o2cb status
Module "configfs": Loaded
Filesystem "configfs": Mounted
Module "ocfs2_nodemanager": Loaded
Module "ocfs2_dlm": Loaded
Module "ocfs2_dlmfs": Loaded
Filesystem "ocfs2_dlmfs": Mounted
Checking O2CB cluster ocfs2: Online
Heartbeat dead threshold: 61
Network idle timeout: 30000
Network keepalive delay: 2000
Network reconnect delay: 2000
Checking O2CB heartbeat: Not active
Same filesystem is visible on node1. Any help is much appreciated

Hi Yuvaraj,
I am facing the same situation and the only difference is that I am abe to see ocfs2 mount point on rac1 node and in rac2 node, it is not viewable.
If you could send how to fix this issue, it will be very gr8ful and would appreciate your timely help.
My id : [email protected]
Rac2 Node
[root@rac2 tmp]# /etc/init.d/o2cb status
Module "configfs": Loaded
Filesystem "configfs": Mounted
Module "ocfs2_nodemanager": Loaded
Module "ocfs2_dlm": Loaded
Module "ocfs2_dlmfs": Loaded
Filesystem "ocfs2_dlmfs": Mounted
Checking O2CB cluster ocfs2: Online
Heartbeat dead threshold: 61
Network idle timeout: 30000
Network keepalive delay: 2000
Network reconnect delay: 2000
Checking O2CB heartbeat: Not active
Rac1 Node
[root@rac2 tmp]# /sbin/mounted.ocfs2 -d
Device FS UUID Label
[root@rac2 tmp]# /sbin/mounted.ocfs2 -f
Device FS Nodes
Rac1 Node

New DVR Issues (First Run, Channel Switching, etc.)

I've spent the last 30 minutes trying to find answers through the search with no luck, so sorry if I missed something.
I recently switched to FIOS from RCN cable in New York. I've gone through trying to setup my DVR and am running into issues and was hoping for some answers.
1. I setup two programs to record at 8PM, I was watching another channel at the time and only half paying attention. Around 8:02 I noticed a message had popped up asking if I would like to switch channels to start recording. I was expecting it to force it to switch like my old DVR, but in this case it didn't switch and I missed the first two minutes of one of the shows. I typically leave my DVR on all day and just turn off the TV, this dual show handling will cause issues with that if I forget to turn off the DVR. Is there a setting I can change that will force the DVR to choose one of the recording channels?
2. I setup all my recordings for "First Run" because I only want to see the new episodes. One show I setup was The Daily Show on comedy central, which is shown weeknights at 11pm and repeated 3-4 times throughout the day. My scheduled recordings is showing all these as planned recordings even though only the 11pm show is really "new". Most of the shows I've setup are once a week so they aren't a problem, but this seems like it will quickly fill my DVR. Any fixes?
Thanks for the help.
Solved!
Go to Solution.

I came from RCN about a year ago. Fios is different in several ways, not all of them desirable. Here are several ways to get--and fix--unwanted recordings from a series recording setup.
Some general principles.
Saving changes. When you originally create a series with options, or if you go back to edit the options for an existing series, You MUST save the Series Options changes. Pretty much everywhere else in the user interface, when you change an option, the change takes effect immediately--but not in Series Options. Look at the Series Options window. Look at the far right side. There is a vertical "Save" bar, which you must navigate to and click OK on to actually save your changes. Exiting the Series Options window without having first saved your changes loses all your attempted changes--immediately.
Default Series Options. This is accessed from [Menu]--DVR--Settings--Default Series Options. This will bring up the series options that will automatically be applied to the creation of a NEW series. The options for every previously created series will not be affected by a subsequent modification of the Default Series Options. You should set these options to the way you would like them to be for the majority of series recordings that you are likely to create. Be sure to SAVE your changes. This is what you will get when you select "Create Series Recording" from the Guide. When creating a new series recording where you think that you may want options different from the default, select "Create Series with Options" instead. Series Options can always be changed for any individual series set up later--but not for all series at once.
Non-series recordings. With Fios you have no directly available options for these. With RCN and most other DVRs, you can change the start and end times for individual episodes, including individual episodes that are also in a series. With Fios, your workarounds are to create a series with options for a single program, then delete the series later; change the series options if the program is already in a series, then undo the changes you made to the series options later; or schedule recordings of the preceding and/or following shows as needed.
And now, to the unwanted repeats.
First, make sure your series options for the specific series in question--and not just the series default options--include "First Run Only". If not, fix that and SAVE. Then check you results by viewing the current options using the Series Manager app under the DVR menu.
Second, and most annoying, the Guide can have repeat programs on your channel tagged as "New". It happens. Set the series option "Air Time" to "Selected Time". To make this work correctly, you must have set up the original series recording after selecting the program in the Guide at the exact time of a first run showing (11pm, in your case), and not on a repeat entry in the Guide. Then, even it The Daily Show is tagged as New for repeat showings, these will be ignored.
Third, another channel may air reruns of the program in your series recording, and the first showing of a rerun episode on the other channel may be tagged as "New". These can be ignored in your series if you set the series option "Channel" to "Selected Channel". Related to this, if there is both an SD and HD channel broadcasting you series program, you will record them both if the series option "Duplicates" is set to "Yes". However, when the Channel option is set to "Selected Channel", the Duplicates Option is always effectively "No", regardless of what shows up on the options screen.
As for you missing two minutes, I have sereral instances in which two programs start recording at the same time. To the best of my recollection, whenever the warning message has appeared, ignoring it has not caused a loss of recording time. You might have an older software version. Newest is v.1.8. Look at Menu--Settings--System Info. Or, I might not have noticed the loss of minutes. I regularly see up to a minute of previous programming at the start of a recording, or a few missing seconds at the beginning or end of a recording. There are a lot of possibilities for that, but the DVR clock being incorrect is not one of them. With RCN, the DVR clocks occasionally drifted off by as much as a minute and a half.

Pension issue Mid Month Leaving

Dear All,
As per rule sustem should deduct mid month joining/leaving/absences or transfer scenarios, the Pension/PF Basis will be correspondingly prorated. But our system is not doing this. In RT table i have found 3FC Pension Basis for Er c 01/2010                    0.00           6,500.00.
Employee leaving date is 14.04.2010. system is picking pension amout as 541. Last year it was coming right.
Please suggest.
Ashwani

Dear Jayanti,
We required prorata basis pension in case of left employees and system is not doing this. This is the issue. As per our PF experts Pension amount should come on prorata basis for left employees in case they left mid of month.System is doing prorata basis last year but from this year it is deducting 541. I am giving two RT cases of different years.
RT table for year 2010. DOL 26.04.2010
/111 EPF Basis              01/2010                    0.00           8,750.00
/139 VPF Basis              01/2010                    0.00           8,750.00
/3F1 Ee PF contribution     01/2010                    0.00           1,050.00
/3F3 Er PF contribution     01/2010                    0.00             509.00
/3F5 Ee Mon PF contribution 01/2010                    0.00           1,050.00
/3F6 Ee Ann PF contribution 01/2010                    0.00          12,600.00
/3F9 PF adm chrgs * 1,00,00 01/2010                    0.00              96.25
/3FA PF basis for Ee contri 01/2010                    0.00           8,750.00
/3FB PF Basis for Er Contri 01/2010                    0.00           8,750.00
/3FJ VPF basis for Ee contr 01/2010                    0.00           8,750.00
/3FL PF Basis for Er Contri 01/2010                    0.00           6,500.00
/3F4 Er Pension contributio 01/2010                    0.00             541.00
/3FC Pension Basis for Er c 01/2010                    0.00           6,500.00
/3FB PF Basis for Er Contri 01/2010                    0.00           8,750.00
/3FC Pension Basis for Er c 01/2010                    0.00           6,500.00
/3FJ VPF basis for Ee contr 01/2010                    0.00           8,750.00
/3FL PF Basis for Er Contri 01/2010                    0.00           6,500.00
/3R3 Metro HRA Basis Amount 01/2010                    0.00           8,750.00
1BAS Basic Salary           01/2010                    0.00           8,750.00
RT table for year 2009. DOL 27.10.2009
                                                                                /111 EPF Basis              07/2009                    0.00           9,016.13
/139 VPF Basis              07/2009                    0.00           9,016.13
/3F1 Ee PF contribution     07/2009                    0.00           1,082.00
/3F3 Er PF contribution     07/2009                    0.00             628.00
/3F5 Ee Mon PF contribution 07/2009                    0.00           1,082.00
/3F6 Ee Ann PF contribution 07/2009                    0.00           8,822.00
/3F9 PF adm chrgs * 1,00,00 07/2009                    0.00              99.18
/3FA PF basis for Ee contri 07/2009                    0.00           9,016.00
/3FB PF Basis for Er Contri 07/2009                    0.00           9,016.00
/3FJ VPF basis for Ee contr 07/2009                    0.00           9,016.00
/3FL PF Basis for Er Contri 07/2009                    0.00           5,452.00
/3FB PF Basis for Er Contri 07/2009                    0.00           9,016.00
/3FC Pension Basis for Er c 07/2009                    0.00           5,452.00
/3FJ VPF basis for Ee contr 07/2009                    0.00           9,016.00
/3FL PF Basis for Er Contri 07/2009                    0.00           5,452.00
/3R4 Non-metro HRA Basis Am 07/2009                    0.00           9,016.13
1BAS Basic Salary           07/2009                    0.00           9,016.13
Now please suggest what to do. where is the problem ? If have also checked EXIT_HINCALC0_002 but nothing written in it.
With Regards
Ashwani

Superblock issue

Similar Messages

Maybe you are looking for