Page 2 of 2 FirstFirst 12
Results 11 to 18 of 18

Thread: Entire system in read-only mode --can't login and I suspect virus...

  1. #11
    Join Date
    Apr 2008
    Location
    Austin, TX
    Beans
    39
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Entire system in read-only mode --can't login and I suspect virus...

    Quote Originally Posted by Gaming4JC View Post
    That sudo cat command seems to be doing nothing.
    This is normal; the command is reading your drive device and writing it to the null device (ie, nowhere).

    It should take a while, and report nothing until it's done.

    As an aside, this being the security forum, I would advise you to avoid running any "sudo" command without first understanding exactly what it does. Otherwise, you open yourself to mischief makers.

    (And really, this applies to all commands ; plenty of damage can be done without sudo).

  2. #12
    Join Date
    Dec 2006
    Location
    Chicago
    Beans
    3,839

    Re: Entire system in read-only mode --can't login and I suspect virus...

    Quote Originally Posted by Gaming4JC View Post
    Ummm... what now?

    Code:
    ubuntu@ubuntu:~$ sudo fsck -y /dev/sda1
    fsck 1.40.8 (13-Mar-2008)
    e2fsck 1.40.8 (13-Mar-2008)
    /dev/sda1: clean, 164090/19161088 files, 1913755/76622009 blocks
    ubuntu@ubuntu:~$ sudo e2fsck /dev/sda1
    e2fsck 1.40.8 (13-Mar-2008)
    /dev/sda1: clean, 164090/19161088 files, 1913755/76622009 blocks
    ubuntu@ubuntu:~$  sudo fsck -y /dev/sda1
    fsck 1.40.8 (13-Mar-2008)
    e2fsck 1.40.8 (13-Mar-2008)
    /dev/sda1: clean, 164090/19161088 files, 1913755/76622009 blocks
    ubuntu@ubuntu:~$ sudo fsck -y /dev/sda
    fsck 1.40.8 (13-Mar-2008)
    e2fsck 1.40.8 (13-Mar-2008)
    fsck.ext2: Device or resource busy while trying to open /dev/sda
    Filesystem mounted or opened exclusively by another program?
    ubuntu@ubuntu:~$ umount /dev/sda
    umount: /dev/sda is not mounted (according to mtab)
    LOL, now it says it's fine. unless I'm reading something wrong here.
    It looks like you probably have a partition on /dev/sda mounted, such as /dev/sda1.
    Code:
    mount|grep /dev/sda
    You may have corrected your filesystem errors, but that doesn't mean you don't still have a hardware problem. I've seen a bad IDE cable cause problems like that before. I wouldn't be surprised if you experience more errors soon.

    todb was right about the "sudo cat" command. If you're ever curious about what a command does, use the "man" command.
    Code:
    man man
    man sudo
    man cat
    man null

  3. #13
    Join Date
    Sep 2007
    Beans
    75

    Re: Entire system in read-only mode --can't login and I suspect virus...

    Run smartctl -a /dev/sda and post the output here. This will read the drive's SMART data, and it will tell us if the drive is obviously having hardware problems.

    There is no point running file system checking tools until you are confident that the drive is okay physically. By trying to repair the file system on a potentially bad drive, you might only make the problem worse.

  4. #14
    Join Date
    Jun 2008
    Beans
    53
    Distro
    Ubuntu 10.04 Lucid Lynx

    Smile Re: Entire system in read-only mode --can't login and I suspect virus...

    Yes, I think I ran this code once before. Anyhow, here it is again. Let me know if you see anything.
    Code:
    ubuntu@ubuntu:~$ sudo smartctl -a /dev/sda
    smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
    Home page is http://smartmontools.sourceforge.net/
    
    === START OF INFORMATION SECTION ===
    Device Model:     ST3320620SV
    Serial Number:    9QF5LNBQ
    Firmware Version: 3.ACH
    User Capacity:    320,072,933,376 bytes
    Device is:        Not in smartctl database [for details use: -P showall]
    ATA Version is:   7
    ATA Standard is:  Exact ATA specification draft version not indicated
    Local Time is:    Fri Jun 13 16:45:26 2008 UTC
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    
    General SMART Values:
    Offline data collection status:  (0x82)	Offline data collection activity
    					was completed without error.
    					Auto Offline Data Collection: Enabled.
    Self-test execution status:      (   0)	The previous self-test routine completed
    					without error or no self-test has ever 
    					been run.
    Total time to complete Offline 
    data collection: 		 ( 430) seconds.
    Offline data collection
    capabilities: 			 (0x5b) SMART execute Offline immediate.
    					Auto Offline data collection on/off support.
    					Suspend Offline collection upon new
    					command.
    					Offline surface scan supported.
    					Self-test supported.
    					No Conveyance Self-test supported.
    					Selective Self-test supported.
    SMART capabilities:            (0x0003)	Saves SMART data before entering
    					power-saving mode.
    					Supports SMART auto save timer.
    Error logging capability:        (0x01)	Error logging supported.
    					General Purpose Logging supported.
    Short self-test routine 
    recommended polling time: 	 (   1) minutes.
    Extended self-test routine
    recommended polling time: 	 ( 115) minutes.
    
    SMART Attributes Data Structure revision number: 10
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate     0x000f   114   100   006    Pre-fail  Always       -       71825124
      3 Spin_Up_Time            0x0003   094   094   000    Pre-fail  Always       -       0
      4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       351
      5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
      7 Seek_Error_Rate         0x000f   078   060   030    Pre-fail  Always       -       60496799
      9 Power_On_Hours          0x0032   098   098   000    Old_age   Always       -       2148
     10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
     12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       351
    187 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
    189 Unknown_Attribute       0x003a   100   100   000    Old_age   Always       -       0
    190 Temperature_Celsius     0x0022   066   054   045    Old_age   Always       -       572063778
    194 Temperature_Celsius     0x0022   034   046   000    Old_age   Always       -       34 (Lifetime Min/Max 0/15)
    195 Hardware_ECC_Recovered  0x001a   072   058   000    Old_age   Always       -       79649612
    197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
    198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
    199 UDMA_CRC_Error_Count    0x003e   200   199   000    Old_age   Always       -       593
    200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0
    202 TA_Increase_Count       0x0032   100   253   000    Old_age   Always       -       0
    
    SMART Error Log Version: 1
    ATA Error Count: 41 (device log contains only the most recent five errors)
    	CR = Command Register [HEX]
    	FR = Features Register [HEX]
    	SC = Sector Count Register [HEX]
    	SN = Sector Number Register [HEX]
    	CL = Cylinder Low Register [HEX]
    	CH = Cylinder High Register [HEX]
    	DH = Device/Head Register [HEX]
    	DC = Device Command Register [HEX]
    	ER = Error register [HEX]
    	ST = Status register [HEX]
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    
    Error 41 occurred at disk power-on lifetime: 1527 hours (63 days + 15 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      84 51 00 4e 90 7e e0  Error: ICRC, ABRT at LBA = 0x007e904e = 8294478
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      25 03 10 3f 90 7e e0 00      00:22:29.217  READ DMA EXT
      25 03 01 00 00 00 e0 00      00:22:29.181  READ DMA EXT
      ef 03 42 4e 10 00 a0 00      00:22:29.181  SET FEATURES [Set transfer mode]
      ef 03 0c 4e 10 00 a0 00      00:22:29.180  SET FEATURES [Set transfer mode]
      c6 00 10 4e 90 7e a0 00      00:22:31.611  SET MULTIPLE MODE
    
    Error 40 occurred at disk power-on lifetime: 1527 hours (63 days + 15 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      84 51 00 4e 90 7e e0  Error: ICRC, ABRT at LBA = 0x007e904e = 8294478
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      25 00 10 3f 90 7e e0 00      00:22:29.217  READ DMA EXT
      25 00 10 3f 90 7e e0 00      00:22:29.181  READ DMA EXT
      25 00 01 00 00 00 e0 00      00:22:29.181  READ DMA EXT
      25 00 01 00 00 00 e0 00      00:22:29.180  READ DMA EXT
      25 00 01 00 00 00 e0 00      00:22:28.892  READ DMA EXT
    
    Error 39 occurred at disk power-on lifetime: 1527 hours (63 days + 15 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      84 51 00 4e 90 7e e0  Error: ICRC, ABRT at LBA = 0x007e904e = 8294478
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      25 00 10 3f 90 7e e0 00      00:22:29.217  READ DMA EXT
      25 00 01 00 00 00 e0 00      00:22:29.181  READ DMA EXT
      25 00 01 00 00 00 e0 00      00:22:29.181  READ DMA EXT
      25 00 01 00 00 00 e0 00      00:22:29.180  READ DMA EXT
      25 00 10 3f 90 7e e0 00      00:22:28.892  READ DMA EXT
    
    Error 38 occurred at disk power-on lifetime: 1527 hours (63 days + 15 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      84 51 00 4e 90 7e e0  Error: ICRC, ABRT at LBA = 0x007e904e = 8294478
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      25 00 10 3f 90 7e e0 00      00:22:29.217  READ DMA EXT
      35 00 08 2f 00 5e e0 00      00:22:29.181  WRITE DMA EXT
      35 00 08 47 00 5e e0 00      00:22:29.181  WRITE DMA EXT
      35 00 48 87 02 5e e0 00      00:22:29.180  WRITE DMA EXT
      25 00 08 f7 62 4b e0 00      00:22:28.892  READ DMA EXT
    
    Error 37 occurred at disk power-on lifetime: 1527 hours (63 days + 15 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      84 51 00 4e 90 7e e0  Error: ICRC, ABRT at LBA = 0x007e904e = 8294478
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      25 00 10 3f 90 7e e0 00      00:22:27.962  READ DMA EXT
      25 00 01 00 00 00 e0 00      00:22:27.941  READ DMA EXT
      25 00 01 00 00 00 e0 00      00:22:27.940  READ DMA EXT
      25 00 01 00 00 00 e0 00      00:22:27.940  READ DMA EXT
      25 00 08 f7 62 4b e0 00      00:22:27.940  READ DMA EXT
    
    SMART Self-test log structure revision number 1
    Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
    # 1  Short offline       Completed without error       00%      2137         -
    # 2  Short offline       Completed without error       00%      2137         -
    
    SMART Selective self-test log data structure revision number 1
     SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
        1        0        0  Not_testing
        2        0        0  Not_testing
        3        0        0  Not_testing
        4        0        0  Not_testing
        5        0        0  Not_testing
    Selective self-test flags (0x0):
      After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    One minor problem, unless I can prove the hard drive is bad I doubt they will let me return it. And the official SeaTools program that the hard drive comes with said it was fine lol.

  5. #15
    Join Date
    Nov 2006
    Location
    Buckeye country
    Beans
    1,079
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Entire system in read-only mode --can't login and I suspect virus...

    are you using ext2 on this drive? can i ask why you're not using ext3?

    also, do you have more than 1 device on the bus? you said it's a new drive, so i'm wondering if you have 2 devices both set as master on the bus. or 2 devices both set to slave.

  6. #16
    Join Date
    Jun 2008
    Beans
    53
    Distro
    Ubuntu 10.04 Lucid Lynx

    Question Re: Entire system in read-only mode --can't login and I suspect virus...

    I believe it is ext2, yes. I installed Ubuntu with default settings so it did automatic partioning... is something wrong with this?

    If you mean is anything on the same IDE cable, no. My hardrive is a SATA-II, so it has it's own cable.

    However, I do have 2 CDR,DVDR, combo drives, and 1 floppy drive.

    You think somehow the system might think that one my CDR, DVD, combo drives is master making my HardDrive conflict?

  7. #17
    Join Date
    Jun 2008
    Beans
    53
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Entire system in read-only mode --can't login and I suspect virus...

    Ok I checked both of my IDE CD and DVD Rom drives. The one on top is set to master the one on bottom is set to slave. This should be fine?

    My SATA-II has no jumper settings anywhere I can see on it for master or slave. sooo....

    I checked all the wiring to make sure it was nice and snug, and put the case back together.

    Then I did another zero disk wipe (to remove grub boot loader), and tried reinstalling Ubuntu. I made sure this time it was ext3.
    But now it just gives this message at my BIOS:
    Code:
    Boot first hard drive:
    -
    The - blinks. But it just stays there locked up.

    I tried installing SlackWare and the same problem occurred. It's not a disk boot failure, but it just stay frozen for some strange reason.

    I am having the SATA drive exchanged for a new one, we'll see if this doesn't fix some of my problems...

    But if the problem were to persist after this new drive?

    I also pulled the memory and the Motherboard battery for the time being. I've heard advanced viruses can remain in memory for up to two hours, so just to be safe.

    If allll else fails, or if I'm daring enough. I my try to flash my bios. It's a bit out dated anyhow and I have my manual with all the information on how to do it...

  8. #18
    Join Date
    Jun 2008
    Beans
    53
    Distro
    Ubuntu 10.04 Lucid Lynx

    Angry Re: Entire system in read-only mode --can't login and I suspect virus...

    Ok I flashed my BIOS successfully, and replaced my hard drive.
    Now there's a new problem. Everytime I plug in this new SATA drive my BIOS freezes at "Verifying DMI Pool Data...". I checked my BIOS. It is recognized as a hard drive but refuses to get past the DMI check.

    My Drive is a Seagate Barracuda 72000.11 320GB. It came with new cables but no software. Here's the spec:
    http://www.seagate.com/ww/v/index.js...eqPage=Support

    My Mother board is a ABIT NF8-V2. All the specs are over here:
    http://www.uabit.com/index.php?optio...ge=2&model=292

    Please HELP!

Page 2 of 2 FirstFirst 12

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •