Logical Block Addressing (LBA)

I have been having dual-boot issues for the past few years, the problem is...I can never get it to boot both operating systems. One suggestion by SUSE is to enable LBA in the BIOS. The article is here
My current motherboard is the MSIO K8N Neo Platinum with an AMD64 3400+ chipset. I do not see any options about enabling LBA in my BIOS.

If you left Bios settings at default there should be LBA enabled anyway. There is a option in the menu where you enable primary and secondary IDE.

Similar Messages

The IO operation at logical block address # for Disk # was retried

Hello everyone,
A warning appears in the system log:
===
Log Name:      System
Source:        disk
Date:          2/20/2013 1:00:28 PM
Event ID:      153
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      STRANGE.aqa.com.ru
Description:
The IO operation at logical block address af7ff for Disk 7 was retried.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="disk" />
    <EventID Qualifiers="32772">153</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-02-20T09:00:28.199176700Z" />
    <EventRecordID>12669</EventRecordID>
    <Channel>System</Channel>
    <Computer>STRANGE.aqa.com.ru</Computer>
    <Security />
</System>
<EventData>
    <Data>\Device\Harddisk7\DR142</Data>
    <Data>af7ff</Data>
    <Data>7</Data>
    <Binary>0F01040003002C00000000009900048000000000000000000000000000000000000000000000000000020828</Binary>
</EventData>
</Event>
===
This warning occurred in several seconds after the Windows Server Backup start. Our backup job finishes successfully. That server is in provisioning without a heavy workload, and we have not experienced any problem yet. But we do not want to face any problems
due to this error in the production environment.
All disks of the server are managed by the LSI MegaRAID controller, which doesn’t report any errors in the disk system.
it is Windows Server 2012 with the latest updates.

Wow, I have been having the exact same problems with Server 2012 WSB. I thought I had it resolved but it started acting up again. I tried 3 different external hard drives thinking they may be the problem. The raid array also seems fine,
it is not giving me any errors, no amber lights.
If I run a backup system state + hyper-v it would fail 9/10 of the time on the host component. I have posted every where and cannot find anything. These are the event during any backup I run.
Source: Disk
Event ID: 153
The IO operation at logical block address 10a58027 for Disk 5 was retried.
Source: VOLSNAP
Event ID: 25
The shadow copies of volume C: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.
Source: Filter Manager
Event ID: 3
Filter Manager failed to attach to volume '\Device\HarddiskVolume109'. This volume will be unavailable for filtering until a reboot. The final status was 0xC03A001C.
Source: VOLSNAP
Event ID: 27
The shadow copies of volume \\?\Volume{a21d0bb7-7147-11e2-93ed-842b2b0982fe} were aborted during detection because a critical control file could not be opened.
Source: VHDMP
Event ID: 129
Reset to device, \Device\RaidPort4, was issued.
Source: VOLSNAP
Event ID: 25
The shadow copies of volume G: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.
Windows backup gives me various errors for what did not backup. Mainly this one:
Error in backup of C:\ during enumerate: Error [0x80070003] The system cannot find the path specified.
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: Host Component
Caption : Host Component
Logical Path:
Error : 8078010D
Error Message : Enumeration of the files failed.
Detailed Error : 80070003
Detailed Error Message : (null)
Not just the host component, sometimes the entire C: ...
So no one has any recommendations on fixing this?
Is any one running dell AppAssure? I have two servers backing up to this server with dell AppAssure. Then I am using WSB to backup the this machines OS and 1 windows 7 VM.

The I operation at logical block address 0x747b49c0 for Disk 0 was retried

The IO operation at logical block address 0x747b49c0 for Disk 0 was retried

nasir-ahmad wrote:
The IO operation at logical block address 0x747b49c0 for Disk 0 was retried
Sounds like a bad hard drive but since we have no idea what computer this si coming form your asking us to find a needle in haystack question.
I am a Volunteer to help others on here-not a HP employee.
Replies aren't online 24/7 because of Time Zone differences.
Remember in this Day and Age of Computing the Internet is Knowledge at your fingertips if you choose understand it. -2015-

Logical block (LBA) information of a file

*How we can find out the Logical Block Address (LBA) of a file blocks. We need to find out the blocks which are using for storing a file in Memory.*

* log2phys.c - this Mac OS X program attempts to provide a physical disk
* map for the specified file(s).
* This is an EXPERIMENT! I think the code does what it says,
* but I have not verified the results.
* Bob Harris 14-Apr-2010 o initial coding
#include <stdio.h>
#include <stdlib.h>
#include <fcntl.h>
#include <unistd.h>
#include <errno.h>
#define STRIDE (4096) /* ASSUMES the allocation unit is 4K */
void log2phys(char *file);
int
main(int ac, char **av)
int n;
if ( ac < 2 ) {
fprintf(stderr, "Usage: log2phys file [file ...]
exit(EXIT_FAILURE);
for(n=1; n < ac; n++) {
log2phys(av[n]);
exit(EXIT_SUCCESS);
void
log2phys(char *file)
int fd;
int sts;
off_t offset;
off_t previous;
off_t length;
struct log2phys phys;
printf("%s
", file); /* display the file name */
fd = open(file, O_RDONLY); /* open the file */
if ( fd < 0 ) {
fprintf(stderr,"open(%s,O_RDONLY)", file);
perror(" ");
exit(EXIT_FAILURE);
* Seek through the file 4K at a time, and obtain the disk offset
sts = 0;
previous = (off_t)-1;
length = 0;
for(offset=0; sts >= 0; offset += STRIDE) {
/* position to next offset in the file */
sts = lseek(fd, offset, SEEK_SET);
if ( sts < 0 ) {
fprintf(stderr,"lseek(%d, %lld, SEEK_SET)", fd, offset);
perror(" ");
exit(EXIT_FAILURE);
/* fetch the current physical location for file offset */
sts = fcntl(fd, F_LOG2PHYS, &phys);
if ( sts < 0 && errno == ERANGE ) {
/* we have gone past the end of the file */
break;
else if ( sts < 0 ) {
fprintf(stderr,"fcntl(%d, F_LOG2PHYS, &phys)", fd);
perror(" ");
exit(EXIT_FAILURE);
* Figure out if this is a non-contiguous allocation unit
if ( previous + length != phys.l2p_devoffset ) {
if ( length != 0 ) {
* We have accumulated some length from the previous run of
* allocation units, so display the length of the previous
* starting offset
printf(" length= %11lld
", length);
length = 0;
/* Display the offset of this new run of allocation units */
printf(" file_offset= %10lld volume_offset= %17lld",
offset, phys.l2p_devoffset);
/* save the new previous starting physical offset */
previous = phys.l2p_devoffset;
/* Count this allocation unit as part of the length */
length += STRIDE;
* Print the final length.
if ( length ) {
printf(" length= %11lld
", length);
close(fd);

OSD-04001: invalid logical block size (OS 2800189884)

My Windows 2003 crashed which was running Oracle XE.
I installed Oracle XE on Windows XP on another machine.
I coped my D:\oracle\XE10g\oradata folder of Win2003 to the same location in WinXP machine.
When I start the database in WinXP using SQLPLUS i get the following message
SQL> startup
ORACLE instance started.
Total System Global Area 146800640 bytes
Fixed Size 1286220 bytes
Variable Size 62918580 bytes
Database Buffers 79691776 bytes
Redo Buffers 2904064 bytes
ORA-00205: error in identifying control file, check alert log for more info
I my D:\oracle\XE10g\app\oracle\admin\XE\bdump\alert_xe I found following errors
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 4 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Wed Apr 25 18:38:36 2007
ALTER DATABASE MOUNT
Wed Apr 25 18:38:36 2007
ORA-00202: control file: 'D:\ORACLE\XE10G\ORADATA\XE\CONTROL.DBF'
ORA-27047: unable to read the header block of file
OSD-04001: invalid logical block size (OS 2800189884)
Wed Apr 25 18:38:36 2007
ORA-205 signalled during: ALTER DATABASE MOUNT...
ORA-00202: control file: 'D:\ORACLE\XE10G\ORADATA\XE\CONTROL.DBF'
ORA-27047: unable to read the header block of file
OSD-04001: invalid logical block size (OS 2800189884)
Please help.
Regards,
Zulqarnain

Hi Zulqarnain,
Error OSD-04001 is Windows NT specific Oracle message. It means that the logical block size is not a multiple of 512 bytes, or it is too large.
So what you can do? Well you should try to change the value of DB_BLOCK_SIZE in the initialization parameter file.
Regards

ORA-27046: file size is not a multiple of logical block size

Hi All,
Getting the below error while creating Control File after database restore. Permission and ownership of CONTROL.SQL file is 777 and ora<sid>:dba
ERROR -->
SQL> !pwd
/oracle/SID/sapreorg
SQL> @CONTROL.SQL
ORACLE instance started.
Total System Global Area 3539992576 bytes
Fixed Size                  2088096 bytes
Variable Size            1778385760 bytes
Database Buffers         1744830464 bytes
Redo Buffers               14688256 bytes
CREATE CONTROLFILE SET DATABASE "SID" RESETLOGS ARCHIVELOG
ERROR at line 1:
ORA-01503: CREATE CONTROLFILE failed
ORA-01565: error in identifying file
'/oracle/SID/sapdata5/p11_19/p11.data19.dbf'
ORA-27046: file size is not a multiple of logical block size
Additional information: 1
Additional information: 1895833576
Additional information: 8192
Checked in target system init<SID>.ora and found the parameter db_block_size is 8192. Also checked in source system init<SID>.ora and found the parameter db_block_size is also 8192.
/oracle/SID/102_64/dbs$ grep -i block initSID.ora
Kindly look into the issue.
Regards,
Soumya

Please chk the following things
1.SPfile corruption :
Startup the DB in nomount using pfile (ie init<sid>.ora) create spfile from pfile;restart the instance in nomount state
Then create the control file from the script.
2. Check Ulimit of the target server , the filesize parameter for ulimit shud be unlimited.
3. Has the db_block_size parameter been changed in init file by any chance.
Regards
Kausik

DB Cloning.file size is not a multiple of logical block size

Dear All,
I am trying to create database in windowsXP from the database files running in Linux.
When i try to create control file, i m getting the following errors.
ORA-01503: CREATE CONTROLFILE failed
ORA-01565: error in identifying file
'D:\oracle\orcl\oradata\orcl\system01.dbf'
ORA-27046: file size is not a multiple of logical block size
OSD-04012: file size mismatch (OS 367009792)
Pls tell me the workarounds.
Thanks
Sathis.

Hi ,
I created database service by oradim. Now i m trying to create control file after editing the controlfile with the location of windows datafiles(copied from Linux)
Thanks,
Sathis.

SAN Configuration Error: Buffer I/O error on device sdd, logical block 0

hi,
I had successfully to configured dm-multipath.. now i can see the mapped device as
# ll /dev/mapper
crw------- 1 root root 10, 61 Nov 19 18:59 control
brw-rw---- 1 root disk 253, 0 Nov 19 20:00 ovs
ovs is an alias for /dev/sdc which is the active path of the storage Lun , but the passive path /dev/sdd is still existing and it giving error at the boot of OVM Server
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
i can't understand why the system is still looking for the passive path /dev/sdd even after multipath was configured ????
did anybody faced this kind of problem then please help me..
Thanks in Advance

Raja Gounder wrote:
I had successfully to configured dm-multipath.. now i can see the mapped device asYou haven't configured it correctly, otherwise you wouldn't have a friendly name configured. Oracle VM requires WWIDs in /dev/mapper to make the device available.

Buffer I/O error on device sdd1, logical block, HDD failure? [SOLVED]

Hello!
I'm a bit puzzled here to be honest. Granted i'm not using linux as much as I used to (not after windows 7). I have archlinux running on my HTPC. Never had any issues before that was this severe, unless I upgraded and forgot to read news section. Booted the htpc today to be greeted by "Buffer I/O error on device sdd1, logical block" with a massive wall of text, a few seconds later "welcome to emergency mode."
*This is NOT hdd where the linux kernel is residing on. What logical purpose would it serve for the kernel/userspace to abort everything just because fsck fails or something? If this was indeed my linux partition I would fully understand.
Anyways, I used parted magic, ran fsck, smart. Sure enough fsck warned me about bad/missing superblock. Restored the superblock by using e2fsck. I had over 10 000 "incorrect size" chunks. Ran 2-3 SMART after that. fsck says okay, smart gives a 100% status report with no errors.
Oh yeah, I have turned off FSCK completly in my fstab, thinking about at least turning it on my bigger hdds
Questions:
*Is SMART reliable? If it says it's alright, does that mean i'm safe? Would physical broken sectors turn up by SMART?
*I know SMART warns the user in windows 7 if hdd failure is imment. Is this possible within linux as well? Since i'm NOT using a GUI, is this possible to send through a terminal/email?
*Sometimes the HTPC have been forefully shut down (power breakage), could this be one of the causes of the I/O error?
As always, thank you for your support.
Last edited by greenfish (2013-10-23 13:23:21)

graysky wrote:Any reallocated sectors in smartmontools? If you run 'e2fsck -fv /dev/sdd1' does it complete wo/ errors? Probably best to repeat for all linux partitions on that disk.
Sorry for the late reply guys. Been busy with my other hdd that decided to screw with me. e2fsck first complained about bad sectors, and wrong size. Now it says all clean. I've decided to remove this HDD from server and mark it "damaged".
Thank you again for your help
alphaniner wrote:
greenfish wrote:*Is SMART reliable? If it says it's alright, does that mean i'm safe? Would physical broken sectors turn up by SMART?
*I know SMART warns the user in windows 7 if hdd failure is imment. Is this possible within linux as well? Since i'm NOT using a GUI, is this possible to send through a terminal/email?
1) Don't trust the 'SMART overall-health self-assessment test result', run the diagnostics (short, long, conveyance, offline). The short and conveyance tests are quick so start with them. If they both pass run the long test. The offline test is supposed to update SMART attributes, but it generally takes longer than the long test, so save it for last if at all. Usually when I see bad drives the short or long tests pick them up.
2) Look into smartd.service.
greenfish wrote:What logical purpose would it serve for the kernel/userspace to abort everything just because fsck fails or something?
Systemd craps itself if an fs configured to mount during boot can't be mounted, even if the fs isn't necessary for the system to boot. Rot sure about how it handles fsck failures. This 'feature' can be disabled by putting nofail in the fstab options. I add it to every non-essential automounting fs.
Thank you for the useful information. I will save this post for future references.
Will deff look into smartd.service, especially when I have so much data running 24/7.
Will also update my fstab table with "nofail" like you suggested
Thank You!

Buffer I/O error on device hda1, logical block 81934

I getting the follow erro message when I session into the CUE of the UC520. All advice appreciated. I read the similar post, however I'm not given any prompts to make a selection.
Buffer I/O error on device hda1, logical block 81934
Processing manifests . Error processing file exceptions.IOError [Errno 5] Input/output error
. . . . . . Error processing file zlib.error Error -3 while decompressing: invalid distances set
. . . . . . . . Error processing file zlib.error Error -3 while decompressing: invalid distances set
. . complete
==> Management interface is eth0
==> Management interface is eth0
malloc: builtins/evalfile.c:138: assertion botched
free: start and end chunk sizes differ
Stopping myself.../etc/rc.d/rc.aesop: line 478: 1514 Aborted /bin/runrecovery.sh
Serial Number:
INIT: Entering runlevel: 2
********** rc.post_install ****************
INIT: Switching to runlevel: 4
INIT: Sending processes the TERM signal
STARTED: cli_server.sh
STARTED: ntp_startup.sh
STARTED: LDAP_startup.sh
STARTED: SQL_startup.sh
STARTED: dwnldr_startup.sh
STARTED: HTTP_startup.sh
STARTED: probe
STARTED: superthread_startup.sh
STARTED: ${ROOT}/usr/bin/products/herbie/herbie_startup.sh
STARTED: /usr/wfavvid/run-wfengine.sh
STARTED: /usr/bin/launch_ums.sh
Waiting 5 ...Buffer I/O error on device hda1, logical block 70429
Waiting 6 ...hda: no DRQ after issuing MULTWRITE
hda: drive not ready for command
Buffer I/O error on device hda1, logical block 2926
Buffer I/O error on device hda1, logical block 2927
Buffer I/O error on device hda1, logical block 2928
Buffer I/O error on device hda1, logical block 2929
Buffer I/O error on device hda1, logical block 2930
Buffer I/O error on device hda1, logical block 2931
Buffer I/O error on device hda1, logical block 2932
Buffer I/O error on device hda1, logical block 2933
Buffer I/O error on device hda1, logical block 2934
REISERFS: abort (device hda1): Journal write error in flush_commit_list
REISERFS: Aborting journal for filesystem on hda1
Jun 17 16:36:11 localhost kernel: REISERFS: abort (device hda1): Journal write error in flush_commit_list
Jun 17 16:36:11 localhost kernel: REISERFS: Aborting journal for filesystem on hda1
Waiting 8 ...MONITOR EXITING...
SAVE TRACE BUFFER
Jun 17 16:36:13 localhost err_handler: CRASH appsServices startup startup.sh System has crashed. The trace buffer information is stored in the file "atrace_save.log". You can upload the file using "copy log" command
/bin/startup.sh: line 262: /usr/bin/atr_buf_save: Input/output error
Waiting 9 ...Buffer I/O error on device hda1, logical block 172794
INIT: Sending processes the TERM signal
INIT: cannot execute "/etc/rc.d/rc.reboot"
INIT: no more processes left in this runlevel

The flash card for CUE might be corrupt. Try and reinstall CUE and restore from backup to see if that fixes it. If it doesnt, try a different flash card.
Cole

Logical Block corruption - not enough RMAN backups

I have to deal with logical block corruption but these guys do not have enough rman backups to go back enough to recover blocks.
All bad blocks are in SYSAUX and it seems because of it EM doesn't work as it's suppose to do. I dropped and recreated EM repository hoping it will clean itself but .... no.
Any ideas?
Oracle Linux 4.7 i386
Oracle 10.2.0.4

OCCUPANT_NAME OCCUPANT_DESC SCHEMA_NAME MOVE_PROCEDURE MOVE_PROCEDURE_DESC SPACE_USAGE_KBYTES
EM Enterprise Manager Repository SYSMAN emd_maintenance.move_em_tblspc Move Procedure for Enterprise Manager Repository 52800
EM_MONITORING_USER Enterprise Manager Monitoring User DBSNMP *** MOVE PROCEDURE NOT APPLICABLE *** 1600

Force Logical Block size for HDD pulled from external enclourse

So I pulled a 3tb hitachi drive from an external enclourse, and the usb-to-sata board in the enclourse forced a logical sector size of 4K for the drive. But connecting directly to the drive exposes the logical sector size to 512 bytes. Resulting in me being unable to mount the partition. So what I am asking is, is there a way to force the logical sector size for a drive to be different than the drive exposes or am I going to have to move everything off the drive and reformat it?
The enclourse in question:
http://www.newegg.com/Product/Product.a … 6822145510
Direct:
[73828.076447] sd 0:0:1:2: [sdl] Synchronizing SCSI cache
[73838.912744] scsi 0:0:1:2: Direct-Access Hitachi HDS723030ALA640 R001 PQ: 0 ANSI: 5
[73838.912889] sd 0:0:1:2: [sdo] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[73838.912892] sd 0:0:1:2: Attached scsi generic sg12 type 0
[73838.912995] sd 0:0:1:2: [sdo] Write Protect is off
[73838.912999] sd 0:0:1:2: [sdo] Mode Sense: cb 00 00 08
[73838.913042] sd 0:0:1:2: [sdo] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[73838.949343] sdo: sdo1
[73838.949614] sd 0:0:1:2: [sdo] Attached SCSI disk
USB:
Mar 5 18:52:35 localhost kernel: [ 4.711438] sd 8:0:0:0: [sdl] 732566016 4096-byte logical blocks: (3.00 TB/2.72 TiB)
Mar 5 18:52:35 localhost kernel: [ 4.712191] sd 8:0:0:0: [sdl] Write Protect is off
Mar 5 18:52:35 localhost kernel: [ 4.712193] sd 8:0:0:0: [sdl] Mode Sense: 4b 00 10 08
Mar 5 18:52:35 localhost kernel: [ 4.712938] sd 8:0:0:0: [sdl] No Caching mode page present
Mar 5 18:52:35 localhost kernel: [ 4.713978] sd 8:0:0:0: [sdl] Assuming drive cache: write through
Mar 5 18:52:35 localhost kernel: [ 4.714720] sd 8:0:0:0: [sdl] 732566016 4096-byte logical blocks: (3.00 TB/2.72 TiB)
Mar 5 18:52:35 localhost kernel: [ 4.716186] sd 8:0:0:0: [sdl] No Caching mode page present
Mar 5 18:52:35 localhost kernel: [ 4.717215] sd 8:0:0:0: [sdl] Assuming drive cache: write through
Mar 5 18:52:35 localhost kernel: [ 4.735573] sdl: sdl1
Mar 5 18:52:35 localhost kernel: [ 4.736557] sd 8:0:0:0: [sdl] 732566016 4096-byte logical blocks: (3.00 TB/2.72 TiB)
Mar 5 18:52:35 localhost kernel: [ 4.738058] sd 8:0:0:0: [sdl] No Caching mode page present
Mar 5 18:52:35 localhost kernel: [ 4.739085] sd 8:0:0:0: [sdl] Assuming drive cache: write through
Mar 5 18:52:35 localhost kernel: [ 4.740238] sd 8:0:0:0: [sdl] Attached SCSI disk

Hi ebrian,
You can't perform a migration from Linux to Windows in that manner with 9i.The plan can be changed to migrate from 9.2.0.4 to 10g and than move from 32-bit Linux to 32-bit Windows.
It should not matter the end result for the OP is the same 10g on 32 bit windows.
It just depends on what technoly the OP wants to use (export/import or rman convert).
Regards,
Tycho

Corrupt logical block

I want to check logical block corruption and repair it with dbms_repair package.
For that first i need to corrupt block logically.
How to corrupt oracle database table block logically? Is there any procedure to do that?
Thanks,

Hello,
Thanks for you resposes.
I tried to corrupt datablock by editing datafile and remove some data and add some data.
1. Execurted below rman commad
RMAN> backup validate check logical database;
Output show block is corrupted.
Below query is also listing corrupted blocks.
SQL> select * from v$database_block_corruption;
But when i am checking corruption with dbms_repair packges it doesn't list any corruption.
SET SERVEROUTPUT ON
DECLARE num_corrupt INT;
BEGIN
num_corrupt := 0;
DBMS_REPAIR.CHECK_OBJECT (
SCHEMA_NAME => 'TEST',
OBJECT_NAME => 'TEST1',
REPAIR_TABLE_NAME => 'REPAIR_TABLE',
CORRUPT_COUNT => num_corrupt);
DBMS_OUTPUT.PUT_LINE('number corrupt: ' || TO_CHAR (num_corrupt));
END;
Please let me know any other scenarios to corrupt LOGICAL block.
Thanks,

I linux inode which contains 13 member array wich stores the actual block address of data .Similarly in windows how data is managed in disk ?. How many members in this array ?

I linux inode which contains 13 member array wich stores the actual block address of data .Similarly in windows how data is managed in disk ?. How many members in this array ?

Hello Vijay Nerkar,
Your question is not related to Windows Forms General. What is the data you mean and also what is that array?
If you are looking for something related to Windows File System, see some words here:
http://en.wikipedia.org/wiki/File_system
For example
"Windows makes use of the
FAT, NTFS,
exFAT and ReFS file systems (the last of these is only supported and usable in
Windows Server 2012; Windows cannot boot from it).
Windows uses a drive letter abstraction at the user level to distinguish one disk or partition from another. For example, the
path <tt>C:\WINDOWS</tt> represents a directory <tt>WINDOWS</tt> on the partition represented by the letter C. Drive C: is most commonly used for the primary hard disk partition, on which Windows is usually installed and from which it boots. This "tradition"
has become so firmly ingrained that bugs exist in many applications which make assumptions that the drive that the operating system is installed on is C. The use of drive letters, and the tradition of using "C" as the drive letter for the primary hard disk
partition, can be traced to
MS-DOS, where the letters A and B were reserved for up to two floppy disk drives. This in turn derived from
CP/M in the 1970s, and ultimately from IBM's
CP/CMS of 1967.
For more details, consider consult on MS Answers:
http://answers.microsoft.com/en-us/windows
Regards,
Barry Wang
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Never Block Addresses - Sensor IP

Ok, finally convinced the boss to buy a 4240 and I am setting it up....
As far as Never Block IP's are concerned, is it profitable to use the Sensor IP since it uses that IP as the Source Address?
What I mean is..say this is your setup
INET --> PIX --> Router
Besides using the PIX as a blocking device I am also using the Router as it connects to some other networks and VPN Devices. I have an Inbound ACL that I am using as a PostBlock ACL. This ACL blocks spoofing. But, when the sensor logs into the router and reconfigures the ACLs (per host manual block), the sensor IP is permitted first and this undos some of the Antispoofing ACEs in the Postshun ACL as if on the chance the Sensors IP was used in a spoofing attack, it would be given a free pass into the network.
BTW, I do have uRPF and other Antispoofing measures setup on the PIX, but I am a big fan of layered security and don't want to comprimise our Network.

As far as never block addresses is concerned, my view is that you shouldnt block you own range as you could create a denial of service on yourself.
With regards to using the router as a blocking device you need to move your anti spoofing ACL from the outside I/F as the sensor needs to use this exclusively to dynamically create ACLs I suggest you move it to the inside I/F and change the direction i.e. instead of inbound change to outbound.
If you have a Pix you could also consider using the Pix as the shunning device and leave your anti-spoofing ACL on the transit router, unless your transit router is quick performance wise the Pix will probably be a better option.
I hope this helps
Regards Mark

Logical Block Addressing (LBA)

Similar Messages

Maybe you are looking for