topic Re: About FSCK on Panorama in General Topics

About FSCK on Panorama

KiCheon.Lee — Thu, 31 Mar 2016 08:09:45 GMT

Hello

My customer use two M-100s.

One is used to Panorama and another is used to log-collector.

I upgraded two M-100s from 6.0.9 to 6.1.10.

I used manual upgraded way because environment what can not access to internet.

1. panorama was upgraded to 6.1.0 manual.

2. panorama was upgraded to 6.1.10 manual

3. log-collector was upgraded to 6.1.0 manual. using 'device deployment' menu

4. log-collector was upgraded to 6.1.10 manual. using 'device deployment' menu

I tried to reboot 4 times on for two M-100s.

But there was no FSCK perfoming. never.

Uptimes were over 380 days.

I expected M-100s must perform FSCK two times.

why did not M-100s perform FSCK?

Because log collector environment? or manual upgrade?

Please let me know it.

Re: About FSCK on Panorama

rmonvon — Thu, 31 Mar 2016 21:33:01 GMT

Hi...Did you attach a terminal to the console port and watch the bootup process? There are system messages on the console that should provide information on success/failure.

Are the M100s working ok after the reboot?

Re: About FSCK on Panorama

KiCheon.Lee — Fri, 01 Apr 2016 01:28:58 GMT

Thanks for your attention.

They are working well.

I was away from them. So I could not access to console port.

But they were boot up after 5 minutes.

Do you know how to check when they were done to perform FSCK last?

I just wonder whether there is a something cli command or not.

If there is the command, At next chance I will check when they perofomed FSCK last before rebooting.

I think I will need to make sure the days whether over 90 days or not.

Re: About FSCK on Panorama

Dulle — Fri, 01 Apr 2016 08:22:34 GMT

Try:
> less mp-log raid.log

Re: About FSCK on Panorama

KiCheon.Lee — Fri, 01 Apr 2016 08:59:46 GMT

What message should I see in the log?

Re: About FSCK on Panorama

Dulle — Fri, 01 Apr 2016 09:06:52 GMT

If ok, something like this:

Feb 11 10:36:51 DEBUG: Unmounting Disk Pair D (/dev/md4)
Feb 11 10:36:51 WARNING: Starting to check the file system integrity of the Raid Disk Pair D
Feb 11 10:36:51 ERROR: e4fsck 1.41.12 (17-May-2010)
Feb 11 10:36:51 DEBUG: 😧 clean, 20347297/61054976 files, 190167989/244189984 blocks (check in 2 mounts)
Feb 11 10:36:51 WARNING: Done checking the file system integrity of the Raid Disk Pair D
Feb 11 10:36:51 DEBUG: Mounting Disk Pair D (/dev/md4)

And also check with :
>show system raid detail
(But this you might very well know...)