What is the meaning of below picture. I ran fsck -c / then I got below output [on hold] The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsShould I be worried? Segfaults reported in syslog when merging LVM snapshot (reverting the original back to the snapshot)Valley View “Black Screen of Death”Which process scheduler is my linux system using?Problem with grep on multiple files and not getting desired outputSSH Connection Timed OutHow to grep response to figure out how many calls got timed out?How can I have a pingable IP but the wireess interface is unassociated?rm -rf directory with 0 size and blocksNeed Intel Xeon E3-1200 drivers for Linux Mint 18Tail with case statement is not working properly
how can a perfect fourth interval be considered either consonant or dissonant?
Relations between two reciprocal partial derivatives?
Can withdrawing asylum be illegal?
Are my PIs rude or am I just being too sensitive?
Arduino Pro Micro - switch off LEDs
Keeping a retro style to sci-fi spaceships?
In horse breeding, what is the female equivalent of putting a horse out "to stud"?
Grover's algorithm - DES circuit as oracle?
Did the UK government pay "millions and millions of dollars" to try to snag Julian Assange?
Create an outline of font
What's the point in a preamp?
Does Parliament hold absolute power in the UK?
I could not break this equation. Please help me
How many people can fit inside Mordenkainen's Magnificent Mansion?
Would an alien lifeform be able to achieve space travel if lacking in vision?
How to test the equality of two Pearson correlation coefficients computed from the same sample?
Why did all the guest students take carriages to the Yule Ball?
"... to apply for a visa" or "... and applied for a visa"?
When did F become S in typeography, and why?
Is a pteranodon too powerful as a beast companion for a beast master?
How to politely respond to generic emails requesting a PhD/job in my lab? Without wasting too much time
Are spiders unable to hurt humans, especially very small spiders?
Difference between "generating set" and free product?
ELI5: Why do they say that Israel would have been the fourth country to land a spacecraft on the Moon and why do they call it low cost?
What is the meaning of below picture. I ran fsck -c / then I got below output [on hold]
The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election ResultsShould I be worried? Segfaults reported in syslog when merging LVM snapshot (reverting the original back to the snapshot)Valley View “Black Screen of Death”Which process scheduler is my linux system using?Problem with grep on multiple files and not getting desired outputSSH Connection Timed OutHow to grep response to figure out how many calls got timed out?How can I have a pingable IP but the wireess interface is unassociated?rm -rf directory with 0 size and blocksNeed Intel Xeon E3-1200 drivers for Linux Mint 18Tail with case statement is not working properly
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
- I unmounted "/" then I ran fsck -c after that I got below out put. please tell me what it is exact meaning.
- And also tell me if I get below output it means will my problem resolved? Please provide a step by step answer dont confuse me.
linux
asked Apr 9 at 23:33
GangasagarGangasagar
11
put on hold as too broad by G-Man, muru, X Tian, roaima, Mr Shunz yesterday
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
- I unmounted "/" then I ran fsck -c after that I got below out put. please tell me what it is exact meaning.
- And also tell me if I get below output it means will my problem resolved? Please provide a step by step answer dont confuse me.
linux
asked Apr 9 at 23:33
GangasagarGangasagar
11
put on hold as too broad by G-Man, muru, X Tian, roaima, Mr Shunz yesterday
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
5
Welcome to U/L. Please do not post images. Please remove the image and replace it with the raw text.
– Sparhawk
Apr 10 at 0:01
Unmounting/would make/sbin/fscknot accessible, so I think you either failed to unmount/or actually did something different, like switched it to read-only mode.
– telcoM
Apr 10 at 6:59
add a comment |
- I unmounted "/" then I ran fsck -c after that I got below out put. please tell me what it is exact meaning.
- And also tell me if I get below output it means will my problem resolved? Please provide a step by step answer dont confuse me.
linux
asked Apr 9 at 23:33
GangasagarGangasagar
11
- I unmounted "/" then I ran fsck -c after that I got below out put. please tell me what it is exact meaning.
- And also tell me if I get below output it means will my problem resolved? Please provide a step by step answer dont confuse me.
linux
linux
asked Apr 9 at 23:33
GangasagarGangasagar
11
asked Apr 9 at 23:33
GangasagarGangasagar
11
asked Apr 9 at 23:33
GangasagarGangasagar
11
asked Apr 9 at 23:33
GangasagarGangasagar
11
asked Apr 9 at 23:33
GangasagarGangasagar
11
11
put on hold as too broad by G-Man, muru, X Tian, roaima, Mr Shunz yesterday
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as too broad by G-Man, muru, X Tian, roaima, Mr Shunz yesterday
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
5
Welcome to U/L. Please do not post images. Please remove the image and replace it with the raw text.
– Sparhawk
Apr 10 at 0:01
Unmounting/would make/sbin/fscknot accessible, so I think you either failed to unmount/or actually did something different, like switched it to read-only mode.
– telcoM
Apr 10 at 6:59
add a comment |
5
Welcome to U/L. Please do not post images. Please remove the image and replace it with the raw text.
– Sparhawk
Apr 10 at 0:01
Unmounting/would make/sbin/fscknot accessible, so I think you either failed to unmount/or actually did something different, like switched it to read-only mode.
– telcoM
Apr 10 at 6:59
5
5
Welcome to U/L. Please do not post images. Please remove the image and replace it with the raw text.
– Sparhawk
Apr 10 at 0:01
Welcome to U/L. Please do not post images. Please remove the image and replace it with the raw text.
– Sparhawk
Apr 10 at 0:01
Unmounting
/ would make /sbin/fsck not accessible, so I think you either failed to unmount / or actually did something different, like switched it to read-only mode.– telcoM
Apr 10 at 6:59
Unmounting
/ would make /sbin/fsck not accessible, so I think you either failed to unmount / or actually did something different, like switched it to read-only mode.– telcoM
Apr 10 at 6:59
add a comment |
1 Answer
1
active
oldest
votes
The fsck command did read through the entire logical volume to look for bad blocks, and then made some change to the list of bad blocks within the filesystem. Then it ran the standard 5 filesystem consistency check passes and found nothing wrong.
As this is your current root filesystem, it cannot really be unmounted, only remounted in read-only mode. That means, even if the filesystem is in read-only mode, any data read from the filesystem will still be cached in the system RAM. So it is possible that old data (in this case, specifically the old version of the bad blocks list) is still in RAM cache and might be used and eventually written back to the disk if the filesystem is switched to read/write mode without rebooting. Because of this, it is important to reboot the system after running fsck on your root filesystem if fsck did have to make any changes to the filesystem, no matter how small. And apart fromt the bad block information update, it appears fsck did not need to do anything else.
You should now reboot, then run dumpe2fs -b /dev/mapper/RootVolGroup00-lv_root to view the current list of bad blocks detected at the filesystem level. If it only displays the version number of the dumpe2fs command, there were no bad blocks detected.
Note: if there are any bad blocks detected at the filesystem level, that very likely means the disk's internal firmware-based bad block replacement mechanism is already been overwhelmed by the number of bad blocks on the disk. In that case I would immediately make sure my backups are up to date, and would seriously consider replacing the disk as a precaution.
You might want to use smartctl -HA -f brief /dev/sda or similar to get more information about the health of the disk.
answered Apr 10 at 7:32
telcoMtelcoM
20.9k12452
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The fsck command did read through the entire logical volume to look for bad blocks, and then made some change to the list of bad blocks within the filesystem. Then it ran the standard 5 filesystem consistency check passes and found nothing wrong.
As this is your current root filesystem, it cannot really be unmounted, only remounted in read-only mode. That means, even if the filesystem is in read-only mode, any data read from the filesystem will still be cached in the system RAM. So it is possible that old data (in this case, specifically the old version of the bad blocks list) is still in RAM cache and might be used and eventually written back to the disk if the filesystem is switched to read/write mode without rebooting. Because of this, it is important to reboot the system after running fsck on your root filesystem if fsck did have to make any changes to the filesystem, no matter how small. And apart fromt the bad block information update, it appears fsck did not need to do anything else.
You should now reboot, then run dumpe2fs -b /dev/mapper/RootVolGroup00-lv_root to view the current list of bad blocks detected at the filesystem level. If it only displays the version number of the dumpe2fs command, there were no bad blocks detected.
Note: if there are any bad blocks detected at the filesystem level, that very likely means the disk's internal firmware-based bad block replacement mechanism is already been overwhelmed by the number of bad blocks on the disk. In that case I would immediately make sure my backups are up to date, and would seriously consider replacing the disk as a precaution.
You might want to use smartctl -HA -f brief /dev/sda or similar to get more information about the health of the disk.
answered Apr 10 at 7:32
telcoMtelcoM
20.9k12452
add a comment |
The fsck command did read through the entire logical volume to look for bad blocks, and then made some change to the list of bad blocks within the filesystem. Then it ran the standard 5 filesystem consistency check passes and found nothing wrong.
As this is your current root filesystem, it cannot really be unmounted, only remounted in read-only mode. That means, even if the filesystem is in read-only mode, any data read from the filesystem will still be cached in the system RAM. So it is possible that old data (in this case, specifically the old version of the bad blocks list) is still in RAM cache and might be used and eventually written back to the disk if the filesystem is switched to read/write mode without rebooting. Because of this, it is important to reboot the system after running fsck on your root filesystem if fsck did have to make any changes to the filesystem, no matter how small. And apart fromt the bad block information update, it appears fsck did not need to do anything else.
You should now reboot, then run dumpe2fs -b /dev/mapper/RootVolGroup00-lv_root to view the current list of bad blocks detected at the filesystem level. If it only displays the version number of the dumpe2fs command, there were no bad blocks detected.
Note: if there are any bad blocks detected at the filesystem level, that very likely means the disk's internal firmware-based bad block replacement mechanism is already been overwhelmed by the number of bad blocks on the disk. In that case I would immediately make sure my backups are up to date, and would seriously consider replacing the disk as a precaution.
You might want to use smartctl -HA -f brief /dev/sda or similar to get more information about the health of the disk.
answered Apr 10 at 7:32
telcoMtelcoM
20.9k12452
add a comment |
The fsck command did read through the entire logical volume to look for bad blocks, and then made some change to the list of bad blocks within the filesystem. Then it ran the standard 5 filesystem consistency check passes and found nothing wrong.
As this is your current root filesystem, it cannot really be unmounted, only remounted in read-only mode. That means, even if the filesystem is in read-only mode, any data read from the filesystem will still be cached in the system RAM. So it is possible that old data (in this case, specifically the old version of the bad blocks list) is still in RAM cache and might be used and eventually written back to the disk if the filesystem is switched to read/write mode without rebooting. Because of this, it is important to reboot the system after running fsck on your root filesystem if fsck did have to make any changes to the filesystem, no matter how small. And apart fromt the bad block information update, it appears fsck did not need to do anything else.
You should now reboot, then run dumpe2fs -b /dev/mapper/RootVolGroup00-lv_root to view the current list of bad blocks detected at the filesystem level. If it only displays the version number of the dumpe2fs command, there were no bad blocks detected.
Note: if there are any bad blocks detected at the filesystem level, that very likely means the disk's internal firmware-based bad block replacement mechanism is already been overwhelmed by the number of bad blocks on the disk. In that case I would immediately make sure my backups are up to date, and would seriously consider replacing the disk as a precaution.
You might want to use smartctl -HA -f brief /dev/sda or similar to get more information about the health of the disk.
answered Apr 10 at 7:32
telcoMtelcoM
20.9k12452
The fsck command did read through the entire logical volume to look for bad blocks, and then made some change to the list of bad blocks within the filesystem. Then it ran the standard 5 filesystem consistency check passes and found nothing wrong.
As this is your current root filesystem, it cannot really be unmounted, only remounted in read-only mode. That means, even if the filesystem is in read-only mode, any data read from the filesystem will still be cached in the system RAM. So it is possible that old data (in this case, specifically the old version of the bad blocks list) is still in RAM cache and might be used and eventually written back to the disk if the filesystem is switched to read/write mode without rebooting. Because of this, it is important to reboot the system after running fsck on your root filesystem if fsck did have to make any changes to the filesystem, no matter how small. And apart fromt the bad block information update, it appears fsck did not need to do anything else.
You should now reboot, then run dumpe2fs -b /dev/mapper/RootVolGroup00-lv_root to view the current list of bad blocks detected at the filesystem level. If it only displays the version number of the dumpe2fs command, there were no bad blocks detected.
Note: if there are any bad blocks detected at the filesystem level, that very likely means the disk's internal firmware-based bad block replacement mechanism is already been overwhelmed by the number of bad blocks on the disk. In that case I would immediately make sure my backups are up to date, and would seriously consider replacing the disk as a precaution.
You might want to use smartctl -HA -f brief /dev/sda or similar to get more information about the health of the disk.
answered Apr 10 at 7:32
telcoMtelcoM
20.9k12452
answered Apr 10 at 7:32
telcoMtelcoM
20.9k12452
answered Apr 10 at 7:32
telcoMtelcoM
20.9k12452
answered Apr 10 at 7:32
telcoMtelcoM
20.9k12452
20.9k12452
add a comment |
add a comment |
5
Welcome to U/L. Please do not post images. Please remove the image and replace it with the raw text.
– Sparhawk
Apr 10 at 0:01
Unmounting
/would make/sbin/fscknot accessible, so I think you either failed to unmount/or actually did something different, like switched it to read-only mode.– telcoM
Apr 10 at 6:59